tired of trying !

[Guest simonta]

Glad it's sorted and thanks for the thanks, but community effort for sure. I only learned what needed to be done by watching others.

Cheers

[Guest fractured]

Glad it's sorted and thanks for the thanks, but community effort for sure. I only learned what needed to be done by watching others.

Cheers

I will be watching even more now Thanks

[Guest cobra111]

Really glad you kept at it, it's so worth it.

[Guest Bobby Elliott]

I share your pain. The process is not straight-forward for anyone (and throw-away lines like "boot into recovery mode" for a newbie - even an *expert* newbie - are horrendous). Not helped by atrocious system software (recovery mode is a blank screen - give that software engineer a prize).

But the real masochist has to try to get a custom ROM onto the device using a Windows 7 64-bit PC. It's an exercise in agony. Someone should have put us out of our pain by simply stating: "using an old laptop running XP for this".

In fact, the lack of straight-forward, common sense advice is a recurring theme on most threads. It's not helped by some people telling you to "check other posts on the forum", since there are around 20,000 posts and that is simply not helpful.

I've experienced less frustration writing operating systems in machine code.

[Guest cobra111]

I've got an 9 year old compaq brick of a laptop that is kept solely for flashing roms, (it's no good for anything else). My wife was going on about giving it away to our 3 year niece as a toy, you can guess what my answer was.

Flashing should be easier on Vista and 7 but until then the antiques will stay in drawers or cupboards for times like this. Maybe we should start a business selling these old things as flashing tools.

[Guest jinkyjim]

I flashed my vega yesterday, on WIN7.

I tried a few guides but no luck, then i tried simonta's guide and as if by magic it worked. WOOOOOHOOOOOOOO

The two hour's i was trying to flash was my most frustrating time on computers. i was ready to bounce it off the wall, lol

[Guest simonta]

I share your pain. The process is not straight-forward for anyone (and throw-away lines like "boot into recovery mode" for a newbie - even an *expert* newbie - are horrendous). Not helped by atrocious system software (recovery mode is a blank screen - give that software engineer a prize).

But the real masochist has to try to get a custom ROM onto the device using a Windows 7 64-bit PC. It's an exercise in agony. Someone should have put us out of our pain by simply stating: "using an old laptop running XP for this".

In fact, the lack of straight-forward, common sense advice is a recurring theme on most threads. It's not helped by some people telling you to "check other posts on the forum", since there are around 20,000 posts and that is simply not helpful.

I've experienced less frustration writing operating systems in machine code.

With respect, I don't think you have stopped to think about this.

Not helped by atrocious system software (recovery mode is a blank screen - give that software engineer a prize).

This is without doubt one of the greatest strengths of the Vega and many have come to love it. It's part of what makes the Vega unbrickable. The recovery mode is hardwired and is neither affected by flashing the Vega or dependent in any way on the OS. It does exactly what is required to enable flashing and no more. If it was to start loading device drivers, running the display etc then it would not be as robust. Contrary to your assessment, I see it as a great piece of design. It has saved many a poor soul.

But the real masochist has to try to get a custom ROM onto the device using a Windows 7 64-bit PC. It's an exercise in agony. Someone should have put us out of our pain by simply stating: "using an old laptop running XP for this".

I tried two searches on this forum. The first was simply x64. In the first 5 results, were these two guides:

http://android.modaco.com/content/advent-v...-wrong-win7-64/

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

The next search I used was "Windows 7 64". In the first 5 results, are these guides:

http://android.modaco.com/content/advent-v...p-update-guide/

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

All of these guides represent hours of work by volunteers who ask for no more than the satisfaction of knowing that they have helped and contributed.

(and throw-away lines like "boot into recovery mode" for a newbie - even an *expert* newbie - are horrendous)

Given the guides above (and there are many more, including Youtube videos - and they took my less than 2 minutes to find), you seem to be suggesting that those same people, who give up many hours already, should be repeating the same step by step "noob" guides in every new topic asking the same questions again and again and in every response to "I can't get my USB drivers loaded".

"Booting into recovery" is about the only thing that Advent document. The procedure is documented on the insert in the box and in the only document Advent has published on Myadventvega - which is referenced in the box and on the initial home screen of a stock Vega. Do you consider it unreasonable that I should expect people to read for themselves how to do this? Do you want me to give the instructions each time I respond to a post (probably in the order of 20 times per week), to go and find the guides and provide links in every response (when it takes so little time to find them) or what?

Finally, I very deliberately give people enough information but not the full story. Two reasons. One, I don't have time to give the full story so I do the best I can and two because I have a futile hope that people will search, read and learn for themselves because there is nothing more effective than helping someone to help themselves.

What is YOUR solution to the problem? I would welcome a better way of doing things.

Edited April 6, 2011 by simonta

[Guest simonta]

Sorry, dupe...

Edited April 6, 2011 by simonta

[Guest Bobby Elliott]

What is YOUR solution to the problem? I would welcome a better way of doing things.

If I have the time, I will write a short FAQ for the new purchaser of a Vega. There is lots of helpful advice scattered throughout this forum and I will link to that - but in context and with warnings about terseness and errors (many procedures here have at least one - sometimes serious - mistake in them).

If the writers of the system software had completed Comp Sci 101 they would know that a blank screen in unacceptable. A few lines of code could have produced a short message such as "Recovery mode entered...". This is the only device I have came across, in 36 years of working with computers, that does this.

[Guest simonta]

If I have the time, I will write a short FAQ for the new purchaser of a Vega. There is lots of helpful advice scattered throughout this forum and I will link to that - but in context and with warnings about terseness and errors (many procedures here have at least one - sometimes serious - mistake in them).

If the writers of the system software had completed Comp Sci 101 they would know that a blank screen in unacceptable. A few lines of code could have produced a short message such as "Recovery mode entered...". This is the only device I have came across, in 36 years of working with computers, that does this.

Then you've never worked on an IBM370 :D

I also still maintain that no reliance on OS or drivers of any kind is a strength but it is what it is and I agree to differ.

If you do an FAQ, the number one error I see in the guides is that "update driver" is recommended. This will usually fail, particularly on Vista or 7 and if the user has made previous unsuccessful attempts. Manually installing drivers will also often fail on Vista/7 if the user is not running as administrator and few people understand the difference between being a member of the local admins group and the real administrator with UAC enabled. Disabling UAC is something I would never recommend. If you see my guide, it avoids both of these by using "add new hardware" rather than "update driver" and running device manager as admin, the only easy way to do this that I have found is via running mmc.exe.

The final hurdle you will face is keeping it in view of newcomers as repeated pleas to sticky the most useful threads have so far fallen on deaf ears.

Good luck and thanks for your efforts.

PS. I have a Bsc Hons in Comp Science and 27 years so not exactly a noob myself B)

Cheers

[Guest Qwertymon]

there are plenty of guides on this forum, the realiy of it is, you just need to learn how to force the device manager to do what you want and not what it thinks you want.

There is a mild learning curve but there shoudlnt be an issue for people with mild it skills im reading here >_< I mean most of you massivly surpass my HND in cs >_<

Edited April 6, 2011 by Qwertymon