Hanging on VEGA screen

[Guest browser01]

I am now 2hours yesterday and three today into trying to restore my Vega which is refusing to fully boot. Each time I boot it gets as far as the VEGA screen and then nothing. I have been trying to use the 'new' BSODFix and have had to uninstall and re-install the device several times. I have had andriod listed in the Windows device manager before and have had the dos screen up but this seems to do nothing. Now when I plug in the usb into my Windows Vista 32bit pc and attempt to put the vega into recovery mode it is automatically trying to install drivers for APX device. there is no sign of Android or Harmony in the device manager list. Q..do I let windows automatically install this driver? I have read on other posts that it is impossible to break these devices but I cannot get any further and there is no sign of the Vega becoming anything but a 'brick'. Sorry to use the forbidden word but I am getting really frustrated with this. Any simply worded advice (the dumber the better) will be greatly appreciated by this android newbie. BTW it has been working perfectly for months and I can think of no reason for this failure to have occurred??? B

[Guest Minimonkey]

Try simontas post to get the correct drivers on your pc: http://android.modaco.com/content/advent-v...iver-installer/

Then check out vega tools to run either the bsod or to install a new rom: http://android.modaco.com/content/advent-v...ega-tools-v3-0/

You can follow the guide on Myadventvega to get back to stock.

Edited April 19, 2011 by Minimonkey

[Guest warriorscot]

If you just want to put it back to stock 1.09 which is a good idea in the meantime just follow the instruction on the advent website and use the standard windows android drivers that download themselves. To install other things like custom roms you need the more specialised ADB drivers which is what people talk about replacing. There are ways around this if its really a problem its not 100% necessary to use the ADB windows drivers its just the most direct method.

Follow the advent full instructions first, get it working and then worry about messing around with drivers.

[Guest browser01]

If you just want to put it back to stock 1.09 which is a good idea in the meantime just follow the instruction on the advent website and use the standard windows android drivers that download themselves. To install other things like custom roms you need the more specialised ADB drivers which is what people talk about replacing. There are ways around this if its really a problem its not 100% necessary to use the ADB windows drivers its just the most direct method.

Follow the advent full instructions first, get it working and then worry about messing around with drivers.

OK done all that still nothing showing in device manager. Tried to run BSODFix and am getting this message in dos screen

C:\Users\***\Desktop>./tools/nvflash.exe -w --bl ./tools/bootloader.bin --downlo

ad 7 ./tools/boot.img --go

'.' is not recognized as an internal or external command,

operable program or batch file.

Press enter to continue:

So I press enter and then zilch. Have been here before several times and can't get passed this. AArrgghhhh!!!

Edited April 19, 2011 by browser01

[Guest Minimonkey]

Follow these instruction first then run the bsodfix instead of the advent vega image: http://www.myadventvega.co.uk/full_system_...nstructions.pdf

[Guest Zebrahead]

OK done all that still nothing showing in device manager. Tried to run BSODFix and am getting this message in dos screen

C:\Users\***\Desktop>./tools/nvflash.exe -w --bl ./tools/bootloader.bin --downlo

ad 7 ./tools/boot.img --go

'.' is not recognized as an internal or external command,

operable program or batch file.

Press enter to continue:

So I press enter and then zilch. Have been here before several times and can't get passed this. AArrgghhhh!!!

My mistake, I'll fix that now ^^

Sorry,

Zeb

[Guest warriorscot]

OK done all that still nothing showing in device manager. Tried to run BSODFix and am getting this message in dos screen

C:\Users\***\Desktop>./tools/nvflash.exe -w --bl ./tools/bootloader.bin --downlo

ad 7 ./tools/boot.img --go

'.' is not recognized as an internal or external command,

operable program or batch file.

Press enter to continue:

So I press enter and then zilch. Have been here before several times and can't get passed this. AArrgghhhh!!!

Or instead of missing around with might work tools, you could just put it back to stock.

[Guest Zebrahead]

My mistake, I'll fix that now ^^

Sorry,

Zeb

You should be able to download it from my other thread and it should work now ^^

Or ofc, as other's have said, you could just flash stock ^^.

Zeb

[Guest browser01]

OK done all that still nothing showing in device manager. Tried to run BSODFix and am getting this message in dos screen

C:\Users\***\Desktop>./tools/nvflash.exe -w --bl ./tools/bootloader.bin --downlo

ad 7 ./tools/boot.img --go

'.' is not recognized as an internal or external command,

operable program or batch file.

