Jump to content
RealModScene

ronsonol

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ronsonol

  • Rank
    RMS Freshman
  1. @Octal450 Thanks for the updated pack, it's nice to have some options in the 150s. I'll try them and settle on the one that works best. I really appreciate your help.
  2. @Octal450 I think I mostly get short third blinks. When I see a long third blink, it tends to glitch successfully just after that one.
  3. @Octal450 Awesome. It works! I think it might be working better than the one I was using before - but it's at least on par. Hard to tell with limited testing over my lunch hour. I only tried a few attempts so far; To the dash 12, 6 and 4. To Xell 4, and 3. So it seems my ace chip is only happy with the 150's. Thanks for the help.
  4. @Octal450 No worries take your time, the zepyhr isn't going anywhere, will test when you are ready. I am also in the middle of a battle with a Jasper BB that might be glitching but not showing video. Fun times. Thanks.
  5. @Octal450 Absolutely, with the amount of testing you do for us it's the least I can do. Thanks!
  6. Thanks again. I definitely tried those first as they were part of your recommendations. I tried them again and still not working. So not sure what's different about zephyr_150_E_2_L_1. While having, by far, the longest glitch times of all the consoles I've done, at least the Zehpyr is working, maybe 7 to 15 attempts and occasionally not at all.
  7. Thanks Josh, i appreciate the reply. Actually it was timing file zephyr_150_E_2_L_1.xsvf that I used successfully. Sorry I miss typed and just now corrected that in my last post. Also, thanks for looking at the smc+ info. I didn't know how to interpret the log differences, thought might be a bug or that the smc+ wasn't being applied.
  8. Hello Josh, thanks for all the great work you do supporting this platform. I really enjoy your videos. I recently did a RGH2 on a Zephyr following your online guide. I made a couple observations along the way. First I could not get Xell to load at all using the timing files built into your latest release. I can't say I tried them all but I did try at least most of them. I also was patient, very patient, in my attempts trying each timing file for a few times. So I literally a couple hours trying different ones which I was prepared for given that it was a Zephyr. I am using the latest release V3.0.0d. Then I found a download from another Youtuber with 4 files in it. 2 labeled zephyr_150 and 2 zephyr_300. It was the second file I tried that worked zephyr_150_E_2_L_1.xsvf to boot Xell. My ace v3 clock says 150MHz, not sure what bundled timing file are 150 vs 300. While booting times are sort of inconsistent it does at least boot, sometimes 1st glitch and often 7 to 15 or more attempts. So I don't know what is different about this timing file and the ones included in your J-runner release. One thing I noticed is that my board has a label Rev A on it, and it has populated the big capacitor right beside the top Alt Rst point whereas the picture of your board online does not. Also when I built the nand I did check SMC+, but I don't think I am seeing quicker glitching attempts. The online guide says you can enable it, but the J-runner hint that pops up says for RGH 1.2 and S-RGH. I have selected Falcon as the board type during both image build attempts. In the xebuild log file I see difference in the build when this is enable vs not. Under the Section labelled: Encrypting and finalizing bootloaders binary! With SMC+ enabled; encoding SMC.bin size 0x3000 SMC checksum: df1fff40 unknown SMC found, type: Falcon v3.1(1.06) glitch hack found in SMC binary! Without SMC+ enabled; encoding smc.bin size 0x3000 SMC checksum: 7e5bc217 known clean SMC found, type: Zephyr v2.1(1.13) patching SMC reset limit at offset: 0x12a3 SMC reset limit patched successfully! Many thanks for all the support.
×
×
  • Create New...