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

Damedus · « **on:** January 27, 2013, 11:26:40 pm »

NCCE Custom Firmware

Custom Firmware:

Unofficial Changelog NCCE 2.0 by Vektor and Damedus:

-All fixes from 1.1 version
-Added bluetooth dongle support.
-Running on newest sources (2.2.2)
-New joystick driver, should improve input lag and sticks are now both real analogs.
-Completely new mapper, supports all of the old features plus some new ones. (instructions will be released!)
a. Profiles can be easily exported and edited as they are in XML format.
b. New stick/button modes can be easily added to the source. (If you're confident with programming).
c. It's specific for JXDS7300 controller, so at the moment external controllers are not working with it.
-XPMB Launcher: put your roms in specified folders to enjoy a psp-like rom launcher.
a. Automatic download of the covers for your collection.
b. Improved title-matching algorithm to avoid the download of the wrong covers (it's really accurate).
c. Shortcuts for media/video players.
d. Uses RetroArch by default, alternative emulators will be included in the next updates.
-Minimal setup: We removed all the useless stock applications.
-Mapper and driver source is open, suggestions and improvements are welcome!
-Some security fixes (untested)

NCCE V 1.1 by Vektor and Damedus:

Note: Firmwares include Kernel and are full clean installs of the OS thus you can downgrade and upgrade from any custom firmware to another.Just be sure to use the proper mod tool that belongs to the custom firmware.
News:
- All fixes from V1
- Apks in the bundle are zipaligned.
- SD card normal mode or swap mode.
- 1.7 Commits added
- Speed improvement and response times.
- New Governors to be used with NCPU
- Option of default system launcher to be Apex and a few others, after all NCCE is about customization.
- Swap options at install.
- Build Prop Tweaks
- AOSP basic features added.(CIFS, NTFS)
- New Open sourced Key Driver
- Exported Mapping tool to apk for easier upgrading without the need of a full flash.
- Heavily upgraded mapping tool to support new features.
- Game X tool has a easier on the eyes look.
- Minor changes on system and Commits submitted by skelton that jxd was to lazy to add on source.
- NCPU app for clock speeds and easy gov changes and manual tweaks.
- New unicorns and Monkeys live now on the framework, they tell me they want to work with us and let you know when there's updates available (OTA)
Bugs:
Game fixes cause a small of glitches on some games, its a known issue.

<a href="https://web.archive.org/web/20221002183859/https://www.youtube.com/watch?v=vOuEE7lAj7E" target="_blank">https://www.youtube.com/watch?v=vOuEE7lAj7E</a>

Firmware Tutorial:

Quote

1. Backup all data from your device.(Keep a backup of your apps and files on pc)
2. Download the NCCE_v1.1_googleplay.rar from the NCCE v1.1 link below and unzip it. You should have the following files:
- factory_update_param.aml
- patch_NCCE.zip
- update_NCCE.zip
3. Place all 3 files to the root of your sd card.
4. With the device off place the sd card in it, press the Vol+ and Power buttons at the same time until it enters the upgrade menu.
5. Wait untill greeted by the NCCE install screen.Here choose your options like sd swap, launcher, extra aplications and CPU speed. Once the device is finished it will reboot back to system fully updated. Enjoy the upgrade!

Note: To use the Mod File, place the mod_setup_NCCE in the root of the sd card. Turn the device on without a sdcard inserted while pressing vol+ and power.(This should bring you to the recovery menu). Select update from ext and choose the mod_setup_NCCE.zip. You will be greeted by an aroma menu with options to use sd swap and set the clock speed of the cpu. This file can be used at any time after the firmware is installed to change the sd swap and clock speed features(in the future there will be more options in this file).
Note: The new modfile is here. do not use the 1.0 modfile on 1.1!

Download:

NCCE V1.1
NCCE Screen Utility 50/60 V1.1
~~NCCE Swap/CPU Tool V1.1~~Coming Soon!
Mapper Credits: Damedus, Vektor, ratbuddy for sources, Anderxale for the initial hints, all the users believing in my project, special thanks to strider_mt2k for testings and help

and very special thanks to Skelton for his kindness and insight! And to all the monkeys and unicorns who have lost sleep for the creation of this.
Older Versions:
NCCE V1
NCCE Swap/CPU Tool V1
CMW by Kalatch
Hosting provided by revnja (thanks!)
---------------------------------------------------------------------------------------------------------------------------------------

NCPU

With this utility you'll be able to edit the CPU speed directly from it instead of rebooting, flashing kernels , using modTools , etc. For users confident with android environment the app also allows you to choose governor and setting its profile parameters. NCPU has also a feature to save your settings and applying them at boot

. This utility is free

.

NCPU V1
Source
Thanks Revnja for the hosting!

-------------------------------------------------------------------------------------------------------------------------------------------------

Willgoo is runing a special on jxd's!
1 JXD S7300 is $139.99 US dollars with shipping!

JXD One Unit Super Pack! - $149.99 US dollars

Two units combo - $285.99 US dollars!

All include shipping fees for the following countries:

Code: [Select]

    Austria
    Belgium
    Denmark
    United Kingdom
    Finland
    France
    Germany
    Greece
    Hungary
    Italy
    Ireland
    Luxembourg
    Netherlands
    Norway
    Poland
    Portugal
    Spain
    Sweden
    Switzerland
    Australia
    New Zealand
    Japan
    United States
    Canada

[/center]

NCCE install and 1st boot video with aroma:

<a href="https://web.archive.org/web/20221002183859/https://www.youtube.com/watch?v=Cv7q1dkw070" target="_blank">https://www.youtube.com/watch?v=Cv7q1dkw070</a>

Manual JXD Update tools:
Firmware Update tool(Clean Log,Drivers,English Tutorial) - USB Tool

- Tutorial(Translated into English by Damedus) Tutorial.doc

- Video Tutorial (Vektor)

<a href="https://web.archive.org/web/20221002183859/https://www.youtube.com/watch?v=nx34AmNwdQs" target="_blank">https://www.youtube.com/watch?v=nx34AmNwdQs</a>

Gamepad Testing Thread

Game Testing Thread

Videos:

Damedus' Unboxing Gamepad 2 from willgoo

<a href="https://web.archive.org/web/20221002183859/https://www.youtube.com/watch?v=r8NXiKSJaNs" target="_blank">https://www.youtube.com/watch?v=r8NXiKSJaNs</a>

ratbuddy's back panel dissasembly:

<a href="https://web.archive.org/web/20221002183859/https://www.youtube.com/watch?v=iJ9fGSR4l_o" target="_blank">https://www.youtube.com/watch?v=iJ9fGSR4l_o</a>

Damedus' CSP2 Emu Video:

<a href="https://web.archive.org/web/20221002183859/https://www.youtube.com/watch?v=2BbIRsCXAfQ" target="_blank">https://www.youtube.com/watch?v=2BbIRsCXAfQ</a>

The Afroman · « **Reply #1 on:** January 28, 2013, 12:49:04 am »

Great post. Hoping on a firmware with everything ripped out. Just plain JB. That way we can add what we need Al a carte.

yakub · « **Reply #2 on:** January 28, 2013, 01:54:19 am »

Internet connectivity needs testing.

Vektor · « **Reply #3 on:** January 28, 2013, 02:06:09 am »

Hi,

I tried to install the willgoo update, but something went wrong and now my screen is black whatever I do.

Can anyone help me? This is the program log file:

Code: [Select]

current pc version is: win7
current tool version is: V1.4.9.1220
-----importUpgradeFile-----filenameF:\JXD-S7300-upgrade\JXD-S7300-upgrade\S7300B-firmware-0121\S7300B-mx-20130121\mx-20130121\mx-20130121.zip
[T 2][03:03:18]: load spl ...
[T 2][03:03:18]: Transfer Complete! total size is 18912 Bytes
[T 2][03:03:27]: load uboot ...
[T 2][03:03:28]: Transfer Complete! total size is 520300 Bytes
[T 2][03:03:34]: test command exec: crc 0x8f800000 520300 2d8529c3
[T 2][03:03:34]: command exec: crc 0x8f800000 520300 2d8529c3
[T 2][03:03:34]: sendCommandWithReply: crc 0x8f800000 520300 2d8529c3 maxCount:30
[T 2][03:03:35]: begin run 8f800000
[T 2][03:03:39]: finish run 8f800000
[T 2][03:03:41]: command exec:set_chgcur 0
[T 2][03:03:42]: command exec:video dev bl_off
[T 2][03:03:43]: command exec:video dev disable
[T 2][03:03:44]: command exec:nand rom_protect off
[T 2][03:03:45]: command exec:nand scrub 0 2000000
[T 2][03:03:47]: command exec:nand erase 2000000
[T 2][03:03:52]: command exec:defenv
[T 2][03:03:53]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 2][03:03:54]: load command: setenv recovery_command --usb_burning
[T 2][03:03:56]: command exec:cmd_in_mem 0x82000000
[T 2][03:03:57]: command exec:save
[T 2][03:03:58]: load uimage ...
[T 2][03:03:58]: Transfer Complete! total size is 4432270 Bytes
[T 2][03:04:04]: test command exec: crc 0x82000000 4432270 26a9d795
[T 2][03:04:04]: command exec: crc 0x82000000 4432270 26a9d795
[T 2][03:04:04]: sendCommandWithReply: crc 0x82000000 4432270 26a9d795 maxCount:30
[T 2][03:04:05]: command exec:bootm 0x82000000
[T 2][03:04:07]: boot uImage ...
[T 2][03:04:43]: cannot find disk! 30times
[T 2][03:04:44]: failed because no connected device ,current step is 18

Damedus · « **Reply #4 on:** January 28, 2013, 02:41:24 am »

before i call it a full brick do you have a pc with windows xp on it?
I think it might be on Fastboot mode

Vektor · « **Reply #5 on:** January 28, 2013, 02:48:56 am »

I used XP on virtual machine.
However, when the error is given, the device is connected as a usb storage drive (empty) named:
Linux 3.0.8 with dwc_otg_pcd-File_backed_storage_gadget

Code: [Select]

current pc version is: xp
current tool version is: V1.4.9.1220
-----importUpgradeFile-----filenameE:\JXD-S7300-upgrade\S7300B-firmware-0121\S7300B-mx-20130121.zip
[T 1][03:54:23]: load spl ...
[T 1][03:54:23]: Transfer Complete! total size is 18912 Bytes
[T 1][03:54:29]: load uboot ...
[T 1][03:54:30]: Transfer Complete! total size is 520300 Bytes
[T 1][03:54:35]: test command exec: crc 0x8f800000 520300 2d8529c3
[T 1][03:54:35]: command exec: crc 0x8f800000 520300 2d8529c3
[T 1][03:54:35]: sendCommandWithReply: crc 0x8f800000 520300 2d8529c3 maxCount:30
[T 1][03:54:36]: begin run 8f800000
[T 1][03:54:43]: finish run 8f800000
[T 1][03:54:47]: command exec:set_chgcur 0
[T 1][03:54:48]: command exec:video dev bl_off
[T 1][03:54:49]: command exec:video dev disable
[T 1][03:54:51]: command exec:nand rom_protect off
[T 1][03:54:52]: command exec:nand scrub 0 2000000
[T 1][03:54:53]: command exec:nand erase 2000000
[T 1][03:54:58]: command exec:defenv
[T 1][03:55:00]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 1][03:55:01]: load command: setenv recovery_command --usb_burning
[T 1][03:55:02]: command exec:cmd_in_mem 0x82000000
[T 1][03:55:03]: command exec:save
[T 1][03:55:04]: load uimage ...
[T 1][03:55:07]: Transfer Complete! total size is 4432270 Bytes
[T 1][03:55:14]: test command exec: crc 0x82000000 4432270 26a9d795
[T 1][03:55:14]: command exec: crc 0x82000000 4432270 26a9d795
[T 1][03:55:14]: sendCommandWithReply: crc 0x82000000 4432270 26a9d795 maxCount:30
[T 1][03:55:15]: command exec:bootm 0x82000000
[T 1][03:55:18]: boot uImage ...
[T 1][03:55:57]: cannot find disk! 30times
[T 1][03:55:58]: failed because no connected device ,current step is 18

