Forum switched to read-only as of 2020/06/01
|Latest product reviews|
I've upgraded my childpad with your first CFW without any problems.
Now I was trying to go to the 4.0.4 but it doesn't work. When connecting the tablet in recovery mode it uses a different device ID. I added the following two lines to rockusb.inf:
The driver got installed and I started EvolutionRKtool. I got some error messages when clicking EraseIDB, so I changed setting.ini accordingly to:
But still I get an error message ("error during boot download" or the like).
Do I also have to change the values of [MSC_ID] and where can I find the correct values?
Any other ideas?
Had installed new firmware, but lots of problems appeared so far.. - could not install some applications which were installed before, still could not move applications to SD card, though the button "move to SD card" exists, it says "could not move application". Could you kindly help me to settle these problems? Many thanks in advance!
did you try post nr. 12?
unmount and mount internal storage?
Here's a rundown of the six USB connection modes, what works and what doesn't:
- MTP: No changes, if it worked with the stock ROM or kasty 40-04, it will still work.
- PTP: Same as above.
- MTP + USB debugging: ADB still works, MTP not possible while USB debugging is enabled, didn't work in stock or kasty 40-04 either.
- PTP + USB debugging: USB Device 0E79:145B appears (not apparent in kasty), ADB not working - solution in next post.
- Mass storage: Shows up on my machine as "Linux File-CD Gadget USB Device", but installs just fine as USB Mass Storage device.
- Mass storage + USB debugging: Mass storage works fine (disconnects and reconnects when toggling USB debugging), USB Device 0E79:1457 appears (not apparent in kasty since mass storage didn't exist in it), ADB not working - working on solution.
Conclusion: MTP and PTP never worked at the same time as USB debugging anyway, but let's fix the unknown devices, because we really want Mass storage mode to work at the same time as ADB.
WARNING: If you do not know the anatomy of an .inf file (or don't even know what an .inf file is), i suggest you do not follow this recipe!
First i assume you have the ADB driver installed already. If not, head over to the following URL and follow that recipe (Arnova have the same Vendor ID as Archos): http://www.archos.com/support/support_tech/updates_adb.html?lang=en
Then we need to find the right .inf file in c:\windows\inf - it is typically called "oemXX.inf" where XX is a one to four digit number. Note that the location might differ for you - i'm still on XP. The file can be found doing a text search for "Android WinUsb driver installation" without the quotes.
Then we have to add a few lines, BOTH to the [Google.NTx86] and [Google.NTamd64] sections. They are as follow:
;;; Arnova ChildPad (capacitive, UMASS)
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1457
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1457&MI_01
;;; Arnova ChildPad (capacitive, MTP)
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1459
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1459&MI_01
;;; Arnova ChildPad (capacitive, PTP)
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_145B
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_145B&MI_01
Save this file with the changes, pull your USB cable if connected, insert it again, enable USB debugging on your CP, and choose each of the three USB connection modes in succession, waiting for the drivers to install every time.
This works for me - YMMV - and both gives you the combined Mass storage + ADB mode, plus it gets rid of those terrible unknown devices in device manager. Note that if your Windows doesn't pop up offering to install the driver in any of the three modes, you will have to find the device in Device Manager, right click and choose "update driver".
Hope this is of use to someone!
Hi and thanks a lot for the new firmware. It is really great to have this better experience.
What seems to be serious is that after applying the trick for installing the apps that couldn't be installed (trick with unmount/mount) and then moving them to internal sdcard a new problem appears.
Specifically, everytime that i restart the childpad, apps are not accesible. I need to unmount/mount again the internal sdcard so as to make them accesible again.
I moved the apps with Titanium backup and not with the default ics way. But i think that this has nothing to do with the problem.
Now, everytime that my son turns on the tablet, he asks me to do that procedure again.
For those that can't move apps to internal sdcard just unmount and mount it again. Then works ok. But how we can fix this?
Thanks again and waiting for the JellyBean firmware!!!
P.S. How we can take advantage of the external sdcard?
Is there anyone that upgraded with this firmware and put 1.5 GB setting for the apps partition of internal storage? Rhis was my first try, but when i restarted form CWM touch i was stacked in the arnova logo. So i did the procedure again for 1G and worked ok.
After 48 hours of working just fine with 4.0.4, my CP also does the "App not installed" thing now, and it takes me several remounts to get it working again.
As for taking advantage of external (as in real) SD cards, the /mnt structure needs a few changes, since it is wrong. The physical SD card should be mounted inside the NAND mount folder, and not next to it. Three files in kernel.img and one in system.img need changes, and i do not have the required skills to do this.
There are more bugs in /init.rc - all those numbered folders in the root directory are due to bad mkdir syntax. If exelletor would like to fix all this, i'd gladly help where i can.
Most Users Ever Online: 803
Currently Browsing this Page:
Devices in use: Desktop (111), Phone (4)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech