Dolby said

Thanx for the informatie how to upload the file. But i got now a problem.

 

C:\Android\android-sdk\platform-tools\adb devices

then press [Enter] and you should get a result similar to the following:

<strong>* daemon not running. starting it now on port 5037 *</strong> <strong>* daemon started successfully *</strong> <strong>List of devices attached</strong> <strong>0123456789ABCDEF        device</strong>

Was it working before? Did you set up the adb driver?

 

My arnova 7D G3 wil not found within de CMD, No devices attached found ?

Dolby said

Yes i set up the adb driver.

Which lines did you add in android-winusb.inf file?

Dolby said
I didn't add android-winusb.inf file. Becourse Windows 7 64-bit detectd my Arnova 7D 4G without any problem.

I tried already to use the android-winusb.inf driver but doesn't work. I get an error message that this drivers

are not 64-bit.

Just follow the tutorial:

Step 4. Get the driver. Here comes the tricky part – we don’t have the adb driver for all models, so you will have to make one yourself. No worries – it is not that difficult. 

Get ours from here. Unpack it in a directory that is most suitable for you. Now you will need to add support for your tablet. For that, you will first need to turn on usb debugging in the settings and then, connect your G3 device to your pc. Unknown device or AN7DG3 should appear. Then you go to your windows device manager(it is part of the control panel, but you can also just search for it).

Find your device(Arnova 7d G3 in in your case), first right click on it and then click on properties.

Click on Details and select hardware-id’s.

Now what you see there you would need to add in android_winusb.inf file which you can find in the adb driver you downloaded from above.

The lines you should add will probably look something like this:

;;; Arnova 7D G3
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_XXXX
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_XXXX&MI_01

Just add it straight after the Arnova 8c G3 lines. In our example, you can see that REV_0261 is also mentioned there, but normally, you don’t have to add it in the android_winusb.inf file.

You are in the right direction. You missed one small thing from the tutorial:

If you get $ in return, then type su. If you get # in return, just continue with the next line.

You got $, so you needed to type su aftrer that.

______

BTW, I just saw I forgot to add a small line in step 7, so here is the slightly edited step 7 for you to follow(because you completed some parts of it yesterday, I left them out in this message, so it should be easier for you). Check that adb is still working(adb devices again) and we can start. You will need to add the following lines in cmd(they are in italic):

cd C:Androidandroid-sdkPlatform-tools

adb shell su

(check you got here an #)

chmod 755 /sdcard/rkdump

/sdcard/rkdump /dev/block/mtdblock4/sdcard/update.img
Adb will state probably something like this:
update.img found (234654564 bytes) dumping... crc found (4 bytes, 0x0709e735 ) done
And then, you should be done. 
You don't need to type cat /proc/mtd this time, because you already know what partition is the backup and that's the only use of it. 

But have an small problem. I can't find the update.img file to send to the site.

Forgot about this. It is actually stored in /sdcard/update.img, but because MTP is a little bit a mess, you won't see the update.img file when you connect the tablet to your pc. So now restart cmd and type the following to get the update.img file transferred to your pc manually:

C:\Android\Android-sdk\Platform-tools\adb pull /sdcard/update.img C:\Android\dump\update.img

And then it should be located in C:\Android\dump\. If you have WinRar/7zip you can make a zip file, otherwise just upload it just like it is now on our artctablet uploader(mediafire, mijnbestand and all the others are also ok):

http://www.arctablet.com/blog/at-upload/

timika said

Dolby said
Thank you admin end Excelletor for the help you gived me allready. To make a image file from the Arnova 7D G3.

And now?

And now we need to finish testing/coooking the custom firmwares, make everything up and it will go online. A little bit patience.