zombiesplay4eats · « **Reply #6 on:** January 28, 2013, 03:28:16 am »

Quote from: Vektor on January 28, 2013, 02:48:56 am

I used XP on virtual machine.
However, when the error is given, the device is connected as a usb storage drive (empty) named:
Linux 3.0.8 with dwc_otg_pcd-File_backed_storage_gadget

Code: [Select]
current pc version is: xp current tool version is: V1.4.9.1220 -----importUpgradeFile-----filenameE:\JXD-S7300-upgrade\S7300B-firmware-0121\S7300B-mx-20130121.zip [T 1][03:54:23]: load spl ... [T 1][03:54:23]: Transfer Complete! total size is 18912 Bytes [T 1][03:54:29]: load uboot ... [T 1][03:54:30]: Transfer Complete! total size is 520300 Bytes [T 1][03:54:35]: test command exec: crc 0x8f800000 520300 2d8529c3 [T 1][03:54:35]: command exec: crc 0x8f800000 520300 2d8529c3 [T 1][03:54:35]: sendCommandWithReply: crc 0x8f800000 520300 2d8529c3 maxCount:30 [T 1][03:54:36]: begin run 8f800000 [T 1][03:54:43]: finish run 8f800000 [T 1][03:54:47]: command exec:set_chgcur 0 [T 1][03:54:48]: command exec:video dev bl_off [T 1][03:54:49]: command exec:video dev disable [T 1][03:54:51]: command exec:nand rom_protect off [T 1][03:54:52]: command exec:nand scrub 0 2000000 [T 1][03:54:53]: command exec:nand erase 2000000 [T 1][03:54:58]: command exec:defenv [T 1][03:55:00]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000 [T 1][03:55:01]: load command: setenv recovery_command --usb_burning [T 1][03:55:02]: command exec:cmd_in_mem 0x82000000 [T 1][03:55:03]: command exec:save [T 1][03:55:04]: load uimage ... [T 1][03:55:07]: Transfer Complete! total size is 4432270 Bytes [T 1][03:55:14]: test command exec: crc 0x82000000 4432270 26a9d795 [T 1][03:55:14]: command exec: crc 0x82000000 4432270 26a9d795 [T 1][03:55:14]: sendCommandWithReply: crc 0x82000000 4432270 26a9d795 maxCount:30 [T 1][03:55:15]: command exec:bootm 0x82000000 [T 1][03:55:18]: boot uImage ... [T 1][03:55:57]: cannot find disk! 30times [T 1][03:55:58]: failed because no connected device ,current step is 18

