nueSPL-2.47 - Page 10

petvolnj · #91 (**permalink**) 08-27-2008, 09:42 PM

Can anyone help this noobie? Trying to run the nueSPL-247 on my VWZ XV6700 and when clicking on .exe I get the following error: The file 'nueSPL-2.47' cannot be opened. Either it is not signed with a trusted certificate or one of its components cannot be found. Can this phone be upgraded????

**puff** · #92 (**permalink**) 08-28-2008, 04:38 PM

Quote:

Originally Posted by petvolnj

Can anyone help this noobie? Trying to run the nueSPL-247 on my VWZ XV6700 and when clicking on .exe I get the following error: The file 'nueSPL-2.47' cannot be opened. Either it is not signed with a trusted certificate or one of its components cannot be found. Can this phone be upgraded????

This is designed for the Titan not the Apache

OffUrRcker · #93 (**permalink**) 09-01-2008, 09:00 PM

So I'm in an interesting situation. I have a cloned ESN, courtesy of the MFG tools provided by bootloader 2.4. I figure hey, perhaps my GPS locks can be improved, and proceed to follow this guide, flashing the new MF1 update, and then relocking and downgrading to 2.09, (at which point my ESN reverted because I no longer had an unlocked SPL) and then I decided to try a little trickery, and first flashed to 2.4 and rewrote my esn, and then went 2.47 and flashed the radio and 20273. My esn reverted again, so I went back to 2.4, wrote it, and that's where I am now.
I know that nuespl 2.47 does not support MFG commands, so I'm pretty sure I'll lose my ESN if I go back to that. Right now, my PRI in EST says it's 2.03, and I just tried to get a lock in my house, and while it searched for forever, it eventually told me I needed a clear view of the sky.

When 2.03 is blocking other applications out of the GPS API, what error message do they get? No GPS found, or location unavailable?

OffUrRcker · #94 (**permalink**) 09-01-2008, 09:09 PM

NVM it's working. I didn't do the QPST gps fix because I did it a long time ago and thought it would have stuck. I just did it, and got a lock inside my house in under 4 seconds flat, from a cold boot. Unbelievable.

SO, for future reference, SPL 2.40 is fully compatible with this PRI, and if GPS fix is applied, the same benefits can be reaped.

deboy_001 · #95 (**permalink**) 09-04-2008, 11:19 AM

I read the thread and a couple of other people seemed to have my same problem, but didn't really post their solution if they figured it out.

I formatted my 2gig micro SD to FAT32 on windows. I put it in and started the nueSPL2.47... It's checklist said it wasn't formatted, so I let it format. Then I ran it. It went into bootloader, but nothing happens... it just says SPL-2.07No2Chem Titan SPL EVT. It's been sitting there 20 minutes now. I reset and restarted from step 1. Same result. I'm pretty sure I got the 2.47 file, but I don't know why it doesn't wanna work. Any ideas? Thanks in advance

p.s. I'm completely stock w/ the MR1 "update"... for now

**GhettoBSD** · #96 (**permalink**) 09-04-2008, 03:48 PM

So i'm confused, i thought that to install a custom rom (from a stock rom) we had to unlock the phone.

Then to install a stock OEM rom we had to re-lock the phone.

So, which is it lol because someone said it's the opposite

SyXbiT · #97 (**permalink**) 09-06-2008, 03:40 PM

anyone else noticed significantly decreased battery life since doing this?
just curious, cause i am. and i've had the same ROM and apps before and after, so i'm pretty sure it's this

CrazyPhil · #98 (**permalink**) 09-06-2008, 05:07 PM

I fixed my self... phew...

**puff** · #99 (**permalink**) 09-06-2008, 05:36 PM

Quote:

Originally Posted by GhettoBSD

So i'm confused, i thought that to install a custom rom (from a stock rom) we had to unlock the phone.

Then to install a stock OEM rom we had to re-lock the phone.

So, which is it lol because someone said it's the opposite

the first one for sure... to install a custom ROM on your Titan you first need to unlock it

now in regards to returning/relocking:
once you unlock the bootloader w/ 2.40 or 2.47 SPL you shouldnt ever need to unlock again...

should u need to install an OEM Rom to return it, some would worry that the bootloader screen might happen to be checked, or it might be stuck in bootloader, or somthing i dunno - but the point is, if you want to make it look 100% OEM you will need to 'relock' the bootloader back to the standard bootloader... this is what the relock is for... most of the time i see people recommend to flash back to Stock ROM first, then relock.

now have i confused you or made it clear as mud ???

**puff** · #**100** (**permalink**) 09-06-2008, 05:39 PM

Quote:

Originally Posted by SyXbiT

anyone else noticed significantly decreased battery life since doing this?
just curious, cause i am. and i've had the same ROM and apps before and after, so i'm pretty sure it's this

I wouldn't think that this has any effect on your battery life, as its not a ROM (just a bootloader)
You state that you have the same ROM b4 and after, but this is so you can unlock and flash a custom ROM