ANSWERED Jasper 512MB E71 after update to 14699 dash

M

MadCabbit

Full Member
Jan 18, 2012
32
0
I have a Jasper 512MB box that I had mailed to someone else to do the RGH mod prior to the new update. Everything was working fine when I got the box. I used NAND Flasher 360 to get a copy of my nand, then I used 360 Multi Builder 0.7 to build an updated nandflash.bin. I had previously tried xebuild directly and kept getting E71s when booting, leading me to have to flash back to my previous nand, but after flashing this new file from 360 Multi builder (using rawflash from xell), it booted properly and I got freestyle dash with greyed avatars.

I copied the system update for 14699 to a USB stick and it ran on boot, it started the initial install process, then rebooted, but booted into an E71 (I don't think it finished the dash install). I had the HD removed at the time, and so I put it back on. Freestyle dash still boots, but every time I try to go into the regular dash, I get an E71. I tried reflashing, but it didn't help.

Where do I go from here? If the system update didn't finish completely, how do I get it ro restart? It ignores the update files now, and holding sync while booting to clear failed updates isn't helping.

Any advice would be appreciated. Thanks.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
Do you have any bad blocks? If so, does Multi_builder's log report on them?
Click to expand...
Yes, three. I only recall two shown in the initial dump, then three when I tried writing. Here's the part from Mutli_builder's log:

------ 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...
block 0x16a was remapped to block 0x16b, entering remap instance 1
block 0x16b was remapped to block 0x1fe, entering remap instance 2
block 0x150 was remapped to block 0x1ff, entering remap instance 3
done!
cleaning up stray remaps
done!
--remap summary--
0: source: 0x016a dest: 0x016b
1: source: 0x016b dest: 0x01fe
2: source: 0x0150 dest: 0x01ff

---------- Post added at 05:57 ---------- Previous post was at 05:55 ----------

And the second part I missed in the log:


------ finalizing image ------
Fixing up empty FS block entries...done!
Writing FS table to image...done!
fixing up big block LBA numbers in spare...done!
calculating ECD bytes and assembling raw image...done!
remapping 3 blocks
copying 0x21000 bytes of LBA 0x16a to block 0x16b...zero fill origin...done!
copying 0x21000 bytes of LBA 0x16b to block 0x1fe...zero fill origin...done!
copying 0x21000 bytes of LBA 0x150 to block 0x1ff...zero fill origin...
dest block is empty, fixing up LBA and EDC...done!
done!
writing file 'nandflash.bin' to disk...done!
nandflash.bin written OK
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
Open the original NAND dump in 360 Flash Dump Tool and make sure the remaps found by Multi_builder match.
Click to expand...

Here's what 360 Flash Dump Tool shows for bad blocks:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x015A [Offset: 0x02EAA000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016A found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]

=== Analyzed successfully ================

Is it missing one, since the second part is only finding 2?
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Well there's your problem.

Whoever did it for you shouldn't be touching consoles. Period.

Cardinal rule is "If it's not remapped, it's a badly read block and therefore needs to be redumped".

This hasn't happened and has thrown multi_builder a curveball as 0x016B may not even need to be there.

We can sort this though, but need to find out first whether these are genuine bad blocks.

Go into options.ini in multi_builder and change noremap to 'true'. Build your image and write it to your NAND. Let me know what errors you get. Don't do any more than that for now.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Actually, I misread what you said and got that report on the new flash I did. When I open the original flash, its not showing a tab for bad blocks at all.

I looked on the disk I got with my info that I got back when I had the RGH done, and it is showing two bad blocks on the nands he gave me. Should I try building with one of these, or will it be a problem if I'm still missing the third?

---------- Post added at 06:32 ---------- Previous post was at 06:28 ----------

I should note I tried reading the nand directly using NAND Flasher 360. It saw at least two of the bad blocks, and that was the flash I was trying to use that for some reason, isn't showing bad blocks. The third showed up on one of my writes, I think. I can use the originals I was sent, but once again, how to proceed with the missing bad block?

---------- Post added at 06:34 ---------- Previous post was at 06:32 ----------

I thought 0x0150 was the new one, but the bad blocks on the original are 0x0150 and 0x016B according to 360 NAND Flash Dump Tool. 0x016A is the new one from the looks of it.
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Ok, so talk me through this.

You have an original NAND dump with no bad blocks.

You used NAND Flasher 360 to get a copy of the NAND. Does this show bad blocks?

If so, something went wrong with the NAND dump as there shouldn't be any.

Use your original NAND as the source and you should be ok.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
Ok, so talk me through this.

You have an original NAND dump with no bad blocks.

You used NAND Flasher 360 to get a copy of the NAND. Does this show bad blocks?

If so, something went wrong with the NAND dump as there shouldn't be any.

Use your original NAND as the source and you should be ok.
Click to expand...
I have an original NAND Dump showing 2 bad blocks.
When I check the one I dumped in NAND Flasher 360, it shows none, yet when I check the new flash after running it through Mullti_Builder, I get the bad block report I pasted earlier.

Every time NAND flasher 360 runs now, it says there are 3 bad blocks.
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
So run your original NAND through 360 Flash Dump Tool and keep the output handy.

use this original NAND with multi_builder for your new image and open the log file. Keep noremap = false for now.

paste the output from both the remap in multi_builder and 360 Flash Dump Tool if they are different. If not, flash to the console.
 
  • Like
Reactions: MadCabbit
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Multi_Builder:
bad block at 0x150 (raw offset 0x2b50000), block ignored
bad block at 0x16b (raw offset 0x2ecb000), block ignored
block 0x16b was remapped to block 0x1fe at remap instance 1
block 0x150 was remapped to block 0x1ff at remap instance 0
done!
cleaning up stray remaps
done!
--remap summary--
0: source: 0x0150 dest: 0x01ff
1: source: 0x016b dest: 0x01fe
-----------------

------ finalizing image ------
Fixing up empty FS block entries...done!
Writing FS table to image...done!
fixing up big block LBA numbers in spare...done!
calculating ECD bytes and assembling raw image...done!
remapping 2 blocks
copying 0x21000 bytes of LBA 0x150 to block 0x1ff...zero fill origin...
dest block is empty, fixing up LBA and EDC...done!
copying 0x21000 bytes of LBA 0x16b to block 0x1fe...zero fill origin...done!
done!
writing file 'nandflash.bin' to disk...done!
nandflash.bin written OK

---------- Post added at 07:00 ---------- Previous post was at 06:59 ----------

360 Flash Dump Tool:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016A found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]