If you have android sdk configured you could try the command "fastboot devices", if your device shows up in the list, then it is indeed stuck in fastboot mode, and you could use fastboot to continue flashing the image.

If you haven't already got android sdk configured, your best bet for fixing this problem is probably Linux.... why? Because in Linux, you build your ADB drivers manually, it doesn't rely on the computer properly detecting anything, also Linux has tools for gathering a WHOLE lot more information than can be done in Windows..... If you do have access to a Linux machine, you could follow this guide to get Android SDK installed and configured for your device.

I doubt it's a full brick, android devices are actually pretty hard to fully brick unless the hardware itself malfunctions, or if something goes wrong in flashing the bootloader and recovery images, normal firmware flashing probably can't fully brick an android device.

okayvin · « **Reply #7 on:** January 28, 2013, 03:44:26 am »

did your device brick because you customized the firmware?
http://boards.dingoonity.org/android-devices/attempt-to-customize-jxd-s7300/

i'm asking because i am wondering if it is safe to use the default firmware update, or if it was the default firmware update that bricked your device

Vektor · « **Reply #8 on:** January 28, 2013, 04:25:54 am »

No, I bricked while making the usb flash by willgoo linked in this topic.

I'm installing ubuntu on VM and I'll let you know asap.

UPDATE: Both Android SDK on Linux and Windows don't list the JXD in 'fastboot devices'. In devices manager the JXD is recognized as M6-CHIP or M3-CHIP without drivers, worldcup device with drivers.

