Develop Bugs

Why my SPV5000 don't want 1.30 rom ?

Hi, i have a SPV5000 and i can put a lot of kind of 1.13 rom inside, like Qtek or Orange.
But impossible to put any 1.30 rom (orange, qtek french or WWE).
I've tried a lot of solution like "put the radio first" ... rest after.
Do you know if it's possible that my hardware version refuse this 1.30 rom?
I think the guy who sell me the spv sell me a pre-serie .
Thanks

The first question I want to ask is: How do you perform the upgrade? Do you use the No ID Tool? If not, try using it. Here is an instructions I made:
The file is extracted in your computer. Once you run the shipped.exe file, you need to go to:
My Computer
Your Drive (mine is Drive C)
Show the contents of this drive
Documents and Settings
Choose your folder name
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
Now go to TEMP folder
Now you will notice a bunch of folders will show up, tons of them to be exact. What you need to do now is click on the shipped.exe file again and "LOOK" for the folder being created because that folder is what you want to copy. If you did not see it created, you have to manually open each folder and look for the files I listed below.
Assuming you found the folder, you will have these following files inside that folder:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
If the file MaUpgradeUt_noID is not there. You need to get hold of a copy of this file as you need this.
There you have it, REMEMBER, you need to have the MaUpgradeUt_noID file plus all the rest of the file in one folder if you want to upgrade to the ENTIRE I-Mate ROM, QTEK, O2, or whatever ROM you want.
If you only want to upgrade to the radio version then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf" alone and click on the "MaUpgradeUt_noID" file to initiate the Radio installation. Basically those 3 files control what you want to update on your device.
Hope my instructions were clear enough for you. Hope this helps.

Thanks for your complete response
Of course i'm using the MaUpgradeUt_noID ... i have no error message during the process but at the end after the hard reset i have black screen.
and to try to only flash the radio I renames other files .
thanks
I steel don't enderstand ....

Do you think the bootloader version is important ?
i have the O.56

SEB152030 said:
Do you think the bootloader version is important ?
i have the O.56
Click to expand...
Click to collapse
It won't hurt to try and update using Boot Loader Mode.
What do you mean "0.56"?

when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56

SEB152030 said:
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
Click to expand...
Click to collapse
You might be right. Your exec must be one of the earlier version. I remeber some time ago, someone asked the same question you did. Maybe someone else can help. Have you tried upgrading it using my instructions?

thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....

SEB152030 said:
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
Click to expand...
Click to collapse
I believe you need to find out how to upgrade the "Serial USB" application on your Universal for the No_ID Tool to work. Other than that you probably need a version of the No_ID Tool that works at an earlier version of the "Serial USB" version that you have. I'm sorry too, if I didn't help.

Instruction Guide For The Htc Universal Rom Upgrading

1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
2nd STEP: You need to get a hold of the ROM file so you can extract the necessary files from it. This is provided by the phone manufacturer.
****To extract the file, someone recomended WinRAR. If you don't have it, follow this: Go to
My Computer
Your Drive (mine is Drive C: )
Show the contents of this drive
Documents and Settings
Choose your folder name
Local Settings
Look for the "Temp" Folder
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
3rd STEP: You need to extract the following files namely and add the MaUpgradeUt_NoID.exe File. These 10 files are found in one of the folders within the "TEMP" folder after running the file you got from Step 2.
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
*****You need these 11 files if you want to upgrade the ENTIRE ROM.
*****If you only want to upgrade to the RADIO VERSION then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf". So there are 9 files on it.
NOTE: The "TEMP" folder has many folders within it. It is your job to look which folder was created upon running the .exe file from step 2. You need to copy those 10 files and paste them on a new folder.
4th STEP: After gathering the necessary files and choosing which part you want to upgrade and keep, you need to put your device to boot loader mode by pressing 3 buttons simultaneously:
Power Button
Backlight Button
Reset Pin
5th STEP: Plug your Universal via USB. Wait for your computer to recognize a newly plugged device.
6th STEP: Now you are ready to upgrade. Double click the MaUpgradeUt_NoID.exe File to run it and follow the on screen instructions.
Hope this helps. Good luck.

Hi...
Nice guide indeed..but u forgot one important step....that is hard resetting after the complete upgrade... :lol:

I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.

Thanks for the input guys. I also remember, I did not perform a hard reset myself, just a soft reset at the end. But I choose not to include that on the steps as the computer will show a window as to what you're supposed to do or press during the upgrade anyway.

