Jump to content
RealModScene

tbrtbr

Members
  • Content Count

    1
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tbrtbr

  • Rank
    RMS Freshman
  1. Worked like a charm. And i was very hesitant, i spent very little time with these things before due to work/family. I had an "off-the-shelf-RGH" and no apparent knowledge so far.. Updating Dashlaunch was easy, I had an 16197 kernel and 3.04 DL on the machine, together with the newest FSD3. i have a Corona Slim 4 GB with additional 320 HDD internally, 2 TB USB on backside USB and 16 GB USB stick in the front. I unplugged the internal HDD and the external HDD because all coming stuff had to go on my internal 4 GB MU and i prefer things to not fuck up ... All i had to do was put the DL 3.09. on a USB-stick and start the .XEX via FSD3. It kept my previous launch.ini and after the update started directly to FSD3. I started Dashlaunch again and started die update-manager, leaving DL running. Xebuild worked like a charm, my corona is wifi-connected by fritzbox router. It found my box directly and it took 19 seconds for the whole process. After restarting i saw that DL had survived, but in FSD my avatar was naked. I was a bit confused but found a solution here in the forums. I downloaded the update from XBOX.COM/update and put it on the usb-stick after renaming $systemupdate to $$ystemUpdate. it didnt work first time because i forgot to change the u to U in the foldername... I swapped to METRO dash, inserted the usb-stick and started the required update. Everything works like a charm. GREAT TUTORIAL and GREAT SOFTWARE!!! BTW: GTAV ran perfectly with my 16197 kernel ...
×
×
  • Create New...