I found this topic and I will install a 32bit xp partition.

wrc1010 · « **Reply #9 on:** January 28, 2013, 05:08:42 am »

Can someone create a video tutorial on how to update the new firmware for jxd s7300 and also how to make the micro tf card 64gb class 10 working on jxd s7300?

New user here for jxd s7300.

Damedus · « **Reply #10 on:** January 28, 2013, 05:09:52 am »

Quote from: Vektor on January 28, 2013, 04:25:54 am

No, I bricked while making the usb flash by willgoo linked in this topic.

I'm installing ubuntu on VM and I'll let you know asap.

UPDATE: Both Android SDK on Linux and Windows don't list the JXD in 'fastboot devices'. In devices manager the JXD is recognized as M6-CHIP or M3-CHIP without drivers, worldcup device with drivers.

I found this topic and I will install a 32bit xp partition.

That's why I said if you had XP. If the device is not on fastboot then its most likely stuck on update waiting to "detect" the device that your log says it fails to do(OS specific/Driver Specific, its a magical thing that windows xp 32 seems to ignore and just works with 90% of devices on black screens down at the shop) otherwise id have to find the button combo for the device have the firmware on a sd card and see if it supports direct update from sd via hardware buttons(makes sense to have it but im not sure JXD placed it) not at the shop so I can't test button combos at boot.

It's most likely menu and power.
Also was the device booting before you flashed the new firmware and did you use USB-Burning-tool-v1.4.9.1220 for it?

Code: [Select]

<command run="true" address="0xd9000000" path="usb_spl.bin" sn="0">load spl</command><command run="false" address="0x8f800000" path="u-boot-orig.bin" sn="1">load uboot</command><command sn="2">crc 0x8f800000 size value</command><command sn="3">run 0x8f800000</command><command sn="4">set_chgcur 0</command><command sn="5">video dev bl_off</command><command sn="6">video dev disable</command><command sn="7">nand rom_protect off</command><command sn="8">nand scrub 0 2000000</command><command sn="9">nand erase 2000000</command><command sn="10">defenv</command><command sn="11">setenv bootargs ${bootargs} a9_clk_max=600000000</command><command address="0x82000000" sn="12" cmd="setenv recovery_command --usb_burning">load addr</command><command sn="13">cmd_in_mem 0x82000000</command><command sn="14">save</command><command run="false" address="0x82000000" path="uImage_usb_burning" sn="15">load uimage</command><command sn="16">crc 0x82000000 size value</command><command sn="17">bootm 0x82000000</command><command sn="18">wipe_data</command><command sn="19">wipe_cache</command><command sn="20" count="150">update:update.zip</command><command sn="21" count="150">update:patch.zip</command><command sn="22">copy_media</command><command sn="23">shutdown</command>

Vektor · « **Reply #11 on:** January 28, 2013, 05:41:39 am »

Quote from: Damedus on January 28, 2013, 05:09:52 am

That's why I said if you had XP. If the device is not on fastboot then its most likely stuck on update waiting to "detect" the device that your log says it fails to do(OS specific/Driver Specific, its a magical thing that windows xp 32 seems to ignore and just works with 90% of devices on black screens down at the shop) otherwise id have to find the button combo for the device have the firmware on a sd card and see if it supports direct update from sd via hardware buttons(makes sense to have it but im not sure JXD placed it) not at the shop so I can't test button combos at boot.

It's most likely menu and power.
Also was the device booting before you flashed the new firmware and did you use USB-Burning-tool-v1.4.9.1220 for it?

Code: [Select]
<command run="true" address="0xd9000000" path="usb_spl.bin" sn="0">load spl</command><command run="false" address="0x8f800000" path="u-boot-orig.bin" sn="1">load uboot</command><command sn="2">crc 0x8f800000 size value</command><command sn="3">run 0x8f800000</command><command sn="4">set_chgcur 0</command><command sn="5">video dev bl_off</command><command sn="6">video dev disable</command><command sn="7">nand rom_protect off</command><command sn="8">nand scrub 0 2000000</command><command sn="9">nand erase 2000000</command><command sn="10">defenv</command><command sn="11">setenv bootargs ${bootargs} a9_clk_max=600000000</command><command address="0x82000000" sn="12" cmd="setenv recovery_command --usb_burning">load addr</command><command sn="13">cmd_in_mem 0x82000000</command><command sn="14">save</command><command run="false" address="0x82000000" path="uImage_usb_burning" sn="15">load uimage</command><command sn="16">crc 0x82000000 size value</command><command sn="17">bootm 0x82000000</command><command sn="18">wipe_data</command><command sn="19">wipe_cache</command><command sn="20" count="150">update:update.zip</command><command sn="21" count="150">update:patch.zip</command><command sn="22">copy_media</command><command sn="23">shutdown</command>

