Please help. Guide button not function after update to 17489

D

dzungnguyen

Noob Account
Feb 17, 2016
7
0
(Solved) Please help. Guide button not function after update to 17489

Hi everybody.
I have a Trinity RGH. Recently, I dumped the nand and there is a bad block in it. This is the text which is showed in J-runner when I loaded my nand:
• Bad Block ID @ 0x29D [Offset: 0xAC7A00]
• Bad Block ID @ 0x29D Found @ 0x3FF[Offset: 0x107BE00]
When I update to the lastest dashboard (17489), the guide button is useless - not function at all. On any dashboard below 17489, everything works fine.
I've tried both J-runner and xeBuild to build my nand. Both of them show the same error on 17489.
I wonder if anybody had the same problem? How can I fix it?
Thank you very much.
Ps: I've tried to solve problem by the donor nand method. Then I get a clean nand without bad block in it. But when I flashed it to the console, the flashing screen still showing that there is bad block at 0x29D and writing error 0x0...0210 (I don't remember exactly how many "0" in it ;D)
and the guide button still not working. Please help me
 
Last edited:
Titanfreak736

Titanfreak736

BANNED
Oct 19, 2014
194
0
Bad blocks are normal why tf would you use a donor nand flash back the normal rgh image the guide button isn't working because the controller probably if it's not the controller probably a dashlaunch setting
 
Last edited:
D

dzungnguyen

Noob Account
Feb 17, 2016
7
0
I'm pretty sure it has nothing to do with the controller or dashlaunch setting. On every dashboard below 17489, everything works flawlessly. The problem only appear when I'm on 17489 (I'm using the latest dashlaunch version with the same setting on every dashboard and my console has only one controller)
And the way I think is that if something not function as it should does, then it isn't normal at all
 
Last edited:
D

dzungnguyen

Noob Account
Feb 17, 2016
7
0
My first post was disappeared after I changed the title of the thread. So I put it again here just in case if someone don't know what has happened in the beginning.
--------------------------
"Hi everybody.
I have a Trinity RGH. Recently, I dumped the nand and there is a bad block in it. This is the text which is showed in J-runner when I loaded my nand:
• Bad Block ID @ 0x29D [Offset: 0xAC7A00]
• Bad Block ID @ 0x29D Found @ 0x3FF[Offset: 0x107BE00]
When I update to the lastest dashboard (17489), the guide button is useless - not function at all. On any dashboard below 17489, everything works flawlessly.
I've tried both J-runner and xeBuild to build my nand. Both of them show the same error on 17489.
I wonder if anybody had the same problem? How can I fix it?
Thank you very much.
Ps: I've tried to solve problem by the donor nand method. Then I get a clean nand without bad block in it. But when I flashed it to the console, the flashing screen still showing that there is bad block at 0x29D and writing error 0x0...0210 (I don't remember exactly how many "0" in it ;D)
I always use the latest dashlaunch version (3.16) and FSD3 rev 775 with the same setting on every dashboard. So it has nothing to do with the settings or dashlaunch or FSD at all."
-----------------------
I solved the problem by using Flash360 instead of Simple 360 nand flasher to flash the 17489 nand. When using Flash360, there are 2 options to flash the nand:
- RAW FLASH with keeping current kv/config
- RAW FLASH without keeping current kv/config
I chosed the 2nd one. Flash360 started to compare the kv/config of the current nand with the new one and some warning pop up saying that these two are mismatch. But I ignored it and chosed to flash the new one. It worked.
I guess that Simple 360 Nand Flasher always flash the nand with the 1st option and there was some problems with the old kv/config. I still don't understand why there was a different between 2 nand. I builded the new one base on the old one, so I think kv/config should be the same on both nand. If someone know why, please explain.
Thank you.
 
Last edited:
You must log in or register to reply here.