|
wang
|
 |
« Reply #200 on: November 16, 2010, 02:15:27 AM » |
|
had some trouble with bestpig's freeboot toolbox and my previous 9199 image. i flashed it, and got nothing but a black screen. resoldered my lpt wires, flashed back xellous, and then compiled an image with fbBuild and flashed that, and boom! no problems. all is good. i have a jasper 16mb with no bad blocks
|
|
|
|
|
Logged
|
|
|
|
|
fryc88
|
 |
« Reply #201 on: November 16, 2010, 02:19:46 AM » |
|
So can i or can't i use Jaspafix on my Falcon V3 with same bad block issue like in jaspers?
|
|
|
|
|
Logged
|
|
|
|
|
andrez
|
 |
« Reply #202 on: November 16, 2010, 03:56:13 AM » |
|
So can i or can't i use Jaspafix on my Falcon V3 with same bad block issue like in jaspers?
Wait for cory reply but I think you can't beacuse this is a fix for a problem related to the jasper_a nand controller. Falcon has a different one which by the way should be compatible with fbbuilded images.
|
|
|
|
« Last Edit: November 16, 2010, 04:00:38 AM by andrez »
|
Logged
|
|
|
|
|
keropi
|
 |
« Reply #203 on: November 16, 2010, 04:28:04 AM » |
|
So can i or can't i use Jaspafix on my Falcon V3 with same bad block issue like in jaspers?
I doubt it will do you any good, the problem only was with jasper16a machines, all others should be just fine 
|
|
|
|
|
Logged
|
2x Jasper16a XBR 
|
|
|
|
fryc88
|
 |
« Reply #204 on: November 16, 2010, 04:37:48 AM » |
|
So can i or can't i use Jaspafix on my Falcon V3 with same bad block issue like in jaspers?
I doubt it will do you any good, the problem only was with jasper16a machines, all others should be just fine  If it would be 'only' jasper, i wouldn't ask. As i said, i got Falc with 1 in 0148 bad sector, after flashing xellous it's not remapping it auto, and i got e71 at first/second launch, then only reflash helps. I did try also to remap it manually to 3ff and other reserved sectors, but no success. I'm using SMC_config and KV from my ORIGINAL nand dump, and smc from xbr/freeboot dumped from my console...Maybe im doing wrong something out here?
|
|
|
|
|
Logged
|
|
|
|
|
andrez
|
 |
« Reply #205 on: November 16, 2010, 05:16:56 AM » |
|
Try manually remapping 148 to 3FF and also flashing a zero sector on 148.
|
|
|
|
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #206 on: November 16, 2010, 05:54:01 AM » |
|
Keropi: good to hear  So can i or can't i use Jaspafix on my Falcon V3 with same bad block issue like in jaspers?
It's right in the name... fixjaspa.exe = (abbreviated to dos file name length)fix jasper_a.exe So no, it does not apply to falcon (falcon always has the 'small block' flash controller and is not capable of using 256M and 512M NAND.) My own falcon has a bad block on the cygnos NAND and I can confirm remapping is no problem for falcon. See some of my earlier suggestions in this thread, they are the first things to try when 'normal' remapping methods don't work, and in your case I think the suggestion to use linux to flash would work as well.
|
|
|
|
|
Logged
|
|
|
|
|
nokaktsawa
|
 |
« Reply #207 on: November 16, 2010, 06:05:40 AM » |
|
Cory1492, I used your fixjaspa app to fix my jasper 16a, and it really worked like a charm!!! Thank you very much, Cory, for your precious efforts to the scene 
|
|
|
|
|
Logged
|
|
|
|
|
Eiji
|
 |
« Reply #208 on: November 16, 2010, 06:56:01 AM » |
|
after talking with cory1942 I am gonna fixjaspa my other working 360 too... since his way is the correct working one, it should be applied to others as well because in the case of a new bad block developing all the working 16a's might suddenly E71 if dash.xex is affected (or other vital parts...)
So even without bad blocks we should use fixJaspa on Jasper "a" NAND images?
|
|
|
|
|
Logged
|
|
|
|
|
keropi
|
 |