I used all the files provided in your link in the first post of this topic. I've already run the burning tools on 32bit XP with no success, I'll try on a real xp machine to see if something changes.

And yes the device was working very well before the update. I pressed power + vol- as in the instructions, then plugged usb, installed driver and run usbtools.

zombiesplay4eats · « **Reply #12 on:** January 28, 2013, 06:16:21 am »

Quote from: Vektor on January 28, 2013, 05:41:39 am

Quote from: Damedus on January 28, 2013, 05:09:52 am

That's why I said if you had XP. If the device is not on fastboot then its most likely stuck on update waiting to "detect" the device that your log says it fails to do(OS specific/Driver Specific, its a magical thing that windows xp 32 seems to ignore and just works with 90% of devices on black screens down at the shop) otherwise id have to find the button combo for the device have the firmware on a sd card and see if it supports direct update from sd via hardware buttons(makes sense to have it but im not sure JXD placed it) not at the shop so I can't test button combos at boot.

It's most likely menu and power.
Also was the device booting before you flashed the new firmware and did you use USB-Burning-tool-v1.4.9.1220 for it?

Code: [Select]
<command run="true" address="0xd9000000" path="usb_spl.bin" sn="0">load spl</command><command run="false" address="0x8f800000" path="u-boot-orig.bin" sn="1">load uboot</command><command sn="2">crc 0x8f800000 size value</command><command sn="3">run 0x8f800000</command><command sn="4">set_chgcur 0</command><command sn="5">video dev bl_off</command><command sn="6">video dev disable</command><command sn="7">nand rom_protect off</command><command sn="8">nand scrub 0 2000000</command><command sn="9">nand erase 2000000</command><command sn="10">defenv</command><command sn="11">setenv bootargs ${bootargs} a9_clk_max=600000000</command><command address="0x82000000" sn="12" cmd="setenv recovery_command --usb_burning">load addr</command><command sn="13">cmd_in_mem 0x82000000</command><command sn="14">save</command><command run="false" address="0x82000000" path="uImage_usb_burning" sn="15">load uimage</command><command sn="16">crc 0x82000000 size value</command><command sn="17">bootm 0x82000000</command><command sn="18">wipe_data</command><command sn="19">wipe_cache</command><command sn="20" count="150">update:update.zip</command><command sn="21" count="150">update:patch.zip</command><command sn="22">copy_media</command><command sn="23">shutdown</command>

I used all the files provided in your link in the first post of this topic. I've already run the burning tools on 32bit XP with no success, I'll try on a real xp machine to see if something changes.

And yes the device was working very well before the update. I pressed power + vol- as in the instructions, then plugged usb, installed driver and run usbtools.

Good idea.... I'm not really sure how great the USB support with virtual machines is, I'm sure it's a passthrough of some type at best, in any event, we wish you luck...... and I'm sure this will have anyone else with ideas of flashing this firmware holding their breath while they're doing it, lol

Damedus · « **Reply #13 on:** January 28, 2013, 06:17:24 am »

USB tools Tips .doc translated to English on main post.

wrc1010 · « **Reply #14 on:** January 28, 2013, 06:45:01 am »

Quote from: Damedus on January 28, 2013, 06:17:24 am

USB tools Tips .doc translated to English on main post.

1) Does the firmware from the willgoo is same as the official firmware from jxd website? If not, what are the different?

2) Does the tutorial you post on the first post is how to update the jxd s7300?

3) Can you also teach how to make the micro tf card 64gb work on jxd s7300?

4) Did you already swap the external as internal memory?

Damedus · « **Reply #15 on:** January 28, 2013, 06:58:12 am »

Quote from: wrc1010 on January 28, 2013, 06:45:01 am

