Thread: nueSPL-2.47
View Single Post
  #83 (permalink)  
Old 07-14-2008, 07:07 PM
joshkeller77's Avatar
joshkeller77
PPCGeeks Regular
Offline
Location: 805
 
Join Date: Feb 2008
Posts: 130
Reputation: 375
joshkeller77 is becoming a PPCGeeks regularjoshkeller77 is becoming a PPCGeeks regularjoshkeller77 is becoming a PPCGeeks regularjoshkeller77 is becoming a PPCGeeks regular
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
nueSPL-2.47 problem

No2chem,

Ok, hear me out, this will make sense and be relevant in a sec.

So 1.20 won't update back to 2.40 after downgrading to test an older radio (3.39), not sure why but it recognizes my phone in activesync with DCD 3.2.2 loaded fine, goes through the cmd window ok, but has an error in the RUU stating that there is a problem with the connection.

The only thing that I can think of is that one time I began the nueSPL update but did not finish as the card that was in was a sdhc so I cancelled out before it asked me to commit. Not sure why that would have been a problem as it didn't complete the flash and never showed the bootloader at 2.47, it has always been 2.40.

Any thoughts on how to clean up the bootloader?

Should I go ahead to nueSPL 2.47 (FYI I am on Verizon)?

Not really worried at this point, but would like to get at least 2.40 back on the phone for the next ROM/Radio upgrade. This could be why 3.39 wasn't flashing right via sd method, right? It would go into bootloader and then say serial (FYI - It was charged, formatted via cmd "format H: /FS:FAT32 /A:1024", and renamed correctly TITAIMG.nbh without double .nbh extension).

P.S. I also posted this on XDA.
Reply With Quote