Press enter to continue:

So I press enter and then zilch. Have been here before several times and can't get passed this. AArrgghhhh!!!

Right I gave up on any form of recovery ...I have now got my tablet running 'as new' with v1.09 on it. Now all I have to do is to put on the latest custom rom and re-install all the apps again. What a waste of time. What a royal PITA. And I thought windows was iffy. This takes the biscuit. Now thinking of putting this hunk of junk on ebay. Q... anyone know of an idiots guide written for beginners like me as there must be hundreds of us in the same boat. BTW I did nothing different other than run the 1.09 update instead of the .bat file.

Edited April 19, 2011 by browser01

[Guest Minimonkey]

Right I gave up on any form of recovery ...I have now got my tablet running 'as new' with v1.09 on it. Now all I have to do is to put on the latest custom rom and re-install all the apps again. What a waste of time. What a royal PITA. And I thought windows was iffy. This takes the biscuit. Now thinking of putting this hunk of junk on ebay. Q... anyone know of an idiots guide written for beginners like me as there must be hundreds of us in the same boat. BTW I did nothing different other than run the 1.09 update instead of the .bat file.

Should have tried Vega tools....

This is nice:

http://android.modaco.com/content/advent-v...guides-how-tos/

Edited April 19, 2011 by Minimonkey

[Guest Zebrahead]

Right I gave up on any form of recovery ...I have now got my tablet running 'as new' with v1.09 on it. Now all I have to do is to put on the latest custom rom and re-install all the apps again. What a waste of time. What a royal PITA. And I thought windows was iffy. This takes the biscuit. Now thinking of putting this hunk of junk on ebay. Q... anyone know of an idiots guide written for beginners like me as there must be hundreds of us in the same boat. BTW I did nothing different other than run the 1.09 update instead of the .bat file.

I've made another thread which should allow you to restore your vega no matter what happens to it once you've made a backup.

It may seem like a PITA now, but once you have a backup, you can restore it no matter what - It's really quite smart.

I'm just sorry I couldn't fix my tool in time for you to fix it ^^

Zeb

[Guest warriorscot]

Tools are nice but its so much easier just to use the built in tools. You messed around with 3rd party community software what did you expect.

Actually installing the correct software for the device is a piece of pie. You shouldn't blame your errors on the device or the OS neither are perfect but most problems are usually user error of one kind or another.

And all the windows tools are nice, vega tools especially is very good but its so much easier just using the built in stuff. If you are getting a black screen for some reason you are most likely experiencing a problem from an installation error when you first put the rom on or a bug so restoring the image is a bit counter productive in some cases. A lot of the time its easier just to reinstall everything and then you can use clockwork to do what you want or just keep a fresh system.

[Guest Zebrahead]

Tools are nice but its so much easier just to use the built in tools. You messed around with 3rd party community software what did you expect.

Actually installing the correct software for the device is a piece of pie. You shouldn't blame your errors on the device or the OS neither are perfect but most problems are usually user error of one kind or another.

And all the windows tools are nice, vega tools especially is very good but its so much easier just using the built in stuff. If you are getting a black screen for some reason you are most likely experiencing a problem from an installation error when you first put the rom on or a bug so restoring the image is a bit counter productive in some cases. A lot of the time its easier just to reinstall everything and then you can use clockwork to do what you want or just keep a fresh system.

Whilst I agree that just restoring stock is simple, most 3rd party restorative tools actually use the stock installer, just only reinstalling parts of the system and not overwriting the users data. For this reason I disagree with discouraging the use of 3rd party restorative software - they boil down to exactly the same thing.

Zeb

[Guest premieral]

Whilst I agree that just restoring stock is simple, most 3rd party restorative tools actually use the stock installer, just only reinstalling parts of the system and not overwriting the users data. For this reason I disagree with discouraging the use of 3rd party restorative software - they boil down to exactly the same thing.

Zeb

+1 to this zeb, i for one see nothing but good in people trying to simplify tasks that others find difficult.

Keep up the good work :)

[Guest browser01]

Back again just to clarify the situation. The problem I was encountering was with windows (I think). It was seeing new hardware and automatically installing what it assumed was the right drivers. The 'fix' was to let it do its thing wrongly and then go to Device Manager and uninstall both the pad and ALL the drivers. Then by going into Control panel do another search for new hardware and then browse to the correct drivers and install. Before running the win.bat I had to click on the adb file to get it to install. Hope this makes sense to anyone out there struggling like I did..B