Quote from: Damedus on January 28, 2013, 06:17:24 am
USB tools Tips .doc translated to English on main post.

1) Does the firmware from the willgoo is same as the official firmware from jxd website? If not, what are the different?

2) Does the tutorial you post on the first post is how to update the jxd s7300?

3) Can you also teach how to make the micro tf card 64gb work on jxd s7300?

4) Did you already swap the external as internal memory?

Yes its the same firmware Chinese instructions and all, I added a rough draft translation on a mediafire doc beside the firmware(my Chinese is mega rusty+ using google to speed me up).
The tutorial just states how to use the USB burn tool. The drivers are there and all in the folder and its detected (on windows 8x64 at least) as a worldcup device.
as for using the card deen said it wont be automounted at boot, rather once the device boots you can mount it. then use a app (no scripts yet sorry) to mount the usual gameloft/data/android folders. however on a reboot you must force end the redirect apk, mount the sd card and run it again. Ill look at this on my 32g card tomorow and see if the mount problem is just something with 64 gig cards.

Note: anyone that sees a good deal on a 64 gig card let me know I need a few, I have around 30 32 gig ones(got a good deal on them) so never felt the need to get 64 gig ones but I think my infinity and JXD deserve one.

Deen0X · « **Reply #16 on:** January 28, 2013, 07:01:01 am »

Quote from: wrc1010 on January 28, 2013, 06:45:01 am

1) Does the firmware from the willgoo is same as the official firmware from jxd website? If not, what are the different?

Yes, are the same

Quote from: wrc1010 on January 28, 2013, 06:45:01 am

2) Does the tutorial you post on the first post is how to update the jxd s7300?

yes

Quote from: wrc1010 on January 28, 2013, 06:45:01 am

3) Can you also teach how to make the micro tf card 64gb work on jxd s7300?

Damedus posted a way to make it to work on the first post.

Quote from: wrc1010 on January 28, 2013, 06:45:01 am

4) Did you already swap the external as internal memory?

I tried, but the system become unstable. Hope Damedus or another guy can get this to work propertly.

Deen0X · « **Reply #17 on:** January 28, 2013, 07:03:24 am »

Quote from: Damedus on January 28, 2013, 06:58:12 am

Ill look at this on my 32g card tomorow and see if the mount problem is just something with 64 gig cards.

I have issues with automount only with 64GB Cards.
i tested 32GB cards and the device don?t have problems, automount correctly on each reboot and directorybind automatic redirects work without problems (don?t need to mount manually)

Damedus · « **Reply #18 on:** January 28, 2013, 07:18:35 am »

so its although the device will read 64 gig cards, they are invisible upon boot. Lovely that's a load order error. Wondering if a simple script to rerun mounting after the .so has loaded will fix this.

also the firmware's framework includes BT, Phone files and a lot of files that can be truncated and optimized for the device. Id keep the OTG BT framework but i see no need for a few of the files (exept the call for turning on/off if it works with the OTG dongles (thinking of a 3mm paper-pin L shaped OTG cable)use a silicon case, atach the BT+ a open USB port on the outside back laying flat towards the bottom left. Adding a batery pack as thick as the usb/bt to cover the rest of the back. then plasticoat the case to make it all 1 unit thing.(the plugged OTG(top)/power plug(bottom) would keep the case aligned, and since most cases would be a bit small for the tablet it would be a snug stretched fit(heat case fitting) since I would use ribbon cable(paperclip cables) it would be flat only adding 3mmup and 3 mm down (so a 3mm thick silicon case would be perfect.) would be thicker but at least id get BT,USB full port and extra batery.

Vektor · « **Reply #19 on:** January 28, 2013, 07:27:13 am »

A little update on my situation: I tried to install winxp but it gave me bsod since it is too recent to run it.
I've tried vmware player and virtualbox to run xp 32bit vm. The issue is that at about 70-75% of the process the tablet turns into a usb storage drive and cannot find some kind of file.

It's the same with 8-64bit and xp32bit

Jul	OCT	Nov
	02
2021	2022	2023

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

Damedus (OP)

Damedus (OP)

Damedus (OP)

Damedus (OP)

Damedus (OP)

Damedus (OP)