akes, on 09 September 2011 - 10:24 PM, said:
Hi
Trying out flashing a new ROm and having some interesting problems. Its a new Vega tablet, and I am using a Windows7 Prof x64 OS. I can see the Vega on the PC device manager, and have already managed to transfer files using the Advent Transfer Companion. After using the Transfer Companion, I have turned ON USB Debugging and turned the USB connection OFF so it can no longer be seen as a disk. However, when I run windows-install.bat, this hangs after *daemon started successfully*.
What should happening after I see *daemon started successfully*?
How long should I wait before terminating the batch file?
What should happen on the Vega while the script is running?
I have tried using "adb-windows devices" in another shell - but it does not list any devices.
I am wondering if the port is being blocked by Windows Firewall?
Any other ideas?
many thanks
akes
Fixed. The problem was a clash of drivers. I used the AUDI utility (see
http://android.modac...ver-installer/) to correct the driver problem, then did the install-windows.bat file to complete the update.
I had previously set the adb-windows.exe program on my machine to Run as Administrator - and the security settings kept popping up to get confirmation each time adb-windows was called in the script. Not a problem, just kept clicking Yes.
To answer my own questions, the you should see activity on the PC screen within a few seconds of running install-windows.bat (and seeing *daemon started successfully*), the Vega itself shuts off the screen (mainly because of the power-saving screen timeout), and after the script runs, the Vega reboots.
I had installed one app - which I used the Settings->Applications to move to the SD card.
Once the installation had finished, and the Vega rebooted, all my settings were retained (so no need to set up wifi, etc again).
thanks
akes
Edited by akes, 10 September 2011 - 10:02 AM.