great post!
AG

radio version? Windows Mobile version? and EXT Rom?
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,

Re: radio version? Windows Mobile version? and EXT Rom?
tmglobe2004 said:
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Click to expand...
Click to collapse
I have tried all ROMs that came out on this site. The ones I recommend are only 2:
1st: QTEK's latest ROM
2nd: JWright's Modified ROM
From my post above these 3 files determine which part you want to upgrade:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
If you look at my signature below. I am using TMobile's Radio while using JWright's Modified ROM. It all depends on you which combination you feel is more stable. On my Universal, I never had any troble no matter what ROM I used, but these 2 I listed above surpasses any ROM released by other manufacturers on my opinion.

Pantaloonie said:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Click to expand...
Click to collapse
Yeah I heard the same thing, I did a soft reset after installation and it worked fine.

error 120 country id
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota

artcsmota said:
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
Click to expand...
Click to collapse
What 3 files? If you are referring to the .nbf files, none of them are responsible. Follow the instructions above and keep repeating them, sometimes it takes more than one try for the Error 120 to disappear according to some who experienced it.

cktlcmd said:
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
Click to expand...
Click to collapse
A great post, Upgraded my O2 Exec using your procedure, worked a treat, Thank you!
Wooky

cktlcmd said:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
Click to expand...
Click to collapse
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here

resetting
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav

xiasma said:
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
Click to expand...
Click to collapse
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.

mavrik64 said:
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
Click to expand...
Click to collapse
YES, if you perform a hard reset. The new upgraded ROM will be the default ROM restored on your device.

cktlcmd said:
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
Click to expand...
Click to collapse
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
I've now ran the T-mobile ext ROM upgrade, hard reset.
When the \extrom autoruns, should I just select T Mobile UK? Or cancel?

xiasma said:
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
Click to expand...
Click to collapse
I think you are doing what I was when it finaly clicked.
By the way, thanks to cktlcmd for the breakdown of the process.
The bit you will need to understand is that when you run the .exe, it unpacks the files into a folder in the Temp directory cktlcmd mentions. All i did then was to search for one of the files listed and i found the folder that way. I then copied the files into a more convinient folder and added the MAUpgrade as per the instructions. Once i did this, running the MAUpgrade does as described.
I know this may seem a bit long winded, but I got there in the end. Also, by saving the contents of the folder elsesware means I can play with it later as also discribed by cktlcmd.
The JASJAR rom is sofar great.
Thanks for all your hard work cktlcmd
regards
Mav

i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks

fuhayer said:
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
Click to expand...
Click to collapse
Have you tried my instructions yet? Try downloading the files again. Sometimes they get corrupted.

it is fixed by flashing with original t-mobile 1.30.232 rom.
but when i flash ivanb14 it is again freezing at 19% of stage3.
what can be the problem ? i have downloaded the ivanb14 rom 3 times and i receive the same error message.

how do you reinstall tilt software

ok heres what happened first i installed hardspl and then i changed my radio to 1.27.14.09 and when i restarted my att tilt the att stuff went on then nothing it never went to the main screen, now how can i reinstall a radio or just the att stock software without using activesync

Go to the bootloader - check the wiki for instructions. Connect your computer to the Tilt - you should see "USB" below the tri-color screen. Install the new ROM or radio. PM me if you have problems.
P.S. The answers to any problems you find are readily accessible in the Kaiser section.

shrshr429 said:
ok heres what happened first i installed hardspl and then i changed my radio to 1.27.14.09 and when i restarted my att tilt the att stuff went on then nothing it never went to the main screen, now how can i reinstall a radio or just the att stock software without using activesync
Click to expand...
Click to collapse
Check the wiki for sd flash. You kan rename the nbh file to KAISIMG.nbh and put it on a sd then goto bootloader and it asks you to install.

im sorry what's wiki and also I can't find software that will let me download the software without activesync does anyone have a link I can use

http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
You should be able to find everything you need here.

i tried everything there, theirs just one problem i cant find a rom that i can use without activesync does anyone have one

When you attach the cable and go to bootloader - does it say "USB" below the tri-color screen? If so, you have communication and can flash.
What do your three lines say at the top of the bootloader (red section)?

it does say usb my computer is reading the phone i just cant find a rom that doesnt use activesync, nothing with RUU_Sign.nbh, i did use hardspl the 3 lines say
KAIS1*0 MFG
SPL-1.0.01iPof
CPLD-8

i do have a microsd card i can try and upload it through their but there is stil the problem with no activesync

so can anyone help me here

ok, since i never really seen this question answered directly anywhere, you get this freebie
how to extract the RUU_Signed.nbh file
If its a cooked rom, the file you download will *usually* be a .rar file, extract the contents with winrar. depending on how the cook packaged it, it may not be named RUU_Signed.nbh, but it will still be a .nbh file
If its an original shipped rom, the file you download will be a .exe file, again, extract the contents with winrar. There will be a bunch of files and the RUU_Signed.nbh will be one of them.

if i downlaod the original rom it just opens up a program to install it how can i extract it without using the program to connect to my phone

omg!!!!!
1. install winrar
2. right click on the file you downloaded
3. choose "extract here"
then do the flashing using the microsd card

How to I install NFSFAN's Bell ROM??

I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks

1)after you download it just extract the file in a new folder
2) Then goto that folder and u will "ROMUpdateUtility" double click on that.
3) just follow the instructions that appears on your computer screen after.

I'm thinking he probably doesn't have WinRAR.

loll thenn ill add another step:
4) download WINRAR and extract the files.
then follow my other other steps.

Do the CDMA Roms require a HARDSPL to flash them? I want to flash a CMDA NSFAN Rom to my friends Vogue and I dont see an stickies for flashing a CDMA rom. I normally spend most of my time in the Kaiser/Raphael Forums.
Any help is greatly appreciated.
Thanks,
Daniel

So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel

atomixpaintball said:
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
Click to expand...
Click to collapse
You are correct, but you do not need to do steps 3 thru 5. After you extract the ROM on your desktop simply doubleclick the RUU utility and it will update your ROM. (you must still be connected via USB to computer) If you want to flash from your storage card instead then do steps 3 thru 7.

I have a bell phone,
and the color screen says .36 and Security Unlocked.
do i have to unlock the phone still ?
its a bell phone, and it was like that when i got it.
does this mean its unlocked?

latinjig said:
I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=3680838&postcount=2
Detroit Doug

By the way, who needs WinRAR when you can get 7-Zip, the best all-around file compression/decompression tool around! And it's free. Opens almost anything out there all in one program.
http://7-zip.org/

hey..
i just had a quick question.. is it possible to switch back to the original BELL rom after you upgrade to NFS rom? i know a lot you might think why would you even wanna do that? But I was just wondering just incase..

Absolutely very easy just flash it like the instruction of a stock rom would require you too

LG Fathom / VS750 kitchen and tools

Hi guys, here's some stuff for you to play and cook custom roms for your beloved(?) fathom.
I'm sorry for the delay but I really couldn't release those tools before.
Please note that I don't have a tool to decrypt other roms. To decrypt those vs750 roms, I had to hack the flash procedure, using an ARM disassembler attached on the flashing tool during a flash. It took me almost 2 weeks to find out a way to get decrypted files without bricking the phone, so hopefully you'll enjoy this and will build great Fathom roms.
Special thanks to trueg for experimenting/testing these tools.
So what do you need ?
- the last lg kitchen (available here)
- a decrypted rom (v5 or v7 available the the bottom of the kitchen's 1st post)
OR
- a full vs750 v7 kitchen (everything ready to cook)
mirror : bad upload, back soon
*****************************
Full vs750 v7 Kitchen info :
- SYS is already extracted (in 21000 folder)
- XIP is already modified to work with erviuskitchen (no more dsm files)
- OEM is stock v7, nothing more, nothing less
Build Procedure :
- Add your packages to EXT folder as usual
- Launch erviuskitchen.exe
- Select vs750, 21000 for ext, sys, xip
- Choose the packages you want to add/remove
- Check 6.5 aku and build rom
- Launch start.bat
- Select vs750 (9)
- Hit "u" to build rom.bin (you must use "vs750" as the beginning of the file name)
- flash it as described below
*****************************
Now the steps to flash the phone :
1- Install drivers
- LGUnitedMobileDriver_S4981CAN33AP22_ML_WHQL_Ver_3.3
- LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0
- LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0
You should easily find them (or more recent version) using your favorite search engine.
2- Install the flash tool
The only one that I know of being able to flash decrypted roms is LGNPST. Sorry, you'll have to search for it on the web (shouldn't be too difficult to find).
If using lgnpst, you'll also need to register this dll (using regsvr32 vs750.dll in a dos command prompt)
3- Connect the phone
To be able to connect the vs750 to lgnpst, you have to be in composite mode (on the phone, go to "settings/connections/Switch usb" then select "VzAccess Manager", click "save" and finally wait for it to reboot.
It's possible to flash this phone in emergency mode (if anything goes wrong and the fathom doesn't boot), but if you do so, you might lose your nv (and MEID info). To boot in emergency mode, shutdown your phone, unplug it, then press the "5" key on the keyboard and while keeping it down, plug the usb cable.
Don't do it unless necessary.
4- Save NV (just to be able to recover in case of problems)
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe, it should detect your phone (filename on the top right panel should be "VS750.dll").
- Click on "phone settings", wait a few secondes for a new window to appear
- Click on read button
- It will create a VS750_COMx.nvs in C:\LG Electronics\LGNPST
- Close the windows and click on "click here to continue".
5- Flash the Rom
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe
- Go in provision Tab (should be selected by default)
- Select Upgrade
- BIN file : "c:\VS750\BIN\VS750XXX5.BIN"
- Check SCR File, then select "C:\VS750\SCR\VS750VZ7_04.scr"
- Check PRL, Nam1 (uncheck nam2), select "C:\VS750\PRL\58006 - EVDO OEM Factory Default.prl"
- Don't check Eri file
- Click on "start"
- Keep fingers crossed for approximately 10min. The phone will reboot a few times, this is normal.
- Enjoy your 1st VS750 custom rom
Also note that for lgnpst to accept your rom, its name will need to start with "vs750".
And don't worry, there is almost no risk of really bricking the phone (especially if you saved the nvs).

I can confirm that you don't need to be too concerned about bricking your phone. As long as you can boot in to emergency mode and you have a backup of your NV data (made with LGNPST - it's very important that you do this - heck make two copies) you can recover it from an unbootable state.
TrueG

Would you be able to provide a pre-configured pack for the Fathom? I am trying my best to figure out how to get the kitchen working, but I haven't gotten it to fully work.
Thanks in advance.

-EDIT- I need to go back to school and learn to read - I saw LGNPST written 3 times, but only 1 was the program. The other 2 were component addons for it, all 3 having version numbers attached to the filename (hence my confusion lol).
@Pizzaboy: I'll help out with getting a filepack together. Which version of windows are you working with? Win7/WinXP, 32bit/64bit
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit

I run 7, both 32 and 64. My main dev is a 64bit system, and my porta-dev is a 32bit.
I've tried following the directions on the kitchen page, but I can't seem to get the XIP to work. It throws errors when I have to start pushing buttons.

da_reeseboy said:
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit
Click to expand...
Click to collapse
XP 32bit
TrueG

I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.

da_reeseboy said:
I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.
Click to expand...
Click to collapse
If you get something working on XP, i'll be able to get it working on 7.
I'm mostly lost on getting the V5 ROM set to work in the kitchen. I've never done a ROM before, and most of the tutorials are either really long and confusing, or really short and confusing...

Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?

da_reeseboy said:
Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?
Click to expand...
Click to collapse
When i hit step 9 in the Kitchen walkthrough, I push "realloc p" and it throws errors. Then when I get to the kitchen, it can't see the XIP and won't let me build a ROM.

@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.

spocky12 said:
@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.
Click to expand...
Click to collapse
could you make a v5 one too? V7 has too many bugs to make it a base personally.

Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.

spocky12 said:
Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.
Click to expand...
Click to collapse
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?

pizzaboy192 said:
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?
Click to expand...
Click to collapse
Totally possible, we just need to have a working base to start from.
Thanks Spocky for the uploads.

I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.

pizzaboy192 said:
I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.
Click to expand...
Click to collapse
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.

da_reeseboy said:
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.
Click to expand...
Click to collapse
I wonder if we could hybridize this... Take the OEM stuff from the V5 rom and the XIP from V7... would it work?

It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.

da_reeseboy said:
It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.
Click to expand...
Click to collapse
I'm waiting for files to copy on my netbook and I'll see what happens and if the ROM builds.
I'd be a little cautious of drivers, as there's some reason that there were so many issues with the 3G connection dropping on the V7 rom, I'd want to pin it on the WWAN drivers...