volotova-
So, just to clarify:
you made a bin with dd of your /dev/mtdblock/0
AND
you used dd to write the SAME bin (can you confirm that?) to the /dev/mtdblock/0?
Or did you modify the /dev/mtdblock/0 (like change the bootcode, settings, whatever) using a hex editor?
After loading the HW register settings, the next step is to load the bootcode, according to that Chinese bootcode recovery document. So, from that document:
"
- Open the terminal, following the blank keys and then boot, the system shows "s / d / g / c>" representatives to the recovery mode
- Press "s" ready to send HW register setting
- Select transfer -> send the file, specify the appropriate HW register setting file, protocol, please select "Ymodem".á(Not Ymodem-G)
- Transmission is completed if the display "hello world!", On behalf of HW register setting sent successfully.
- Press "d" ready to send updated bootcode
- Select transfer -> send the file, specify the appropriate bootcode image, protocol, please select "Ymodem".áHere's transmission rate than Ethernet download slow (1.4MB 8 minutes)
- The transfer is complete CRC calculation will take some time (Note) After calculated as shown below:
- Press "g" to perform the update bootcode
- See the "Finish" on behalf of updates bootcode completed, you can reboot.
"
So it sounds like you did steps 1-4, now you need to do steps 5-9.
To do that you need a bootcode. ASUS has not released a bootcode update bin for the OPLAY- they simplay have some that shipped with 0000.0202.0017 and some that shipped with 0000.0202.0018.
Since you are out of luck on that front, why don't you try the bootcode 18 bin from patriot? the worst that could happen is you'll still have a non-working unit.
Here's a link to pbo's bootcode 18:
http://www.4shared.com/file/ecr6Diwb...dd_PATRIO.html
Please answer my questions and supply logs if you can,
wigout


Reply With Quote


