I've already posted this today and someone was kind enough to reply but now the original post has gone. Please reply again.
I uploaded my ROM image using XDA tools from my XDAII and attempted to open it using the ROM editor but it says that the passwords don't work that allow it to open.
Any ideas?
Thanks again.
Make sure you don't use the Autodetect type when selecting. Specify the particular file type from the drop down list when selecting the nbf file to open.
(I think that's what I said)
Thanks for that. Still no joy though.
What format does the filename need to be?
When opening a file in ER2003Edit, the file open dialog contains a 'Files of type' drop down list from which you can select the OS ROM (NK.nbf), the Extended ROM (ms_.nbf) or the Radio ROM (Radio_.nbf). Select the appropriate one here, then look for the file in the file list. Do not use the Auto-detect ROM option.
If, after selecting the file as stated above, the password still fails, then the password being used may be wrong.
So, using the Image Tool I select the source as Device Memory (current rom) and the source as any file name I choose on my PC.
When it gets to time left = 0:00 the file should be there? I chose to call it Original.nbf. The image tool doesn't say its done by the way, it just reaches zero. Is this correct?
When I now try to open this I get the password error.
Where am I going wrong?
Aaah now I understand. I missed that are using XDATools to obtain the file. So ignore everything I have been saying I thought you were using ER2003Edit to open standard nbf files. Files extracted using XDATools will be in decrypted form and won't need a password.
btw - XDATools is designed for use with the XDA I, not the XDA II. What is it you are trying to do?
Okay, now we're getting somewhere.
I want to extract my ROM, play around with it and write it back.
By 'playing around', do you mean changing the default installed applications? If so, you would probably be better unlocking the extended ROM on the device and playing around with that. You can find information about doing that by searching the forums. If you are talking about upgrading your software (OS), then you need to use the HimaUpgradeUt route instead of XDATools. My post here gives details on how to do that.
I hope this helps.
Related
Hi guys,
I've got an XDAII and I want to be able to see / edit the extended rom...
I've found the cab files I need (elsewhere in this forum) but I have no idea whatsoever how to use them?!?!
I can't run them, so there must be either an app I need or somewhere I need to put them, right?
Please help
Thx
Have you transfeered the cab file to your phone and executed from there?
It's a cab file. You put it on the XDA II in a folder of your choice, then run it, after reboot you will find a new icon in Programs. The rest is simple. :wink:
When I try to run it I get:
The is no application associated with "00unhide". Run the application first, then open this file from within the application.
Click to expand...
Click to collapse
Please post the link to the exact file so I can download and test it.
I just got it working...
After I downloaded the .cab, as I have WinRar I thought that it was something that needed extracting and it didn't!
http://forum.xda-developers.com/download.php?id=567
that's the link anyway, but it works perfectly!
Sorry for being such a idiot
No problem, hope its all sorted for you now.
is there any way of getting the cab files from the exteneded rom without upgrading it?
running imate 172---------want the orange uk exteneded rom files.
tried upgrading or down grading but getting error country code
You mean to update the ExtROM without flashing?
use the ExtROMTools (as found on this forum)
It allows to unhide & unlock the ExtROM. When undidden & unlocked you simply change its contents. After locking it you simply hard-reset to see the miracle take place . . .
hi
ive dun that'but can not up or down grade my xda2.
And i want the new orange exteneded rom file without upgrading is there anyway of getting them out of the updates files(nbf files)without flashing it?
Just want to upgrade my exteneded rom---but i need the uk orange rom files
With er2003edit (to be found on this forum) you can open the ms_.nbf (the upgrade file that contains the extende ROM).
(remember: do choose the type of romfile. The password of the file is 0x20040305 (enter when asked))
Then you just extract the contents from there to any folder on your pc. from tere on you can manage yourself (using extROMTools)
hi again tried that just get a error message
Looks like you did NOT chose the rom type in the last combo-box of the file-open dialog.
The ER2003Edit autodetect feature DOES NOT WORK.
hi again
just tried it again and it does not give me the option ?
please help
when you select the file you want to open, in the file type selector you have "WIN2003 autodetect ROM (*.nbf)" enabled by default, but you can select in the list the OS, Radio or Extended ROM file type.
Select the one you are using and do not let autodetect, as edsub says it does not work well.
Also, use the correct password, probably 0x20040305 for the ms_NBF file
If you choose File / open ROM Image
You get the attached window.
In the indicated combo-box (see red elipse) make sure to choose "WM2003 Extended ROM".
Then select the correct ms_.nbf
If asked enter the password / key.
thank you
got there in the end
So is there a way I can do this on my G4 8125? I've been trying, but have not been successful.
Extended ROM basically consists of large number of CAB files. Go to the ftp and get hold of some of the ROM packages in ZIP format and unzip the EXT rom. Unlock your EXT ROM and replace everthing with the one you've downloaded. Done.
Personally, I don't use Ext Rom. Upon hard reset, I just skip the Ext Rom installation and I install my stuff manually, which I think gives more flexibility. I had my phone backup-ed into an EXE file which I can use when I hardreset next time.
I don't know how to unlock it, and I can't even stop my Cingular one from installing every time.
To stop it from installing, upon hardreset, softreset your phone just after the security option (eg when it asked you to set your PIN for the phone). It should skip installing the EXT ROM.
I'm not sure if it is read only or not, but you can try. Download and open Total Commander (for PPC), at the top section of TC, enter this
Code:
\Extended_ROM
It will show you stuff in your Ext Rom. See if you can overwrite it.
If the extended_rom is protected like in G3 >2.xx SPLs then you have no luck there. Even if you change something and it looks like it worked you'll get bad checksums on next soft-reset and all data in extended-rom will be deleted
mestrini said:
If the extended_rom is protected like in G3 >2.xx SPLs then you have no luck there. Even if you change something and it looks like it worked you'll get bad checksums on next soft-reset and all data in extended-rom will be deleted
Click to expand...
Click to collapse
exactly what happened to me.
after it had bad checksums, strange characters and folders, i formatted the extemded rom using wizard service tool ver 4.2.1
now my extended rom is empty... but i have a copy of it on the PDA in a different folder and on my PC.
Is there a way to restore it?
royorlev said:
exactly what happened to me.
after it had bad checksums, strange characters and folders, i formatted the extemded rom using wizard service tool ver 4.2.1
now my extended rom is empty... but i have a copy of it on the PDA in a different folder and on my PC.
Is there a way to restore it?
Click to expand...
Click to collapse
Absolutely. Simply use WST and select the "Write ROM" option. Then select "Extended ROM" and upload the backup from your PC.
Hi All,
Is there any way to build own ExtROM?
Thanks
Hi all, I'm trying to make Fido Call Display to work on my Device, and I found the solution here. However the solution requires me to cook the rilphone.dll file into the ROM that I'm using (NAFT's v2.3). I've never cooked a ROM before and I'm far from understanding the procedure, but I don't think it's that hard to add a file in a cooked ROM. Can you guys help me out with this?
Please show me how to add/replace rilphone.dll in NAFT's v2.3 ROM. Thank you.
Replied on other thread
Da_G said:
Replied on other thread
Click to expand...
Click to collapse
Da_G said:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..
Pretty much leaves the only option as cooking it in, unless you are already using a ROM with a modified nk.exe in XIP to disable certificate checking.. then you can just drag and drop rilphone.dll and reboot.. but since stock ROMs are not modified in such a way, you cook it in, as all files cooked into ROM are trusted..
Unfortunatly there is no way to modify XIP without cooking either.
If a ROM is unprotected (still has it's rgu's) - download a ROM kitchen for your device.. extract the rom of your choice.. replace rilphone.dll in \OEM\OEMDrivers.. then re-assemble the ROM.. no registry manipulation needed.
For the raphael ROM kitchen, name your ROM "RUU_Signed.nbh", put it in \BaseROM
Run RaphaelKitchen.bat
select "e" for extract, then "a" for "From RUU_Signed.nbh"
let it go through its motions, when it's done replace rilphone.dll in \OEM\OEMDrivers
again in RaphaelKitchen.bat select "cf" then "b"
click "BuildOS" tab
click "Load ROM" button
navigate to RaphaelKitcken folder (has subfolders OEM, ROM, SYS, etc), press ok
click green "Go" button
when done, close the window
again the kitchen will go through some motions, when it pops up XVI32 and says "Page Pool Changer" in the command prompt window simply close xvi32
now it should prompt to flash to your device.. and you're done
Click to expand...
Click to collapse
Ya, I tried it with NAFT's v2.3, but it seems that the file is protected... the file can't be read.
I'm not sure I understand, you tried to cook the file into ROM and it gave you an error about it being protected? Or do you mean you tried to copy the file to the device, and it wouldn't let you overwrite? If that's the case that's why I suggest renaming rilphone.dll to rilphone2.dll before you copy to device, and then change the registry to point to that.. that way you don't have to overwrite the file that's already on the device.
Da_G said:
I'm not sure I understand, you tried to cook the file into ROM and it gave you an error about it being protected? Or do you mean you tried to copy the file to the device, and it wouldn't let you overwrite? If that's the case that's why I suggest renaming rilphone.dll to rilphone2.dll before you copy to device, and then change the registry to point to that.. that way you don't have to overwrite the file that's already on the device.
Click to expand...
Click to collapse
i tried what you told me to do on the other post; Rename the file, and extract it... I have no problem renaming the file, but when I tried to extract it with Raphael Kitchen, I got error like "Cannot read the file" or something like that... here is the dump log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
Click to expand...
Click to collapse
Nothing was extract.
hmm, sounds like the ROM kitchen is having a problem handing the .nbh you fed it, try it with a stock nbh and see if it works..
the rom you are trying to extract may be protected from extraction.
Just to make sure, you are trying to extract the ruu_shipped.nbh in \baserom.. which is the ROM image, somewhere in the range of 50 to 200mb large..
Da_G said:
hmm, sounds like the ROM kitchen is having a problem handing the .nbh you fed it, try it with a stock nbh and see if it works..
the rom you are trying to extract may be protected from extraction.
Just to make sure, you are trying to extract the ruu_shipped.nbh in \baserom.. which is the ROM image, somewhere in the range of 50 to 200mb large..
Click to expand...
Click to collapse
I redownload the Rom and it seems to work now. I can finally extract it.
As for the rilphone.dll... do you have the right one for Rogers Display? and the one that will work for Fido as well?
edit: I successfully reflashed my ROM, but the display thing doesn't work. Beside replacing rilphone.dll is there any reg I need to change? (can you give me the right rilphone.dll file?
I got the rilphone.dll file here
Sucessfully cooked in NaFT's v3.1, however it still doesn't work. It always show unknown Caller.
any help here would be much appreciated
I will say i haven't searched for this one yet but i probably will a little later if i don't get any quick responses.
Now to my question. I'm trying to create a cab file that i can use to install some registry changes from the performance tweak thread. The file is specifically based on the memory tweak cab file that is available there but because i use the energy standard 6.5.x series roms there are a couple of tweaks that cause the phone to stop booting correctly. So i have extracted all the original files and modified the xml file appropriately. I've then recompressed them into a new cab file but if i try to install it i get an "not installed successfully error" so obviously i'm doing something wrong but i have no idea what. Anyone got any ideas?
What software did you use to make the cab file?
I actually first tried to create it with winace and that was the problem. Winace just creates the cab as a storage file and not as an installable cab file. I've since searched coz i didn't get a quick reponse and found quickcab. Did the trick nicely. I've tested it on my phone and i've now posted the finished file in the energy rom thread. You will find it here: http://forum.xda-developers.com/showpost.php?p=8078336&postcount=24318
At beginning I create .caps I used QuickCap (in the attachment). In the .zip for you is the Programm and guide only in german but with pictures. I think you can understand it, its very simple. Now i used the WinCE CapMgr, but you must pay for it, so I can't share.
Bonito77 said:
At beginning I create .caps I used QuickCap (in the attachment). In the .zip for you is the Programm and guide only in german but with pictures. I think you can understand it, its very simple. Now i used the WinCE CapMgr, but you must pay for it, so I can't share.
Click to expand...
Click to collapse
Quickcab did it for me and i will continue to use until it my needs exceed it but i have to say i figured out to use it in about 10 seconds (literally). Kudos to the developers for making a very intuitive and easy to use program. Not many out there that are that specialised and that easy to use.