Error while loading ROM from CoreProKitchen... (not "HELP! I'M STUCK IN BOOTLOADER!") - 8125, K-JAM, P4300, MDA Vario ROM Development

Error while loading ROM from CoreProKitchen... (not "HELP! I'M STUCK IN BOOTLOADER!")
Okay, so I added my packages, etc and followed all the steps, everything worked up until the point where I flashed my phone. When it get's to 98% my computer pops up with the following error message:
-----------------------------------------
The instruction at "0x00405e9b" referenced memory at "0x0018a000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------------------
I'm back up and running, but I would really like to use my rom. Any idea how to clear up this error and get this baby flashed?

inneyeseakay said:
Okay, so I added my packages, etc and followed all the steps, everything worked up until the point where I flashed my phone. When it get's to 98% my computer pops up with the following error message:
-----------------------------------------
The instruction at "0x00405e9b" referenced memory at "0x0018a000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------------------
I'm back up and running, but I would really like to use my rom. Any idea how to clear up this error and get this baby flashed?
Click to expand...
Click to collapse
Mabe you put too many files in the ROM ... how big is the nk.nbf ?

The nk.nbf is 60,161KB... that's smaller than some of the other nk.nbf's I have seen.
Anything else it could be? Redid the whole process, flashing again...

For an OS only nbf the file should be around 57/58MB - sounds to me like you over filled the ROM.

