CORONA Corona V3 CR4 XL issue
- Thread starter tr4ckerz
- Start date
Is there any other app but J-Runner able to build CR4 freeboot image? As far as I am aware not but just to be sure ...
In case of writting freeboot image back to NAND, I already tried J-Runner using NAND-X, tried writting from Xell using USB stick and tried SW X360 NAND Flasher. No difference.
No, not yet. I guess it's kinda tricky to desolder the anchors.
I use XE-build sometimes as far as I know it will just use the CR-4 current SMC on the upflash bin you provide to the the app
It is pretty strait forward.
It is pretty strait forward.
he still used only the blue wire with same results, just didnt take blue out when trying yellow because blue had hot glue on it.
Right but in the pic it clearly shows a wire still solder to FT3T10 right along side of the blue normal CPU_RST which can act like an antenna.
pretty sure he said the yellow wire is just temporary
I never had any luck with that point FT3T10
Hopefully he removed it for testing one at a time both ends
I never had any luck with that point FT3T10
Hopefully he removed it for testing one at a time both ends
Desoldered from just the CR4 end (kept soldered to C5R11 while testing temporary FT3T10).
Your guessing is probably correct, having it soldered even at the one end while testing alternative point may cause issues especially on something as sensitive as CPURST is, however I think this is not the issue in my case because the behavior of the console simply has not changed. In both cases - single CPURST wire to C5R11 or CPURST to FT3T10 while having one end of wire to C5R11 still soldered gave me same results as desribed in the OP.
Well, still no luck damn.
I treid to use Slim Proto V2, redid the installation accordingly (bridged R2C6 and R2C7) using Slim Proto wiring diagram, rebuilt and wrote a new freeboot image, console still behaves the same.
I tried POST_OUT 50/70/90 cm on POSTFIX Adapter and I also tried to swap the POSTFIX adapter for another one. Nothing helped.
As a last chance I'm still thinking to pull CR3 Lite from my own console and give it a try, but I don't believe much that would help.
It really drives me crazy as I have no idea what's going on and support here from devs/staff isn't coming, not even on IRC
I treid to use Slim Proto V2, redid the installation accordingly (bridged R2C6 and R2C7) using Slim Proto wiring diagram, rebuilt and wrote a new freeboot image, console still behaves the same.
I tried POST_OUT 50/70/90 cm on POSTFIX Adapter and I also tried to swap the POSTFIX adapter for another one. Nothing helped.
As a last chance I'm still thinking to pull CR3 Lite from my own console and give it a try, but I don't believe much that would help.
It really drives me crazy as I have no idea what's going on and support here from devs/staff isn't coming, not even on IRC
john mathews
VIP Member
That pretty much rules out any glitch chip hardware failure. I would be looking In to the consoles hardware or software as the problem. I don't see how 15432 could really help because I doubt it could be anything to do with the spedup-SMC that the cr4 uses causing this problem otherwise the proto would have solved the issue. . If I am totally off base saying that the cr4xl uses a sped-up smc, then at least it will draw some attention to the issue with the mods.
Update:
So I pulled out CR3 Lite from my personal console. Having everything wired from my previous setup with Slim Proto V2, I only changed 5V for 3V3. Everything else remained untouched.
Console seems working. It takes forever to boot, but at least it boots. Debug LED on CR3 Lite keeps blinking until boot sequence starts. It does not get stuck like with CR4 XL or Slim Proto V2. I tried tens of starts and each was sooner or later successful.
Now if anyone can advise what is going on here, why console behaves with CR4 and Proto V2 as described in the OP I would really appreciate it. I used all my knowledge, spent dozens of hours with it and now I'm without any more ideas. I RGH'd many consoles but never encountered similar issue.
I don't think I would be satisfied with this result, keeping CR3 Lite inside is a step back. Also the console owner is getting angry because I have this at home several days and he starts thinking that I'm total noob
So I pulled out CR3 Lite from my personal console. Having everything wired from my previous setup with Slim Proto V2, I only changed 5V for 3V3. Everything else remained untouched.
Console seems working. It takes forever to boot, but at least it boots. Debug LED on CR3 Lite keeps blinking until boot sequence starts. It does not get stuck like with CR4 XL or Slim Proto V2. I tried tens of starts and each was sooner or later successful.
Now if anyone can advise what is going on here, why console behaves with CR4 and Proto V2 as described in the OP I would really appreciate it. I used all my knowledge, spent dozens of hours with it and now I'm without any more ideas. I RGH'd many consoles but never encountered similar issue.
I don't think I would be satisfied with this result, keeping CR3 Lite inside is a step back. Also the console owner is getting angry because I have this at home several days and he starts thinking that I'm total noob