Someone updated 14699 on slim, no boot

[Kinsxxxman]

People never listen.
Here's the problem, installed a coolrunner for a friend and everything was fine. His roommate saw the update this morning and installed it.

Xell boots, but no dashboard.
What's the fix? They have their two original NAND dumps and the freeboot it was flashed with using rawflash that I gave them after the install.
Do I tell them to rawflash the stock or the freeboot back to it?

Edit:
I figured I would save some reading and post the resolution up top.

Problem:
Person installed the the metro dash 14699 over a coolrunner running 13604
Xell boots but no dashboard
This was on a 4 gig slim trinity

Resolution:
1. Performed 3 NAND dumps from xell's web interface, and checked them, I used jtag tool's compare feature.

2. Ran the new dump through easyggBuild v0.4 Final, it gave me the new LDV value.
There's several ways to get it but this is how I did it because I needed to build a new nandflash.bin anyways and it only take a few seconds to do.

3. Edited the settings.ini with the new LDV value, and CPU key.

4. Built a new glitch image from the original stock NAND dump that was used to install the RGH.

5. Flashed the new image through xell with rawflash

Ta-da!

Thanks to everyone for their feedback and advice!

 

[x360ccm]

so you didnt block live then

or set the ini right.

liveblock = true
livestrong = false

 

[ocmoho]

Id reflash freeboot.
He went on live with a rgh? Wow... Lol

 

[Kinsxxxman]

Like I said people don't listen , I said no live. I didn't know about a live block!?

 

[krier023]

Your ldv values have probably changed with the update.

 

[x360ccm]

Like I said people don't listen , I said no live. I didn't know about a live block!?

you can block live via the settings.whenever i fit a coolrunner i block live.

just coz people will try it,even tho you tell them not to.

just edit your ini with this if you install it to hdd

[QuickLaunchButtons]
BUT_X = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
Default = Hdd:\Freestyle\default.xex
[Settings]
nxemini = true
pingpatch = true
liveblock = true
livestrong = false

if you install to usb then use this

[QuickLaunchButtons]
BUT_X = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
Default = Usb:\Freestyle\default.xex
[Settings]
nxemini = true
pingpatch = true
liveblock = true
livestrong = false

:biggrin:

 

[TilVl]

Make another dump of the new dash and check the LDV. Match the old freeboot with the new LDV and reflash. If that don't work might have to wait for a new freeboot.

 

[Kinsxxxman]

Make another dump of the new dash and check the LDV. Match the old freeboot with the new LDV and reflash. If that don't work might have to wait for a new freeboot.

Ok. I'll try that Friday have to get their box from them and post the results. I'm sure someone else is going to do this.
Maybe a dumb question, but with xell working is there a way I can have them dump it from there to a usb without have to get their box and hook a NAND-x to it? Kind of like a reverse rawflash?

Edit.. Never mind I posted too early and found that you can download your flash from the embedded web server in xell reloaded.

 

[blastagator]

Should have taken the resistor off so ldv wouldn't change

Then the old glitch image would flash back perfectly

 

[ball00]

It's ok you can make a new glitch image off the new dash. LDV may have changed so you may have to patch that but I glitched a console last night from the new dash with no particular problems.

 

[Kinsxxxman]

It's ok you can make a new glitch image off the new dash. LDV may have changed so you may have to patch that but I glitched a console last night from the new dash with no particular problems.

I used jtag tool to do the initial install, can you give me details on how you made a new glitch image? I guess I have some reading to do on the whole LDV patching, I have not yet needed to do that to any consoles so that is new territory.

 

[gargoyle67]

Should have taken the resistor off so ldv wouldn't change

Then the old glitch image would flash back perfectly

I thought slims didn't have one ?

Edit** Soz I was thinking of efuses

 

[bongtoker]

I used jtag tool to do the initial install, can you give me details on how you made a new glitch image? I guess I have some reading to do on the whole LDV patching, I have not yet needed to do that to any consoles so that is new territory.

IIRC, you can set the LDV manually in ggbuild.

 

[Kinsxxxman]

IIRC, you can set the LDV manually in ggbuild.

Ok, I got 3 NAND dumps off of the non booting dash after the update from xell and compared them, all 3 match.

I ran ggbuild on the 14699 dump and told it to make a 13604 glitch and it did, finished and told me LDV 3

Then I ran it on the 13604 factory dump and it said LDV 2

Now what?

 

[bongtoker]

Make a new freeboot with LDV at 3 and flash to the console

 

[Kinsxxxman]

Make a new freeboot with LDV at 3 and flash to the console

With which one I'm guessing the 13604 with LDV 3 and then wait for an official 14699 freeboot?

Sorry for the newb type questions. I'm and old school hardware guy trying to learn the new stuff, and missed the learning curve somewhere along the way.

 

[bongtoker]

yes

 

[Kinsxxxman]

Ok, so that worked just fine!

 

[TilVl]

No you can install the patched dash as well. Just makeb sure your freeboot image has a matching ldv.

Sent from my SGH-T839 using Tapatalk

 

[bongtoker]

Good to hear. This time don't forget to add

noupdater = true
liveblock = true
livestrong = false

to your launch.ini so it doesn't happen again