corona stock image wont boot after update. demon rgh boots

[Zebesk]

So I have an odd issue. I have a 16mb Corona with a demon and cr3 installed and everything worked as it should until the stock dash was updated to 16202.
The Xbox was originally 13599 and the rgh image mage was 16202.
The stock NAND was updated via USB drive.
All the wires have been checked via multimeter.
The cr3 is flashed with corona timing files and the demon option was selected.
I can get a rgh image to boot on both bands fine.
I have tried flashing my stock NAND before the update, I've tried making a 16202 stock NAND, I've tried flashing a lower dash version rgh image and then updating with USB. All have not worked and the last thing I mention I tried, the update fails with an error.

Any advice, thanks

Edit:
Also have tried making a fresh NAND from a donor NAND and the extracted USMC.
Sorry, I only have a pic of the top of the mobo.
Also, I have done tons of searching with no luck. I found similar things, but nothing exact and no solutions were given.
I know this is my first post on here, but that is only because I know how to read before bugging people.
Thanks

 

[Krafter]

What do you mean by wont boot? Do you get a red dot, black screen, etc..


Sent from my iPhone using Tapatalk

 

[Zebesk]

Some builds end up as a red error light. Some just show power led solid without error forever. Never any rol activity or error lights and blank screen every time.

 

[big_ted]

To flash your old image you'll need to up the ldv count by one. if only one update has been carried out.

Ted

 

[Zebesk]

Thanks, I will try this and report back!

 

[Zebesk]

So after doing quite a bit of searching and testing a few different things, I need some direction with changing the LDV.
I tried Multi Builder (and also read the post by Martin C) and it doesn't seem to support Corona motherboards. The options file show corona as a motherboard type and some of the other files list corona, but the command interface doesn't show corona as an option and even setting type=corona in the options and not selecting the motherboard type in the command interface (pushing enter when prompted for a number) the output is a trinity file. I checked the file in the JRunner program and under KV info it shows the motherboard type as trinity as well.
I tried flashing anyways with no luck and I also tried changing the NAND type to corona in the JRunner program by selecting the dashboard version and retail nand option then selecting create image and choosing corona. Still nothing.
I am pretty sure that the LDV should be 2 now as it was 1 according to the stock nand I have and Xell not showing video on coronas makes it dificult to see for sure that it should be 2. Should I ignore that Multi Builder and JRunner are telling me that it is a Trinity nand and keep trying different LDV values, or is the issue with Multi Builder setting the motherboard type to trinity?

Thanks

 

[Zebesk]

Bump!
So far no luck.
Got the eFuse info from Xell over the network and can confirm that the LDV is 1.
Since this is the same as the stock image I would think that the stock image should beet then :/

 

[Zebesk]

Solved!

The issue ended up being the CoolRunner timing files.
The files that came with the Jrunner app didn't work and I had to grab the unreleased and write them using the advanced custom CR functions in the app.

Odd that the stock image booted up until the update failed...

Hope this helps other people that may run into the same issue!