RGH Updating to Dash 17150 on RGH1 Jasper CB 6750

[rghabc]

Hi I just installed RGH 1 to my Jasper CB 6750, 512 mb, with a Coolrunner REV B. I was on dashboard 12416, after a bit of confusion and some crashes in Jrunner I ended up with the 14699 dash, which is the newest dash to be compatible with RGH 1.

My question is, if I update using Xebuild and such, my dashboard, flashing the NAND and all that, to dash 17150, will I lose my RGH? or will it turn into RGH 2 (I heard RGH1 boot times are better than RGH2). If it does become RGH2 will I have to do more soldering or more tinkering with the NAND-X to make the installation compatible with RGH2.

Thank you

 

[nofeloniesyet]

Hi I just installed RGH 1 to my Jasper CB 6750, 512 mb, with a Coolrunner REV B. I was on dashboard 12416, after a bit of confusion and some crashes in Jrunner I ended up with the 14699 dash, which is the newest dash to be compatible with RGH 1.

My question is, if I update using Xebuild and such, my dashboard, flashing the NAND and all that, to dash 17150, will I lose my RGH? or will it turn into RGH 2 (I heard RGH1 boot times are better than RGH2). If it does become RGH2 will I have to do more soldering or more tinkering with the NAND-X to make the installation compatible with RGH2.

Thank you

freeboot dash and retail dash are 2 diff things totally.you can build a rgh1 dash img for 17150 and youll be fine.just use updserv read page 22 of jrunner pdf

 

[rghabc]

freeboot dash and retail dash are 2 diff things totally.you can build a rgh1 dash img for 17150 and youll be fine.just use updserv read page 22 of jrunner pdf

Thank you very much, I thought it was something like that, I'll keep my current dashboard until I get my new 2.5" HDD and then I'll update it. I looked at the Jrunner guide, but I think I'll go with some youtube tutorial that uses Flash 360, looks simpler.

Thanks again

 

[nofeloniesyet]

Thank you very much, I thought it was something like that, I'll keep my current dashboard until I get my new 2.5" HDD and then I'll update it. I looked at the Jrunner guide, but I think I'll go with some youtube tutorial that uses Flash 360, looks simpler.

Thanks again

i highly doubt that that method is easier than simply plugging up ur 360 to the local network,running dashlaunch,and enabling updserv,then one click in jrunner bam its updated.and less risk of messing it up than with flash360.but its ur box do it how ya want.

 

[rghabc]

i highly doubt that that method is easier than simply plugging up ur 360 to the local network,running dashlaunch,and enabling updserv,then one click in jrunner bam its updated.and less risk of messing it up than with flash360.but its ur box do it how ya want.

So, I got my hard drive today, and started the update proccess with J-Runner (I have FSD 775 and Dashlaunch 3.14 (571), this is what I did, enabled updserv in DL, in Jrunner loaded in Source my nanddump, previously I went to Advanced>Get latest System Update, went to Patches/Dashlaunch tab and checked "Use Dashlaunch" and "Include Launch .ini ?", then in Update Mode tab it says 1750, I clicked Update, and the log says this:





WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Select Load Nand to open the folder: C:\Users\Pedro Miguel\Desktop\my jasper\J-Runner v3 (5) Core Pack\417942194105
Initializing nanddump1.bin..
Jasper BB
Glitch Selected
Nand Initialization Finished
Finished Checking Files
Load Files Initiliazation Finished
17150
Started Updating Console to 17150
---------------------------------------------------------------
xeBuild v1.14.693
---------------------------------------------------------------
base path changed to C:\Users\Pedro Miguel\Desktop\my jasper\J-Runner v3 (5) Core Pack\xeBuild
---- { Update Mode } ----
***** WARNING: reusing folder C:\Users\Pedro Miguel\Desktop\my jasper\J-Runner v3 (5) Core Pack\output\!
started, watching network for xbox...success, found xbox beacon at 192.168.1.101
connected to Jasper with updsvr version 3 (peek version 0)


*****ERROR: console hv patches are not recent enough to support update mode!


update console patches and reboot before trying again.




***** FATAL UPDATE ERROR: unable to parse info reply from console!


---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Failed


What can I do?

 

[15432]

it seems, 14699 kernel is way too old for updserv thing.. build image manually

 

[nofeloniesyet]

it seems, 14699 kernel is way too old for updserv thing.. build image manually

yea we figured that out last night. see this thread .