« Reply #209 on: November 16, 2010, 06:59:57 AM » |
|
after talking with cory1942 I am gonna fixjaspa my other working 360 too... since his way is the correct working one, it should be applied to others as well because in the case of a new bad block developing all the working 16a's might suddenly E71 if dash.xex is affected (or other vital parts...)
So even without bad blocks we should use fixJaspa on Jasper "a" NAND images? yes if you think of it is logical to apply fixjaspa on ALL jasper16a machines. The current fbbuild builds wrong images, the fact that they happen to run OK on machines with no bad blocks is just luck. Like cory1942 said, if your OK 16a suddenly develops a bad block then you will get errors with fbbuild's image... so why not be on the safe side and have a correct image from the start? 
|
|
|
|
|
Logged
|
2x Jasper16a XBR 
|
|
|
|
Eiji
|
 |
« Reply #210 on: November 16, 2010, 07:02:27 AM » |
|
yes if you think of it is logical to apply fixjaspa on ALL jasper16a machines. The current fbbuild builds wrong images, the fact that they happen to run OK on machines with no bad blocks is just luck. Like cory1942 said, if your OK 16a suddenly develops a bad block then you will get errors with fbbuild's image... so why not be on the safe side and have a correct image from the start?  And should I flash a patched image with bad blocks (or not) with Xellous or is Flash360 also ok?
|
|
|
|
|
Logged
|
|
|
|
|
keropi
|
 |
« Reply #211 on: November 16, 2010, 07:03:22 AM » |
|
xellous/flash360 is OK , just flash your image 
|
|
|
|
|
Logged
|
2x Jasper16a XBR 
|
|
|
|
doveman
|
 |
« Reply #212 on: November 16, 2010, 08:13:38 AM » |
|
Can anyone just reassure me that dash 12611 built with fbBuild 0.1 is working fine on Jasper512 (SMC 2.3, CB6723)?
I just don't want to be jumping in blind!
|
|
|
|
|
Logged
|
|
|
|
|
ZerOneX
|
 |
« Reply #213 on: November 16, 2010, 08:17:35 AM » |
|
ZerOneX, any of your jaspers with bad blocks?
Yes, one bad block on the 2nd!!!! But I did not remapped it! I just flashed as it is.
|
|
|
|
|
Logged
|
Just a noob in search of knowledge!
|
|
|
|
ZerOneX
|
 |
« Reply #214 on: November 16, 2010, 08:48:45 AM » |
|
after talking with cory1942 I am gonna fixjaspa my other working 360 too... since his way is the correct working one, it should be applied to others as well because in the case of a new bad block developing all the working 16a's might suddenly E71 if dash.xex is affected (or other vital parts...)
this sounds interesting, I´m going to try this right now.
|
|
|
|
|
Logged
|
Just a noob in search of knowledge!
|
|
|
|
cory1492
|
 |
« Reply #215 on: November 16, 2010, 12:06:50 PM » |
|
Can anyone just reassure me that dash 12611 built with fbBuild 0.1 is working fine on Jasper512 (SMC 2.3, CB6723)?
I just don't want to be jumping in blind!
There is no problem with big block machines, just machines with a big block controller and 16M NAND. That said, this fix doesn't need to be applied to machines that in nandpro (not on the dump, on the machine itself) detect as config 1198010, just the ones that detect as config 23010 - chances are it will work anyway on 1198010 jasper small block though.
|
|
|
|
|
Logged
|
|
|
|
|
doveman
|
 |
« Reply #216 on: November 16, 2010, 12:49:54 PM » |
|
There is no problem with big block machines, just machines with a big block controller and 16M NAND. That said, this fix doesn't need to be applied to machines that in nandpro (not on the dump, on the machine itself) detect as config 1198010, just the ones that detect as config 23010 - chances are it will work anyway on 1198010 jasper small block though.
Cheers for the confirmation cory. I'm always a bit nervous updating because of the bad blocks I've got that Xellous can't cope with, but Flash360 always seems to do the job so fingers crossed it will work first time.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
keropi
|
 |
« Reply #218 on: November 16, 2010, 05:35:47 PM » |
|
@artik: I just tested , all is working fine !!! 
|
|
|
|
|
Logged
|
2x Jasper16a XBR 
|
|
|
|
CAPS369
|
 |
« Reply #219 on: November 16, 2010, 05:53:16 PM » |
|
FbBuild V0.11: Update to a builder of new freeBOOT is out
|
|
|
|
|
Logged
|
CAPS cause women like things nice and big...
|
|
|
|