On XP if you put your mouse over the nk.nbf and it shows its bigger than 57.3meg then you will not be able to flash it as its too big (thats for a rom with OS, and splash screens. If you don't have splash screens I think its like 57.1). The other way to check is right click and choose properties on the nk.nbf. Look at the size (not the on disk size).

Thanks... I guess I overstuffed it... I didn't think it had all that much in it... oh well.

inneyeseakay said:
Thanks... I guess I overstuffed it... I didn't think it had all that much in it... oh well.
Click to expand...
Click to collapse
Try to optimise some big executables. That will surely give you couple of spare MB

Up and running now!

Related

Please please please help me upgrade my MDA...

I've searched and searched to find a post that tells me straight to the point how to upgrade my MDA but I just can't find one.
I've got the XDA Developers FTP loaded up in FlashFXP but there seems to be a lot of empty folders on it.
Can someone please tell me if there is a guide on here of exactly what I need to do to upgrade the unit? I followed some advice to fix my Bluetooth problems on here and now my whole MDA has stopped functioning properly... the Today screen just shows all strange graphics etc but I still have the upper and lower menus.
If there is no guide, can someone please tell me what I need to do... my business relies on my MDA! :roll:
ewg_uk said:
I've got the XDA Developers FTP loaded up in FlashFXP but there seems to be a lot of empty folders on it.
Click to expand...
Click to collapse
Well, there seems to be a very very very very very funny guy of girl who has deleted most of de maps of de the Magician. Again, very very funny, we're all lauging very loud. (or is it a manifacturer??? QTEK?, iMate? T-Mobile? Who's the bad guy?
ewg_uk said:
the Today screen just shows all strange graphics etc but I still have the upper and lower menus.
Click to expand...
Click to collapse
Maybe there is a solution: someone else had the same problem (I think, he also had a corrupted Today screen), but after he chose a different picture in the today screen the problem is solved.
Not good about the files Whoever it is has just cost me an awful lot of money so I hope they feel great!
Screen issue is now solved thnks to the picture thing but my Bluetooth will not function at all now... was asking for me to turn flight mode off when it wasn't even on and now it doesn't work full stop.
ok this a small guide i made for a friend..... i'll post it here
ok first thing to do is get the ROM file.
second... after you download the file... extract the zip into any
place you want you will end up with an .exe file... right click on the
exe file and choose extract ( not you need winrar to do that) and
after you extract you will find a bunch of files one of them is named
ROMUpgradeUt.exe or (MaUpgradeUT.exe) replace this file with this one
http://forum.xda-developers.com/download.php?id=4022
after you replace the above file, double click on it and it will start
upgrading ... the device will go into bootloader mode (black screen
with Serial 1 written in it) you will get the country error ID
((((DON'T PANIC)))) and DON'T REMOVE THE DEVICE FROM THE USB OR REST
THE DEVICE, just click Exit to finish. while the deice in the bootloader
mode click on the replaced file and run it again the upgrade process
should go fine................
i will try later to do the guide in a pdf format with pix and more detialed
Okay guys I'm new here too Since I want to get rid of the pink t-mobile stuff and upgrading to a ROM which provides me better camera quality I would like to try a newer ROM version.
But where to get the newest ROM from ftp://ftp.xda-developers.com/Magician/ ? I see extened ROM's but I have been told an extended ROM is a kind of addition to a normal ROM. But where can I find the basic ROM. I've been told that O2 and Qtek roms are the best.

Struck by an MDA brick!!

Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.

Read everyfing i can find on Bigstorage and still no success

Hi I know the big storage hack is plastered all over this forum but i still cant get it right.Some one please help me!
Ive got a magician with rom version 1.13.00 WWE radio v. 1.12.00 (i used to have 1.12.00 but i upgraded it by accident.<I woz finkin of it anyway>)
I fink Ive tried every procedure possible but always have problems but basically this is what ive done:
1.Using OS image tool ive copied my rom to pc.
2.Ive changed the 80 00 00 thingy to b8 01.
3.Ive tried to use the os image tool to write it back t ppc but it comes with a usb/communication error in programme A.Im using this way because I have only 32mb mmc card.
Any help would be much appreciated,
Thanks
wiki
Try the wiki (top right link on the page) & go to the magician section. It contains a description howto patch a shipped-rom, the one you used to upgrade to 1.13WWE, & get BS. Apperently you missed this method.
Cheers, M
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,
Gareth
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,
Gareth
Stop,
You're going in the wrong direction. The BS from shipped-rom method is about patching the provider supplied exe file. & after the patch you run it like a regular rom-upgrade. No SD or MMC involved!!! It's a rom-update via USB like the normal update.
pls read it once again @ the wiki.
ok thanks im trying that now.Im stuck on getting nbfdec to run.Ive extracted it to the unzipped rom folder.I open ms-dos command prompt and drag and drop the .exe on the command line to save typing the path.The program runs but then it crashes.Can anyone help me?
Try putting everything in "C:\BS" saves a lot of typing errors including filename handling.
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks
garethsimpsonuk said:
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks
Click to expand...
Click to collapse
Hi Rod,
To go to C:\BS from your personal doc&settings type on the commandline:
cd \ [Enter]
now you should be in C:\
then type:
cd bs [Enter]
now you should be in C:\BS
Works for other directories too.
Cheers, M
Thanks, that helped me a lot.Ive done everything els now so I converted it back to nbf and then executed the maupgrade_noid.It checked device info then displayed the rom to and from screen and both were blank.I proceeded and it displayed the 'success' screen but nothing had actually happened on the ppc.Ive tried the other upgrade program and the one thats cracked on the site.
Any help would be much appreciated
Thanks
Did you reset after the update process finished? & if so did it boot normally? & if so did you look at the internal storage folder size? Cause that's the only thing that's changed & the ext-rom has disappeared. Oh & you shouldn't see the customization start after a hard-reset...
btw rom to & from shouldn't be blank, pls run the update program without patch cause I think the editing somehow invalidated the shipped-rom. The original upgrade program should work & if so you know what's going on. If the original program fails there might be something with your device.
So start the plain shipped-rom first to find out..
Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8
Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8
The header contains info about romtype & provider name, probably some things more I'm
not sure about. The reason for changing it is to avoid errors like the country id error. With the use of maupgradeut_noid it's less important.
One thing I'm questioning is the reason why some of us have probs with connecting to the, I believe, special O2 services. Some claim there not able to connect anymore... Can some other setting as well. I'm on T-Mobile & everything works fine.
Basically if the upgrade was succesfull, you have an enlarged storage & the rest of your device will be working as before.
Cheers, M
how much space would i have in my main memory now? i have a 64+64 system (O2 Xda Mini) now branded to T-Mobile 1.33 and now applied the new patch (BIG STORAGE) using the Wiki Information guides. However any idea how much FREE space on first reboot i should have.
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
nevermind got it
Total Main Memory - (FREE MEMORY) - 43.99MB Storage / 25.54 MB Programs! woo hoo this is HOT
shivam said:
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
Click to expand...
Click to collapse
First boot takes much more time than next boots.
Have fun, M
all,
look over here.
cheers!
Sorry to say, but it's old news. We got a thread about it for three months now I guess with that method. Problem is you always need to update first & then dump your rom again. & somehow not all dumps are accurate. The brick change with a SD is larger than with a shipped-rom.
M

-[Sticky] maybe - Flashing RUU Error/Solution & Explanation List-

I realize this information is on the HTC website but I have seen alot of questions lately regarding these errors. I decided that maybe, just maybe it might help someone with an error when flashing a rom, radio or splash and they can't quite figure out what the error is referring to. I also figured that this might lighten the load that GSLEON3 has been seeing lately with all of the "HELP, I think I BRICKED my phone" threads that keep popping up. Maybe it will help and maybe it won't but I thought it might be worth a try. I'd like to say thanks to OLI, Jocky, all of the rom cookers, GSLEON3 and XDA. You people make this fun.
I hope this helps someone.
? ERROR [202, 204] : CONNECTION
? This error message will appear when the device is not connected to ActiveSync correctly. Make sure
you properly connect the device to the PC through ActiveSync before running RUU.
? ERROR [206] : MEMORY ALLOCATION
? ERROR [280] : UPDATE ERROR
? When you see any of these error messages, close other running programs on the computer and run RUU again.
? ERROR [208] : FILE OPEN
? ERROR [210] : FILE READ
? These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
? ERROR [212] : FILE CREATE
? ERROR [214] : FILE WRITE
? ERROR [222, 224] : DEVICE NOT RESPONDING
? These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
? ERROR [220] : MAIN BATTERY POWER
? This error message will appear when the device's battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery
when it is upgrading the radio).
? ERROR [238] : FILE READ
? This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
? ERROR [240] : FILE OPEN
? When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again. Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up. Thanks ConfusedSTU.
? ERROR [242] : INVALID LANGUAGE
? ERROR [244] : INVALID MODEL ID
? ERROR [294] : INVALID VENDER ID
? ERROR [296] : UPGRADE ONLY
? One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
? ERROR [246] : DEVICE NOT RESPONDING
? This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
? ERROR [260] : UPDATE ERROR
? This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again.
? ERROR [262] : UPDATE ERROR
? This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
? ERROR [300] : INVALID UPDATE TOOL
? This error message will appear when you use the incorrect RUU version to upgrade.
? ERROR [330] : ROM IMAGE ERROR
? This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Nice one mate, at leat this will give people who flash some idea what to do when or if they get errors flashing.
great find thanks for posting this will be useful for everyone.
Obligatory "thank you" post.
haha ok ok mistake now i see the solutions xD!
edit...............
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Confused Stu said:
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
Click to expand...
Click to collapse
I'll add this to the post. Thanks Stu.
_Alex_ said:
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Click to expand...
Click to collapse
I thought so to but I have had to answer a couple of these lately and was hoping that this might help to clear a few things up.
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
RPG0 said:
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
Click to expand...
Click to collapse
I can make that change.
Thanks for the info pal
helpful! thankx
Wiki
Ported to the Wiki
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Ta
Dave
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
iXiR said:
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
Click to expand...
Click to collapse
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
DaveShaw said:
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
Click to expand...
Click to collapse
That's similar to my own schedule. P1 got to have a secret in finding time for this kind of things
ERROR 200
I got this error 200 "get newer update utility" I am using windows vista 32 bit.
where can i get a newer update utility? thanks
I-mate JasJam upgrade error
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
rumjar86 said:
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
Click to expand...
Click to collapse
Try resetting the phone and the computer to make sure that no other processes are running. Then try putting phone into bootloader, and when sync'd try flashing from there.

lightest rom

what rom is the lightest english rom?
josefcrist said:
what rom is the lightest english rom?
Click to expand...
Click to collapse
Would be the rom produced from Ivan's Justme kitchen. You got to choose what basic apps you want and end up a lite rom that only contains what you needs exactly.
thank you now can you point me to it?
josefcrist said:
thank you now can you point me to it?
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=408502
But you can search better next time
sorry about 2 minutes after i posted that i found it. thanks for your help but i am getting an error when i run the bat file to build the rom. later i will post what it is on the thread for that rom.
josefcrist said:
sorry about 2 minutes after i posted that i found it. thanks for your help but i am getting an error when i run the bat file to build the rom. later i will post what it is on the thread for that rom.
Click to expand...
Click to collapse
What does the error say? Make sure you've installed the required components. (.NET2.0 and the Microsoft Visual C++ 2008 Redistributable Package.
thank you for your hard work and patience. ok it worked after i installed those two programs. now what do i do? i ran the bat file with out errors and now what?
You build the ROM all the way through? (BuildOS, compile, nb->nbh and all?) Then open your ROMBUILD_JustMe folder and transfer the HERAIMG.nbh file into your cell phone's SD card. You have to HardSPL first before using it. Then reset the phone while holding the camera button down and press the down volume and wait until it tells you that it's done.
On a side note: I didn't realize that I had THAT many posts...
thank you so much for all of your help. i ran the bat file now i have no idea what to do. this is the first time i have done this. what is the next file i have to run? how do i compile it? what spl do you recommend?
You HAVE to HardSPL. As far as what to do, follow the bat file. It's a script. Just follow the steps that are on the screen.
i have no idea what was going on with it but i ran the bat file and it crapped out about halfway though before my nbh file was built. but then it all of a sudden started to work. i just finnished hard spl on my device no i am coppying the 4 files in the storage card
4 files? shouldn't there be only one?
sorry my post got cut off but thank you so much it works very well. i kinda wish the wing had more ram but the rom is not going to change that. i only had to install 2 things that you did not have. windows live for hotmail and a good battery meter. thanks again for all of your help
More RAM? How much are you getting? (The phone only has 64mb so with having Windows Mobile running, you can only get so much free.)
my phone says total 43.78 and with just windows running i have 12.42 free what about you?

Categories

Resources