Xebuild Error

[Diddlesom]

Hi,

I keep running into this error in xebuild:

-----------------------------------------------------------
xeBuild v1.00.356
---------------------------------------------------------------
building glitch image


An unhandled exception 0xC0000005 has occured, exiting...

ERROR: No Output file from xeBuild present!
Cleaning data and temporary directories...Done!


****** The app has now finished! ******


I have tried to build the image with Bestpig and multibuilder but it fails with these also

CPUkey is correct

Any ideas on this error guys ?

 

[manwithoutname]

How did you verify the CPU key?

 

[Diddlesom]

How did you verify the CPU key?

I took a photograph of it from Xell screen and checked it over

 

[manwithoutname]

Load up 360 dump tool and add the CPU key to it's database, then see if it will decrypt your nand dump and show all the KV values include the the CPU key it self.

 

[JayDee]

If you can hook the 360 on to your network and enter the ip you see on your tv, into your browser, and download the fuses (cpukey)

Then nothing can be lost in "translation"

 

[Diddlesom]

If you can hook the 360 on to your network and enter the ip you see on your tv, into your browser, and download the fuses (cpukey)

Then nothing can be lost in "translation"

Done and the cpu key was correct,will try the other idea

 

[manwithoutname]

Are you using the latest version of Multi Builder?

 

[Diddlesom]

Are you using the latest version of Multi Builder?

V0.7

---------- Post added at 23:21 ---------- Previous post was at 23:18 ----------

output name overridden to: nandflash.bin


------ Checking .\my360\nanddump.bin ------
Loading NAND dump (0x28ee70 bytes)...done!
NAND dump is from a big block machine
NAND dump uses big block controller
parsing dump into user and spare...
done!
decrypting KeyVault at address 0x4000 of size 0x4000
keyvault decrypted OK, will use if no kv.bin is provided
decrypting SMC at address 0x1000 of size 0x3000
SMC decrypted OK, will use if no external smc.bin is provided
seeking smc config in dump...

An unhandled exception 0xC0000005 has occured, exiting...

---------- Post added at 23:24 ---------- Previous post was at 23:21 ----------

In Jtag tool i get: Error checking key

 

[manwithoutname]

You want me to try and make an image for you or focus on finding why it's not working?

 

[Diddlesom]

sure i will send you the nand.bin

Where do you want it sent ?

 

[Martin C]

open the NAND in 360 Flash Dump Tool. Any bad blocks?

 

[Diddlesom]

open the NAND in 360 Flash Dump Tool. Any bad blocks?

KV Decrypting Error The CPU Key is all Zero or not entered!

I guess this is bad ?

 

[manwithoutname]

Bad nand image. Check your PM . . .

 

[Diddlesom]

Bad nand image. Check your PM . . .

Thanks for your time on this,i read the nand with jtag tool and had 2 matching dumps right away with no bad blocks.

It will have to wait until tomorow evening now as its a bit late for me now.

Load the first 50 blocks you say,im not quite sure how to do this so will have to look that up

Thanks again and will let you know how it goes tomorow

 

[Diddlesom]

So just to recap I type:
nandpro usb: -w32 nanddump.bin 0 50

Into a command prompt to write back the first 50 blocks?

Anything else I need to do before/after,I do not want to make anything worse

Sent from my HTC Desire HD A9191 using Tapatalk

 

[Martin C]

Can you upload one of your dumps?

 

[Diddlesom]

Sure,I have one on fileserve I will see if I can get the link on my phone and PM it to you
Thanks

Sent from my HTC Desire HD A9191 using Tapatalk

 

[manwithoutname]

you mean nandpro usb: -w16 nanddump.bin 0 50

 

[Martin C]

Doesn't actually matter what you use:

-w2
-w16
-w32
-w64
etc

They will all flash back the first 50 blocks.

OP - the issue is you have a BB Jasper, so the dump is incomplete.

Flash back the first 50 blocks (nandpro usb: -w2 nand1.bin 0 50).

Then re-dump: nandpro usb: -r64 nand.bin

Read my roadmap for noobies as it stops this mistake from happening.

 

[Diddlesom]

Doesn't actually matter what you use:

-w2
-w16
-w32
-w64
etc

They will all flash back the first 50 blocks.

OP - the issue is you have a BB Jasper, so the dump is incomplete.

Flash back the first 50 blocks (nandpro usb: -w2 nand1.bin 0 50).

Then re-dump: nandpro usb: -r64 nand.bin

Read my roadmap for noobies as it stops this mistake from happening.

I get error: Incompatible ARM hardware for this version of nandpro!

My nandx is v3 as i bought a upgrade cable and did it only a couple weeks ago