Author Topic: [S7300][Custom Firmware] NCCE 1.1 [New]2.0 Soon  (Read 701303 times)

Vektor

  • **
  • Posts: 605
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #30 on: January 28, 2013, 10:02:04 am »
It's possible that he didn't turn debug mode on in the tablet before bricking it.... that would render adb totally usesless unfortunatly i think.

Unfortunately debugging was off, but I've found some interesting things about this bug. The Device is detected as M3-chip or M6-chip and then as usb mass storage. This is right. What's wrong is that the storage partition should contain some files coming from uImage_usb_burn to go on, but it's empty.

It's the same chip of amlogic/onda and many others devices, but those ones have more support and unbrick roms  :'(
« Last Edit: January 28, 2013, 10:08:53 am by Vektor »

skelton

  • *****
  • Posts: 6508
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #31 on: January 28, 2013, 10:08:44 am »

Vektor I am afraid that you erased bootloader from NAND. Try the follwing, open the amlogic tool, select the config file (there should be a xml file in it), once you open select the upgrade file (update.zip or the name it has), and try to reflash it.

By the way, the amlogic burning toll is not needed at all to upgrade a firm, the firm in JXD webpage is basically to uograde from a sdcard, putting the files in micro sdcard and booting from recovery with Power and Volume'+ button.
So why using the amlogic tool? Since it can erase or bad flash the spl.bin file.
Retired

Damedus (OP)

  • *** Moderator
  • Posts: 1196
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #32 on: January 28, 2013, 10:09:11 am »
It's possible that he didn't turn debug mode on in the tablet before bricking it.... that would render adb totally usesless unfortunatly i think.

Unfortunately debugging was off, but I've found some interesting things about this bug. The Device is detected as M3-chip or M6-chip and then as usb mass storage. This is right. What's wrong is that the storage partition should contain some files coming from uImage_usb_burn to go on, but it's empty.
Update.zip and patch.zip does your log stop at hop 20?
~JXD 7300 Cook~
Devices:
JXD S7300B, PSP, Dingoo, Vita, 3ds, Kindle, ASUS Ti 700, SG2Sky, SG3, Note, Note 2, PS3, 360, Wii, WiiU, Asus quad-crossfire 7970 32g 4.8(8core) Ghz PC,ASUS GTX-71, ASUS H-1000, PS2, PSX, Jaguar, DC, SNES, Nes, SMS, Atari 2600, Genesis gen 2 /w cd & 32x. and a bunch of older consoles in collective storage (current:92 unique consoles)

Damedus (OP)

  • *** Moderator
  • Posts: 1196
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #33 on: January 28, 2013, 10:13:19 am »

Vektor I am afraid that you erased bootloader from NAND. Try the follwing, open the amlogic tool, select the config file (there should be a xml file in it), once you open select the upgrade file (update.zip or the name it has), and try to reflash it.

By the way, the amlogic burning toll is not needed at all to upgrade a firm, the firm in JXD webpage is basically to uograde from a sdcard, putting the files in micro sdcard and booting from recovery with Power and Volume'+ button.
So why using the amlogic tool? Since it can erase or bad flash the spl.bin file.

look at the firmware zip from willgoo skelton it has the burn tool bundled twice in it,It even has logs of fails. He posted doing the JXD progress with no luck, only other way would be using the tool to flash but the device is not waking up.
~JXD 7300 Cook~
Devices:
JXD S7300B, PSP, Dingoo, Vita, 3ds, Kindle, ASUS Ti 700, SG2Sky, SG3, Note, Note 2, PS3, 360, Wii, WiiU, Asus quad-crossfire 7970 32g 4.8(8core) Ghz PC,ASUS GTX-71, ASUS H-1000, PS2, PSX, Jaguar, DC, SNES, Nes, SMS, Atari 2600, Genesis gen 2 /w cd & 32x. and a bunch of older consoles in collective storage (current:92 unique consoles)

Vektor

  • **
  • Posts: 605
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #34 on: January 28, 2013, 10:13:54 am »
It's possible that he didn't turn debug mode on in the tablet before bricking it.... that would render adb totally usesless unfortunatly i think.

Unfortunately debugging was off, but I've found some interesting things about this bug. The Device is detected as M3-chip or M6-chip and then as usb mass storage. This is right. What's wrong is that the storage partition should contain some files coming from uImage_usb_burn to go on, but it's empty.
Update.zip and patch.zip does your log stop at hop 20?
hop 18, the bootm command

Damedus (OP)

  • *** Moderator
  • Posts: 1196
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #35 on: January 28, 2013, 10:25:53 am »
It's possible that he didn't turn debug mode on in the tablet before bricking it.... that would render adb totally usesless unfortunatly i think.

Unfortunately debugging was off, but I've found some interesting things about this bug. The Device is detected as M3-chip or M6-chip and then as usb mass storage. This is right. What's wrong is that the storage partition should contain some files coming from uImage_usb_burn to go on, but it's empty.
Update.zip and patch.zip does your log stop at hop 20?
hop 18, the bootm command
Udisk is not being booted. That firmware also has all the files. I think the problem might be a soft brick, but unlike odin i dont see if this tool will let me to flash individual parts of the firmware.
~JXD 7300 Cook~
Devices:
JXD S7300B, PSP, Dingoo, Vita, 3ds, Kindle, ASUS Ti 700, SG2Sky, SG3, Note, Note 2, PS3, 360, Wii, WiiU, Asus quad-crossfire 7970 32g 4.8(8core) Ghz PC,ASUS GTX-71, ASUS H-1000, PS2, PSX, Jaguar, DC, SNES, Nes, SMS, Atari 2600, Genesis gen 2 /w cd & 32x. and a bunch of older consoles in collective storage (current:92 unique consoles)

Vektor

  • **
  • Posts: 605
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #36 on: January 28, 2013, 10:27:44 am »
I post a log if this can be useful:

Code: [Select]
[11:16:36]AmlUsbIdentifyHost
[11:16:42]AmlUsbIdentifyHost
[11:16:43]AmlUsbIdentifyHost
[11:16:44]AmlUsbIdentifyHost
[11:16:46]AmlUsbIdentifyHost
[11:16:47]AmlUsbIdentifyHost
[11:16:48]AmlUsbIdentifyHost
[11:16:49]AmlUsbIdentifyHost
[11:16:51]AmlUsbIdentifyHost
[11:17:39]AmlUsbIdentifyHost
[11:17:39]AmlUsbRunBinCode:ram_addr=d9000000
[11:18:07]AmlUsbIdentifyHost
[11:18:08]AmlUsbIdentifyHost
[11:18:16]AmlUsbIdentifyHost
[11:18:16]AmlUsbTplCmd =crc 0x8f800000 520300 2d8529c3
[11:18:16]AmlUsbReadStatus
[11:18:18]AmlUsbIdentifyHost
[11:18:18]AmlUsbIdentifyHost
[11:18:18]AmlUsbRunBinCode:ram_addr=8f800000
[11:18:18]AmlUsbIdentifyHost
[11:18:18]IOCTL_IDENTIFY_HOST_Handler ret=-5
[11:18:18]reset worldcup device
[11:18:18]Reset WorldCup Device
[11:18:23]AmlUsbIdentifyHost
[11:18:24]AmlUsbIdentifyHost
[11:18:24]AmlUsbTplCmd =set_chgcur 0
[11:18:24]AmlUsbReadStatus
[11:18:25]AmlUsbIdentifyHost
[11:18:25]AmlUsbTplCmd =video dev bl_off
[11:18:25]AmlUsbReadStatus
[11:18:26]AmlUsbIdentifyHost
[11:18:26]AmlUsbTplCmd =video dev disable
[11:18:26]AmlUsbReadStatus
[11:18:27]AmlUsbIdentifyHost
[11:18:27]AmlUsbTplCmd =nand rom_protect off
[11:18:27]AmlUsbReadStatus
[11:18:28]AmlUsbIdentifyHost
[11:18:28]AmlUsbTplCmd =nand scrub 0 2000000
[11:18:28]AmlUsbReadStatus
[11:18:29]AmlUsbIdentifyHost
[11:18:30]AmlUsbIdentifyHost
[11:18:30]AmlUsbTplCmd =defenv
[11:18:30]AmlUsbReadStatus
[11:18:31]AmlUsbIdentifyHost
[11:18:31]AmlUsbTplCmd =setenv bootargs ${bootargs} a9_clk_max=600000000
[11:18:31]AmlUsbReadStatus
[11:18:32]AmlUsbIdentifyHost
[11:18:33]AmlUsbIdentifyHost
[11:18:33]AmlUsbTplCmd =cmd_in_mem 0x82000000
[11:18:33]AmlUsbReadStatus
[11:18:34]AmlUsbIdentifyHost
[11:18:34]AmlUsbTplCmd =save
[11:18:34]AmlUsbReadStatus
[11:18:35]AmlUsbIdentifyHost
[11:19:02]AmlUsbIdentifyHost
[11:19:02]AmlUsbTplCmd =crc 0x82000000 4432270 26a9d795
[11:19:02]AmlUsbReadStatus
[11:19:03]AmlUsbIdentifyHost
[11:19:03]AmlUsbTplCmd =bootm 0x82000000
[11:19:08]can not find ms devices
[11:19:09]can not find ms devices
[11:19:10]can not find ms devices
[11:19:11]can not find ms devices
[11:19:12]can not find ms devices
[11:19:13]can not find ms devices
[11:19:14]can not find ms devices
[11:19:16]can not find ms devices
[11:19:17]can not find ms devices
[11:19:18]can not find ms devices
[11:19:19]can not find ms devices
[11:19:20]can not find ms devices
[11:19:21]can not find ms devices
[11:19:23]can not find ms devices
[11:19:24]can not find ms devices
[11:19:25]can not find ms devices
[11:19:26]can not find ms devices
[11:19:27]can not find ms devices
[11:19:28]can not find ms devices
[11:19:29]can not find ms devices
[11:19:31]can not find ms devices
[11:19:32]can not find ms devices
[11:19:33]can not find ms devices
[11:19:34]can not find ms devices
[11:19:35]can not find ms devices
[11:19:36]can not find ms devices
[11:19:38]can not find ms devices
[11:19:39]can not find ms devices
[11:19:40]can not find ms devices
[11:19:41]can not find ms devices
[11:19:42]can not find ms devices
[11:19:43]can not find ms devices
[11:21:59]AmlUsbIdentifyHost
[11:21:59]AmlUsbRunBinCode:ram_addr=d9000000
[11:22:22]AmlUsbIdentifyHost
[11:22:24]AmlUsbIdentifyHost
[11:22:32]AmlUsbIdentifyHost
[11:22:32]AmlUsbTplCmd =crc 0x8f800000 520300 2d8529c3
[11:22:32]AmlUsbReadStatus
[11:22:33]AmlUsbIdentifyHost
[11:22:33]AmlUsbIdentifyHost
[11:22:33]AmlUsbRunBinCode:ram_addr=8f800000
[11:22:33]AmlUsbIdentifyHost
[11:22:34]IOCTL_IDENTIFY_HOST_Handler ret=-5
[11:22:34]reset worldcup device
[11:22:34]Reset WorldCup Device
[11:22:39]AmlUsbIdentifyHost
[11:22:40]AmlUsbIdentifyHost
[11:22:40]AmlUsbTplCmd =set_chgcur 0
[11:22:40]AmlUsbReadStatus
[11:22:41]AmlUsbIdentifyHost
[11:22:41]AmlUsbTplCmd =video dev bl_off
[11:22:41]AmlUsbReadStatus
[11:22:42]AmlUsbIdentifyHost
[11:22:42]AmlUsbTplCmd =video dev disable
[11:22:42]AmlUsbReadStatus
[11:22:43]AmlUsbIdentifyHost
[11:22:43]AmlUsbTplCmd =nand rom_protect off
[11:22:43]AmlUsbReadStatus
[11:22:44]AmlUsbIdentifyHost
[11:22:44]AmlUsbTplCmd =nand scrub 0 2000000
[11:22:44]AmlUsbReadStatus
[11:22:45]AmlUsbIdentifyHost
[11:22:46]AmlUsbIdentifyHost
[11:22:46]AmlUsbTplCmd =nand erase 2000000
[11:22:46]AmlUsbReadStatus
[11:22:47]AmlUsbIdentifyHost
[11:22:47]AmlUsbTplCmd =defenv
[11:22:47]AmlUsbReadStatus
[11:22:48]AmlUsbIdentifyHost
[11:22:49]AmlUsbTplCmd =setenv bootargs ${bootargs} a9_clk_max=600000000
[11:22:49]AmlUsbReadStatus
[11:22:50]AmlUsbIdentifyHost
[11:22:52]AmlUsbIdentifyHost
[11:22:52]AmlUsbTplCmd =cmd_in_mem 0x82000000
[11:22:52]AmlUsbReadStatus
[11:22:53]AmlUsbIdentifyHost
[11:22:53]AmlUsbTplCmd =save
[11:22:53]AmlUsbReadStatus
[11:22:54]AmlUsbIdentifyHost
[11:23:18]AmlUsbIdentifyHost
[11:23:18]AmlUsbTplCmd =crc 0x82000000 4432270 26a9d795
[11:23:18]AmlUsbReadStatus
[11:23:19]AmlUsbIdentifyHost
[11:23:19]AmlUsbTplCmd =bootm 0x82000000
[11:23:23]can not find ms devices
[11:23:25]can not find ms devices
[11:23:26]can not find ms devices
[11:23:27]can not find ms devices
[11:23:28]can not find ms devices
[11:23:29]can not find ms devices
[11:23:30]can not find ms devices
[11:23:32]can not find ms devices
[11:23:33]can not find ms devices
[11:23:34]can not find ms devices
[11:23:35]can not find ms devices
[11:23:36]can not find ms devices
[11:23:37]can not find ms devices
[11:23:38]can not find ms devices
[11:23:40]can not find ms devices
[11:23:41]can not find ms devices
[11:23:42]can not find ms devices
[11:23:43]can not find ms devices
[11:23:44]can not find ms devices
[11:23:45]can not find ms devices
[11:23:47]can not find ms devices
[11:23:48]can not find ms devices
[11:23:49]can not find ms devices
[11:23:50]can not find ms devices
[11:23:51]can not find ms devices
[11:23:52]can not find ms devices
[11:23:54]can not find ms devices
[11:23:55]can not find ms devices
[11:23:56]can not find ms devices
[11:23:57]can not find ms devices
[11:23:58]can not find ms devices
[11:23:59]can not find ms devices

Damedus (OP)

  • *** Moderator
  • Posts: 1196
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #37 on: January 28, 2013, 10:39:10 am »
I post a log if this can be useful:

Code: [Select]
[11:16:36]AmlUsbIdentifyHost
[11:16:42]AmlUsbIdentifyHost
[11:16:43]AmlUsbIdentifyHost
[11:16:44]AmlUsbIdentifyHost
[11:16:46]AmlUsbIdentifyHost
[11:16:47]AmlUsbIdentifyHost
[11:16:48]AmlUsbIdentifyHost
[11:16:49]AmlUsbIdentifyHost
[11:16:51]AmlUsbIdentifyHost
[11:17:39]AmlUsbIdentifyHost
[11:17:39]AmlUsbRunBinCode:ram_addr=d9000000
[11:18:07]AmlUsbIdentifyHost
[11:18:08]AmlUsbIdentifyHost
[11:18:16]AmlUsbIdentifyHost
[11:18:16]AmlUsbTplCmd =crc 0x8f800000 520300 2d8529c3
[11:18:16]AmlUsbReadStatus
[11:18:18]AmlUsbIdentifyHost
[11:18:18]AmlUsbIdentifyHost
[11:18:18]AmlUsbRunBinCode:ram_addr=8f800000
[11:18:18]AmlUsbIdentifyHost
[11:18:18]IOCTL_IDENTIFY_HOST_Handler ret=-5
[11:18:18]reset worldcup device
[11:18:18]Reset WorldCup Device
[11:18:23]AmlUsbIdentifyHost
[11:18:24]AmlUsbIdentifyHost
[11:18:24]AmlUsbTplCmd =set_chgcur 0
[11:18:24]AmlUsbReadStatus
[11:18:25]AmlUsbIdentifyHost
[11:18:25]AmlUsbTplCmd =video dev bl_off
[11:18:25]AmlUsbReadStatus
[11:18:26]AmlUsbIdentifyHost
[11:18:26]AmlUsbTplCmd =video dev disable
[11:18:26]AmlUsbReadStatus
[11:18:27]AmlUsbIdentifyHost
[11:18:27]AmlUsbTplCmd =nand rom_protect off
[11:18:27]AmlUsbReadStatus
[11:18:28]AmlUsbIdentifyHost
[11:18:28]AmlUsbTplCmd =nand scrub 0 2000000
[11:18:28]AmlUsbReadStatus
[11:18:29]AmlUsbIdentifyHost
[11:18:30]AmlUsbIdentifyHost
[11:18:30]AmlUsbTplCmd =defenv
[11:18:30]AmlUsbReadStatus
[11:18:31]AmlUsbIdentifyHost
[11:18:31]AmlUsbTplCmd =setenv bootargs ${bootargs} a9_clk_max=600000000
[11:18:31]AmlUsbReadStatus
[11:18:32]AmlUsbIdentifyHost
[11:18:33]AmlUsbIdentifyHost
[11:18:33]AmlUsbTplCmd =cmd_in_mem 0x82000000
[11:18:33]AmlUsbReadStatus
[11:18:34]AmlUsbIdentifyHost
[11:18:34]AmlUsbTplCmd =save
[11:18:34]AmlUsbReadStatus
[11:18:35]AmlUsbIdentifyHost
[11:19:02]AmlUsbIdentifyHost
[11:19:02]AmlUsbTplCmd =crc 0x82000000 4432270 26a9d795
[11:19:02]AmlUsbReadStatus
[11:19:03]AmlUsbIdentifyHost
[11:19:03]AmlUsbTplCmd =bootm 0x82000000
[11:19:08]can not find ms devices
[11:19:09]can not find ms devices
[11:19:10]can not find ms devices
[11:19:11]can not find ms devices
[11:19:12]can not find ms devices
[11:19:13]can not find ms devices
[11:19:14]can not find ms devices
[11:19:16]can not find ms devices
[11:19:17]can not find ms devices
[11:19:18]can not find ms devices
[11:19:19]can not find ms devices
[11:19:20]can not find ms devices
[11:19:21]can not find ms devices
[11:19:23]can not find ms devices
[11:19:24]can not find ms devices
[11:19:25]can not find ms devices
[11:19:26]can not find ms devices
[11:19:27]can not find ms devices
[11:19:28]can not find ms devices
[11:19:29]can not find ms devices
[11:19:31]can not find ms devices
[11:19:32]can not find ms devices
[11:19:33]can not find ms devices
[11:19:34]can not find ms devices
[11:19:35]can not find ms devices
[11:19:36]can not find ms devices
[11:19:38]can not find ms devices
[11:19:39]can not find ms devices
[11:19:40]can not find ms devices
[11:19:41]can not find ms devices
[11:19:42]can not find ms devices
[11:19:43]can not find ms devices
[11:21:59]AmlUsbIdentifyHost
[11:21:59]AmlUsbRunBinCode:ram_addr=d9000000
[11:22:22]AmlUsbIdentifyHost
[11:22:24]AmlUsbIdentifyHost
[11:22:32]AmlUsbIdentifyHost
[11:22:32]AmlUsbTplCmd =crc 0x8f800000 520300 2d8529c3
[11:22:32]AmlUsbReadStatus
[11:22:33]AmlUsbIdentifyHost
[11:22:33]AmlUsbIdentifyHost
[11:22:33]AmlUsbRunBinCode:ram_addr=8f800000
[11:22:33]AmlUsbIdentifyHost
[11:22:34]IOCTL_IDENTIFY_HOST_Handler ret=-5
[11:22:34]reset worldcup device
[11:22:34]Reset WorldCup Device
[11:22:39]AmlUsbIdentifyHost
[11:22:40]AmlUsbIdentifyHost
[11:22:40]AmlUsbTplCmd =set_chgcur 0
[11:22:40]AmlUsbReadStatus
[11:22:41]AmlUsbIdentifyHost
[11:22:41]AmlUsbTplCmd =video dev bl_off
[11:22:41]AmlUsbReadStatus
[11:22:42]AmlUsbIdentifyHost
[11:22:42]AmlUsbTplCmd =video dev disable
[11:22:42]AmlUsbReadStatus
[11:22:43]AmlUsbIdentifyHost
[11:22:43]AmlUsbTplCmd =nand rom_protect off
[11:22:43]AmlUsbReadStatus
[11:22:44]AmlUsbIdentifyHost
[11:22:44]AmlUsbTplCmd =nand scrub 0 2000000
[11:22:44]AmlUsbReadStatus
[11:22:45]AmlUsbIdentifyHost
[11:22:46]AmlUsbIdentifyHost
[11:22:46]AmlUsbTplCmd =nand erase 2000000
[11:22:46]AmlUsbReadStatus
[11:22:47]AmlUsbIdentifyHost
[11:22:47]AmlUsbTplCmd =defenv
[11:22:47]AmlUsbReadStatus
[11:22:48]AmlUsbIdentifyHost
[11:22:49]AmlUsbTplCmd =setenv bootargs ${bootargs} a9_clk_max=600000000
[11:22:49]AmlUsbReadStatus
[11:22:50]AmlUsbIdentifyHost
[11:22:52]AmlUsbIdentifyHost
[11:22:52]AmlUsbTplCmd =cmd_in_mem 0x82000000
[11:22:52]AmlUsbReadStatus
[11:22:53]AmlUsbIdentifyHost
[11:22:53]AmlUsbTplCmd =save
[11:22:53]AmlUsbReadStatus
[11:22:54]AmlUsbIdentifyHost
[11:23:18]AmlUsbIdentifyHost
[11:23:18]AmlUsbTplCmd =crc 0x82000000 4432270 26a9d795
[11:23:18]AmlUsbReadStatus
[11:23:19]AmlUsbIdentifyHost
[11:23:19]AmlUsbTplCmd =bootm 0x82000000
[11:23:23]can not find ms devices
[11:23:25]can not find ms devices
[11:23:26]can not find ms devices
[11:23:27]can not find ms devices
[11:23:28]can not find ms devices
[11:23:29]can not find ms devices
[11:23:30]can not find ms devices
[11:23:32]can not find ms devices
[11:23:33]can not find ms devices
[11:23:34]can not find ms devices
[11:23:35]can not find ms devices
[11:23:36]can not find ms devices
[11:23:37]can not find ms devices
[11:23:38]can not find ms devices
[11:23:40]can not find ms devices
[11:23:41]can not find ms devices
[11:23:42]can not find ms devices
[11:23:43]can not find ms devices
[11:23:44]can not find ms devices
[11:23:45]can not find ms devices
[11:23:47]can not find ms devices
[11:23:48]can not find ms devices
[11:23:49]can not find ms devices
[11:23:50]can not find ms devices
[11:23:51]can not find ms devices
[11:23:52]can not find ms devices
[11:23:54]can not find ms devices
[11:23:55]can not find ms devices
[11:23:56]can not find ms devices
[11:23:57]can not find ms devices
[11:23:58]can not find ms devices
[11:23:59]can not find ms devices
Yep Nand is erased, and Udisk never boots again, however the hash files are correct, so udisk doe snot seem to be faulty

missing the rest of the procedure:
Code: [Select]
[09:30:39]: command exec:bootm 0x82000000
[T 6][09:30:41]: boot uImage ...
[T 6][09:30:59]: find disk: J:
[T 6][09:31:00]: recoveyCommand:  wipe_data prepareCommand:
[T 6][09:31:00]: send command : wipe_data ok!
[T 6][09:31:04]: wipe_data success(wipe_data):ok
[T 6][09:31:05]: recoveyCommand:  wipe_cache prepareCommand:
[T 6][09:31:05]: send command : wipe_cache ok!
[T 6][09:31:07]: wipe_cache success(wipe_cache):ok
[T 6][09:31:08]: recoveyCommand:  update:update.zip prepareCommand:
[T 6][09:31:57]: copy successed:update.zip
[T 6][09:31:57]: send command : update:update.zip ok!
[T 6][09:33:51]: update:update.zip success(update:update.zip):ok
[T 6][09:33:53]: recoveyCommand:  update:patch.zip prepareCommand:
[T 6][09:34:15]: copy successed:patch.zip
[T 6][09:34:15]: send command : update:patch.zip ok!
[T 6][09:35:03]: update:patch.zip success(update:patch.zip):ok
[T 6][09:35:04]: recoveyCommand:  copy_media prepareCommand:
[T 6][09:35:05]: recoveyCommand:  shutdown prepareCommand:
[T 6][09:35:06]: send command : shutdown ok!
~JXD 7300 Cook~
Devices:
JXD S7300B, PSP, Dingoo, Vita, 3ds, Kindle, ASUS Ti 700, SG2Sky, SG3, Note, Note 2, PS3, 360, Wii, WiiU, Asus quad-crossfire 7970 32g 4.8(8core) Ghz PC,ASUS GTX-71, ASUS H-1000, PS2, PSX, Jaguar, DC, SNES, Nes, SMS, Atari 2600, Genesis gen 2 /w cd & 32x. and a bunch of older consoles in collective storage (current:92 unique consoles)

Vektor

  • **
  • Posts: 605
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #38 on: January 28, 2013, 10:50:44 am »
So.. the only way to fix it is to burn a special firmware with a fully working nand?

skelton

  • *****
  • Posts: 6508
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #39 on: January 28, 2013, 10:53:25 am »
[11:19:08]can not find ms devices

According to log, it seems as if device wasn't detected by the tool, when you connect it and detect it as m3-chip maybe you need to install a driver? I don't know if a driver is included, I haven't download that file.
Retired

Vektor

  • **
  • Posts: 605
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #40 on: January 28, 2013, 10:55:46 am »
Device is detected until step 17-18, then it turns to usb mass storage and does not get recognized. I install a driver that installs m3/m6 chip as worldcup device, but nothing else for the last part which doesn't work.

skelton

  • *****
  • Posts: 6508
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #41 on: January 28, 2013, 11:17:57 am »

Maybe you can try this, it's for Amlogic m3 but maybe works for the Mx too:

http://www.j1nx.nl/wp-content/uploads/downloads/2013/01/Create_recovery_sdcard_Amlogic.pdf
Retired

Dexidus

  • **
  • Posts: 976
JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #42 on: January 28, 2013, 11:34:32 am »
I think most important to me is swapping the sd and extsd so that i can use a 32gb card instead of the 8gb internal (like what skelton did for the s5300). I think i will take a look at the s5300 cleaning script and modify it to try to make it work on the s7300 (i hear i should use root explorer to find all the crap i want to remove, then modify the script accordingly). I'm just a but affraid to do it because i'd rather not have a bricked device haha

indask8

Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #43 on: January 28, 2013, 11:54:04 am »
Device is detected until step 17-18, then it turns to usb mass storage and does not get recognized. I install a driver that installs m3/m6 chip as worldcup device, but nothing else for the last part which doesn't work.

Amlogic flash tool requires an english windows (switching windows language to english will do), also it works better under Win7 and don't forget to "Run as administrator".

I know because I bricked an amlogic tablet because of this tool (french windows...), it worked fine once I switched to english.

Vektor

  • **
  • Posts: 605
Re: JXD S7300 Fixes, Firmware, Roms Thread.
« Reply #44 on: January 28, 2013, 12:16:25 pm »
It's taking me some more time since I've the SD reader only on a MacBook and it can't be added as device in a virtualbox ubuntu machine.

In the meantime, I'm installing win7 english too.

 

Post a new topic