ANSWERED Help with J-Runner

Status
Not open for further replies.
C

criminalce

Junior Member
Feb 5, 2011
16
0
Please verified the code on creation Freeboot.
Yesterday I upgdating 14719 avatar on 14719 freeboot....overwritten with nxe stock!! :mad2:
Freebot bin is not always genuine
 
Last edited:
C

criminalce

Junior Member
Feb 5, 2011
16
0
Re: Bug on creation freeboot jrunner

I specified NOT ALWAYS....but it is so.
Have you ever tried to compare a freeboot created with Xbuild 2.0 and jrunner .....it's NOT same.
Then maybe this does not mean anything but it is so.
the fact remains that still is not anything I did wrong ... is not the my first or second rhg...
 
C

criminalce

Junior Member
Feb 5, 2011
16
0
Re: Bug on creation freeboot jrunner

If the software has a bug in the log does not tell you anything ..... but here
Code: 
===================================================
giovedì 29 marzo 2012 15:51:23



No Updates Found


Checking Files
Finished Checking Files
Error: 000 reading block 0
Error: A32 reading block 1
Error: A32 reading block 2
Error: A32 reading block 3
Jasper 512MB
Jasper 512MB
Can not continue
Error: 000 reading block 3
Jasper 512MB
Error: 000 reading block 2
Error: 000 reading block 3
Jasper 512MB
Error: 000 reading block 1
Error: 000 reading block 2
Error: 000 reading block 3
Jasper 512MB
Reading Nand to I:\Programmi essenziali\J-Runner v01 Beta (256)\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00AA3020
Reading Nand
Error: 000 reading block 1
Error: 000 reading block 2
Error: 000 reading block 3
Error: 000 reading block 4
Error: 000 reading block 6
Error: 000 reading block 7
Error: 000 reading block 8
Error: 000 reading block 9
Error: 000 reading block A
Error: 000 reading block B
Error: 000 reading block C
Error: 000 reading block D
Error: 000 reading block E
Error: 000 reading block F
Error: 000 reading block 10
Error: 000 reading block 11
Error: 000 reading block 12
Error: 000 reading block 13
Error: 000 reading block 14
Error: 000 reading block 15
Error: 000 reading block 16
Error: 000 reading block 17
Error: 000 reading block 19
Error: 000 reading block 1A
Error: 000 reading block 1D
Error: 000 reading block 1E
Error: 000 reading block 1F
Error: 000 reading block 20
Error: 000 reading block 21
Error: 000 reading block 22
Error: 000 reading block 23
Error: 000 reading block 24
Error: 000 reading block 25
Error: 000 reading block 26
Error: 000 reading block ===================================================
giovedì 29 marzo 2012 16:02:08



No Updates Found


Checking Files
Finished Checking Files
Jasper 512MB
Jasper 512MB
Reading Nand to I:\Programmi essenziali\J-Runner v01 Beta (256)\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00AA3020
Reading Nand
Done!

Reading Nand to I:\Programmi essenziali\J-Runner v01 Beta (256)\output\nanddump2.bin
Initializing Nand..
Arm Version: 3
Flash Config: 0x00AA3020
Reading Nand
Done!

Comparing...Takes a while on big nands
Nands are the same
* found flash image, unpacking....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 2.3
CB_A: 6750
CB_B: missing
CD (image): 8453
CD (decrypted): 8453
 * this image will be valid *only* for: jasper (CB_6750)
 * patching SMC...
Patching Jasper version 2.3 SMC at offset 0x12BA
 * zero-pairing...
 * constructing new image...
 * base size: 70000
 * encrypting CB...
7B67DFF4AE33BEEDB39398E8D6CCDE44
 * encrypting CD...
 * No separate recovery Xell available!
 * Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0xFFF (0xE00 bytes) Padding
