Jump to content


Photo

Rgh Jasper - Freeze When Opening File Manager


  • Please log in to reply
8 replies to this topic

#1 moshbear

moshbear

    X-S Young Member

  • Members
  • Pip
  • 42 posts
  • Location:Canada
  • Interests:C, C++, guitar, drums, bass, death metal, etc.
  • Xbox Version:none
  • 360 version:v4.0 (jasper)

Posted 10 May 2012 - 06:16 PM

I have an RGHed Jasper 512, where I used xell's updater to write the 64M glitched image. After which, both FSD and official dash freeze when I attempt to open the file manager. Any clue as to why this is?

#2 TheRealJPizzle

TheRealJPizzle

    X-S Member

  • Members
  • Pip
  • 105 posts

Posted 11 May 2012 - 12:07 AM

did you use XeBuild to create you image or one of the crappy gui's ?
also dont use Xell to flash the image if you can avoid it, use NAND Flasher 360 http://www.elitemods.....60 v1.2.0.rar

#3 moshbear

moshbear

    X-S Young Member

  • Members
  • Pip
  • 42 posts
  • Location:Canada
  • Interests:C, C++, guitar, drums, bass, death metal, etc.
  • Xbox Version:none
  • 360 version:v4.0 (jasper)

Posted 11 May 2012 - 03:09 AM

360 Multi Builder 0.83 isn't a GUI. Also, i would've used j-runner, but it keeps on throwing an exception.

Secondly, as much as I enjoy nandpro, xell is faster and does bad block relocation automatically.

#4 TheRealJPizzle

TheRealJPizzle

    X-S Member

  • Members
  • Pip
  • 105 posts

Posted 11 May 2012 - 06:18 AM

use XeBuild, like i said....

#5 steveo1978

steveo1978

    Local Retard

  • Head Moderators
  • PipPipPipPipPip
  • 1,967 posts
  • Gender:Male
  • Location:north carolina
  • Xbox Version:v1.1
  • 360 version:v5.0 (360S - trinity)

Posted 11 May 2012 - 06:56 AM

Multibuilder uses xebuild.

moshbear what do you mean you used xells updater to flash the image? Multibuilder v 0.83 I believe did not have the updated Xell reloaded which had rawflash built in. Also the newest Multibuilder is v 0.93

#6 moshbear

moshbear

    X-S Young Member

  • Members
  • Pip
  • 42 posts
  • Location:Canada
  • Interests:C, C++, guitar, drums, bass, death metal, etc.
  • Xbox Version:none
  • 360 version:v4.0 (jasper)

Posted 12 May 2012 - 12:39 AM

0.93 behaved a bit buggily, so I used 0.83 because it was more stable.

Also, I used xell's updater from the xell in image_00000000.ecc.

#7 steveo1978

steveo1978

    Local Retard

  • Head Moderators
  • PipPipPipPipPip
  • 1,967 posts
  • Gender:Male
  • Location:north carolina
  • Xbox Version:v1.1
  • 360 version:v5.0 (360S - trinity)

Posted 12 May 2012 - 12:54 AM

well stuff is updated for a reason and you are probably using a older xell reloaded so try multibuilder v 0.91 or newer and see if you get the same issue

#8 moshbear

moshbear

    X-S Young Member

  • Members
  • Pip
  • 42 posts
  • Location:Canada
  • Interests:C, C++, guitar, drums, bass, death metal, etc.
  • Xbox Version:none
  • 360 version:v4.0 (jasper)

Posted 12 May 2012 - 09:04 AM

I found the 360 multi builder bug by reading the changelog - on 0.92 and later, when selecting a dash version, it fails to copy the proper smc patchset, thus causing xebuild to whine about failure reading smc.bin. 0.92 and later also don't like cpukey.txt, which consists of just ([0-9A-F]){32}\n.

Whereas with jrunner, it just throws a null ptr/ref exception.

Anyways, with 360MB 0.91, FSD simply freezes after 20-25 seconds. While dash does not freeze, it also does not show the 512 MU under storage devices.

Note: I upgraded directly from stock/8955 to rgh/14719.

Also, the central light keeps on constantly flashing after boot animation is finished.

Edited by moshbear, 12 May 2012 - 09:39 AM.


#9 moshbear

moshbear

    X-S Young Member

  • Members
  • Pip
  • 42 posts
  • Location:Canada
  • Interests:C, C++, guitar, drums, bass, death metal, etc.
  • Xbox Version:none
  • 360 version:v4.0 (jasper)

Posted 14 May 2012 - 09:14 AM

Problem solved: (Memcard[01]|OnboardMU):\\ExtendedSystemPartition was missing due to taking shortcuts with the dash upgrades.

This was the solution:
  1. restore stock 8955
  2. update to stock 14699 via usb
  3. E80 -> update successful
  4. make a retail 14699 with 360 multi builder 0.92, with corrected cfldv
  5. flash retail_flash.bin
  6. boot into dash
  7. format the OnboardMU
  8. do a new 64mb dump
  9. run 360 multi builder 0.94 on the new dump
  10. flash updflash.bin
  11. fsd on (6750 zp / 8453 / 14719)
  12. :D

Note: all flashing and dumping was made by nandpro, since I didn't need xell due to already having the cpukey.

So, in short, the issue was a missing ExtendedSystemPartition due to not updating to stock kinect dash before RGH.

Regarding bad data in cpukey.txt: it was caused by notepad prepending a UTF-8-encoded UTF-16 BOM (U+FEFF).




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users