=== Analyzed successfully ================

However, when I flash this, I still get E71
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Output from multi_builder?

EDIT:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016A found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]

Did you copy this directly or type it out?
 
Last edited:
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
Output from multi_builder?

EDIT:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016A found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]

Did you copy this directly or type it out?
Click to expand...
That was from 360 Flash Dump Tool. I couldn't find a way to copy and paste it, so I typed it out carefully.

The Multi Builder output, I copied and pasted.
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
try this:

nandpro nandflash.bin: -r64 150.bin 150 1
nandpro nandflash.bin: -r64 16A.bin 16A 1
nandpro nandflash.bin: -r64 16B.bin 16A 1

nandpro usb: -w64 150.bin 150
nandpro usb: -w64 16A.bin 16A
nandpro usb: -w64 16B.bin 16B


Let me know if you get an error during the writing to USB.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
try this:

nandpro nandflash.bin: -r64 150.bin 150 1
nandpro nandflash.bin: -r64 16A.bin 16A 1
nandpro nandflash.bin: -r64 16B.bin 16A 1

nandpro usb: -w64 150.bin 150
nandpro usb: -w64 16A.bin 16A
nandpro usb: -w64 16B.bin 16B


Let me know if you get an error during the writing to USB.
Click to expand...
That would involve connecting a nand-x or similar between my PC and my 360, right? I had someone else do the hack, so I don't have a nand-x.
 
You must log in or register to reply here.