0x1000..0x3FFF (0x3000 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x11A3F (0x9A40 bytes) CB_A 6750
0x11A40..0x17A3F (0x6000 bytes) CD 8453
0x17A40..0xBFFFF (0xA85C0 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
 * Encoding ECC...

100%
------------- Written into output\image_00000000.ecc
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

Programming Coolrunner
Flashing I:\Programmi essenziali\J-Runner v01 Beta (256)\common\xsvf\jasper.xsvf to CoolRunner
Input Filesize: 593E
Output Filesize: 27F0
Done!


Exited!

Getting info from ip...
Getting info from ip...
Connection TimeOut
Connection TimeOut
Getting info from ip...
Initializing Nand..
CpuKey is Correct
Added Key to Database
Load Files Initiliazation Finished
Started Creation of the xebuild image
KV Info saved to file
Initializing Nand..
CpuKey is Correct
Key already Exists
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building glitch image


****************  WARNING  *************************
  nanddump.bin has NAND memory unit data, make
  sure you back up any important data off the
  internal MU before flashing a new image!
****************************************************

---------------------------------------------------------------
I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB + NAND MU area
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  :
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : 
CF LDV   : 9
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
Device Not Found.
Exited!

Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

===================================================
giovedì 29 marzo 2012 19:14:02



No Updates Found


Checking Files
Finished Checking Files
Programming Coolrunner
Flashing I:\Programmi essenziali\J-Runner v01 Beta (256)\common\xsvf\jasper.xsvf to CoolRunner
Input Filesize: 593E
Output Filesize: 27F0
Done!


Exited!

Initializing Nand..
Jasper 512MB
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

Jasper 512MB
Initializing Nand..
Comparing...Takes a while on big nands
Nands are the same
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

===================================================
giovedì 29 marzo 2012 19:53:37



No Updates Found


Checking Files
Finished Checking Files
Jasper 512MB
Jasper 512MB
Reading Nand to I:\Programmi essenziali\J-Runner v01 Beta (256)\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00AA3020
Reading Nand
===================================================
giovedì 29 marzo 2012 19:58:03



No Updates Found


Checking Files
Finished Checking Files
Initializing Nand..
Initializing Nand..
Initializing Nand..
CpuKey is Correct
Key already Exists
Initializing Nand..
Initializing Nand..
Initializing Nand..
Comparing...Takes a while on big nands
Nands are the same
Jasper 512MB
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

===================================================
giovedì 29 marzo 2012 21:02:53



No Updates Found


Checking Files
Finished Checking Files
Jasper 512MB
Jasper 512MB
Reading Nand to I:\Programmi essenziali\J-Runner v01 Beta (256)\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00AA3020
Reading Nand
Done!

Reading Nand to I:\Programmi essenziali\J-Runner v01 Beta (256)\output\nanddump2.bin
Initializing Nand..
Arm Version: 3
Flash Config: 0x00AA3020
Reading Nand
Done!

Comparing...Takes a while on big nands
Nands are the same
* found flash image, unpacking....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 2.3
CB_A: 6753
CB_B: 6753
CD (image): 6753
CD (decrypted): 8453
Not supported yet
* found flash image, unpacking....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 2.3
CB_A: 6753
CB_B: 6753
CD (image): 6753
CD (decrypted): 8453
Not supported yet
Load Files Initiliazation Finished
Started Creation of the xebuild image
KV Info saved to file
Initializing Nand..
CpuKey is Correct
Key already Exists
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building glitch image


****************  WARNING  *************************
  nanddump.bin has NAND memory unit data, make
  sure you back up any important data off the
  internal MU before flashing a new image!
****************************************************

---------------------------------------------------------------
I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB + NAND MU area
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  :
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : 
CF LDV   : 10
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
Initializing Nand..
CpuKey is Correct
Key already Exists
Load Files Initiliazation Finished
Started Creation of the xebuild image
KV Info saved to file
Initializing Nand..
CpuKey is Correct
Key already Exists
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB (system only)
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  :
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : 
CF LDV   : 10
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

===================================================
giovedì 29 marzo 2012 21:49:06



No Updates Found


Checking Files
Finished Checking Files
Initializing Nand..
Jasper 512MB
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

Load Files Initiliazation Finished
Started Creation of the xebuild image
KV Info saved to file
Initializing Nand..
CpuKey is Correct
Key already Exists
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building glitch image


****************  WARNING  *************************
  nanddump.bin has NAND memory unit data, make
  sure you back up any important data off the
  internal MU before flashing a new image!
****************************************************

---------------------------------------------------------------
I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB + NAND MU area
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  :
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : 
CF LDV   : 9
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

===================================================
giovedì 29 marzo 2012 22:15:27



No Updates Found


Checking Files
Finished Checking Files
Initializing Nand..
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

Initializing Nand..
Comparing...Takes a while on big nands
Nands are the same
Load Files Initiliazation Finished
Initializing Nand..
CpuKey is Correct
Key already Exists
Started Creation of the xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building retail image


****************  WARNING  *************************
  nanddump.bin has NAND memory unit data, make
  sure you back up any important data off the
  internal MU before flashing a new image!
****************************************************

---------------------------------------------------------------
I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB + NAND MU area
Build    : Retail
CPU Key  : 
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : 
CF LDV   : 10
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

===================================================
giovedì 29 marzo 2012 22:42:33



No Updates Found


Checking Files
Finished Checking Files
Initializing Nand..
Comparing...Takes a while on big nands
Nands are the same
Load Files Initiliazation Finished
Initializing Nand..
CpuKey is Correct
Key already Exists
Started Creation of the xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building glitch image


****************  WARNING  *************************
  nanddump.bin has NAND memory unit data, make
  sure you back up any important data off the
  internal MU before flashing a new image!
****************************************************

---------------------------------------------------------------
I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Jasper (big block)
NAND size: 64MiB + NAND MU area
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  : 
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : 
CF LDV   : 10
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to I:\Programmi essenziali\J-Runner v01 Beta (256)\219156494005
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
Initializing Nand..
CpuKey is Correct
Key already Exists
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!

Programming Coolrunner
Flashing I:\Programmi essenziali\J-Runner v01 Beta (256)\common\xsvf\jasper.xsvf to CoolRunner
Input Filesize: 593E
Output Filesize: 27F0
Done!


Exited!

Initializing Nand..
Comparing...Takes a while on big nands
Initializing Nand..
Nands are the same
Comparing...Takes a while on big nands
Nands are the same
Jasper 512MB
Arm Version: 3
Flash Config: 0x00AA3020
Writing Nand
Done!

Exited!
 
Oggy

Oggy

Staff member
Troll Eating Dogs
Mar 1, 2010
3,346
128
Re: Bug on creation freeboot jrunner

Not even sure why you were building retail images in the first place ?
 
C

criminalce

Junior Member
Feb 5, 2011
16
0
Re: Bug on creation freeboot jrunner

I'm sure.... I writing freeboot with jrunner.
Is not reporting in the log?
But is normal the freeboots create with jrunner and Xbuild 2.0 aren't same??
 
Last edited:
S

superspeed

VIP Member
Feb 2, 2012
825
0
TX, USA
Re: Bug on creation freeboot jrunner

criminalce said:
I'm sure.... I writing freeboot with jrunner.
Is not reporting in the log?
But it's normal the freeboots create with jrunner and Xbuild 2.0 aren't same??
Click to expand...
The avatar update does not override the freeboot image others would have been flooding the thread with complaints if it did. The is what we call user error. Sorry for the inconvenience but unless it's a slim you're gonns need to wait for RGH 2.0
 
C

criminalce

Junior Member
Feb 5, 2011
16
0
Re: Bug on creation freeboot jrunner

superspeed said:
The avatar update does not override the freeboot image others would have been flooding the thread with complaints if it did. The is what we call user error. Sorry for the inconvenience but unless it's a slim you're gonns need to wait for RGH 2.0
Click to expand...
nice answer .....very diplomatic and comprehensive.
But is normal the freeboots created with jrunner and Xbuild 2.0 aren't same??Have you response for this question?
 
S

superspeed

VIP Member
Feb 2, 2012
825
0
TX, USA
Re: Bug on creation freeboot jrunner

criminalce said:
nice answer .....very diplomatic and comprehensive.
But is normal the freeboots created with jrunner and Xbuild 2.0 aren't same??Have you response for this question?
Click to expand...
No they will be different because different methods of programming and J-Runner also embeds dashlaunch.
 
Last edited:
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Re: Bug on creation freeboot jrunner

They are different because Big Block NANDs have random padding in them. That's why.

Kindly refrain from accusing a reliable app of being wrong when you haven't got a clue what you're doing.
 
  • Like
Reactions: superspeed
C

criminalce

Junior Member
Feb 5, 2011
16
0
I really do not have offended anyone on the contrary have been offended. But you know you're famous on the web for your pride ... goodbye genes.
I forgot ... I came here with a problem ... and immediately I was told in advance that I was wrong about me without giving me an explanation .... jrunner ... trouble and perfect stop to question it.
thanks for the help :facepalm:
 
Last edited:
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Re: Bug on creation freeboot jrunner

criminalce said:
compliments
What's wrong reading log in the first page Sir Admin?
say that I do not know what I do know tell me why...?
Click to expand...
Because according to you, there's a bug in J-Runner.

I've looked through the log and can't see anything out of place, apart from the obvious point of you not having your NAND-x connected properly.

You were also bitching about the files being different. As I explained, there's random padding on Big Block NANDs. Common sense would tell you this since 16MB NANDs have exactly the same data on them as the first 64MB of a big block NAND, so there's 48MB of surplus space.

So yes, you don't know what you're doing.
 
S

superspeed

VIP Member
Feb 2, 2012
825
0
TX, USA
criminalce said:
I really do not have offended anyone on the contrary have been offended. But you know you're famous on the web for your pride ... goodbye genes.
I forgot ... I came here with a problem ... and immediately I was told in advance that I was wrong about me without giving me an explanation .... jrunner ... trouble and perfect stop to question it.
thanks for the help :facepalm:
Click to expand...
I've never acclaimed myself to be a "genius" but like Martin said you don't have your nand-x wired wrong. There's no way to get that many bad blocks if everything is soldered properly.
 
C

criminalce

Junior Member
Feb 5, 2011
16
0
superspeed said:
Try not being a complete arse to people and you would've probably gotten better help. K thanks bye.
Click to expand...


maybe if you were telling me that the freeboot you write to us, corrupt could be .... but you have done nothing but give me incompetent ...this is respect?
And my question was to take away all doubt ... what do I know if freeboot must all be equal? offense and ask?

---------- Post added at 07:14 ---------- Previous post was at 07:10 ----------
superspeed said:
I've never acclaimed myself to be a "genius" but like Martin said you don't have your nand-x wired wrong. There's no way to get that many bad blocks if everything is soldered properly.
Click to expand...
Sorry, but you're saying? the first reading does not need to consider maybe ..... look at those later


small clarification.
creates two freeboot from 16mb:
first with xbuild 2.0
second with jrunner
show the difference
So yes, you don't know what you're doing.
 
Last edited:
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I'm looking through the log and I can't work out why you're creating another ECC for your NAND when you have the CPU key. I also can't see what the problem is, if there's one at all

Maybe just paste the error and then we can take a look?
 
C

criminalce

Junior Member
Feb 5, 2011
16
0
Martin C said:
Maybe just paste the error and then we can take a look?
Click to expand...
I'm also a fake?:facepalm:
sorry but the log is complete(excluding serial).
I have tested recreate ecc only after update 14719 stock for the confirmation overwritten completaly (look cb a/b)
 
Status
Not open for further replies.