Novice requires help on resetting vega with r8 ROM

[Guest Zebrahead]

Here you go, I've made it a thread of it's own :

http://android.modaco.com/content/advent-v...k/#entry1674189

This should fix you ^^

Zeb

[Guest pompey007]

Here you go, I've made it a thread of it's own :

http://android.modaco.com/content/advent-v...k/#entry1674189

This should fix you ^^

Zeb

Ok, I think I have got the pc to recognise the vega. It searched for the USB drivers, found them , took a while to transfer files. finally, it states hardware installed ready to use.

Do I now run the BSOD fix?

[Guest Minimonkey]

I think you need to extract the zip file and run the .bat file. If that's not

Working install vega tools and just click on run bsod fix.

[Guest pompey007]

I think you need to extract the zip file and run the .bat file.

I have xtracted a file called tools and cannot see a bat file and I also have a BSODfix application?

When I run the BSODfix it does flash up the black DOS screen, but it just disappears

Was hoping to use this method to restore so trying to perservere with this!

[Guest Minimonkey]

I think zebrahead is fixing it now. Vegatools should do the same.

Edited April 19, 2011 by Minimonkey

[Guest Zebrahead]

I have xtracted a file called tools and cannot see a bat file and I also have a BSODfix application?

When I run the BSODfix it does flash up the black DOS screen, but it just disappears

Was hoping to use this method to restore so trying to perservere with this!

I THINK (untested due to no windows), it's just blinking as the device may not be connected using the whole 2 second cycle. Because the device isn't connected, it just closes.

It should work, I've just updated it, there may have been a slight problem, but it should work now.

Again, I'm sorry for the kinda unreliability, it's horrible not being able to test things!!

Thanks,

Zeb

[Guest Zebrahead]

I THINK (untested due to no windows), it's just blinking as the device may not be connected using the whole 2 second cycle. Because the device isn't connected, it just closes.

It should work, I've just updated it, there may have been a slight problem, but it should work now.

Again, I'm sorry for the kinda unreliability, it's horrible not being able to test things!!

Thanks,

Zeb

http://android.modaco.com/content/advent-v...a-double-click/

Download link there

Zeb

[Guest pompey007]

I THINK (untested due to no windows), it's just blinking as the device may not be connected using the whole 2 second cycle. Because the device isn't connected, it just closes.

Ok - I assumed that becasue it installed the drivers and added new hardware that it was connected? Presumably not now!! Quite frustrating knowing if it is connected or not?

Looks like I am back to square 1!

I will go through the 2 second cycle for the umpteenth time!

Rant over...thnks for your help!

[Guest Zebrahead]

Ok - I assumed that becasue it installed the drivers and added new hardware that it was connected? Presumably not now!! Quite frustrating knowing if it is connected or not?

Looks like I am back to square 1!

I will go through the 2 second cycle for the umpteenth time!

Rant over...thnks for your help!

I dont think any special drivers need be added, after all, this just abuses the stock installer really.

And I THINK you get the driver window both when it's plugged in normally, and for recovery.

Whether the popup message is different or not, I don't know.

My only other suggestion would be to reflash stock. However, this ofc requires the special recovery mode also. (And my tool just abuses it, they're effectively the same thing but my tool on restores the broken part and keeps your data)

Good luck ^^

Zeb

[Guest pompey007]

However, this ofc requires the special recovery mode also. (And my tool just abuses it, they're effectively the same thing but my tool on restores the broken part and keeps your data)

Good luck ^^

Zeb

I think that is my problem...getting into recovery mode and knowing it!

[Guest simonta]

I think that is my problem...getting into recovery mode and knowing it!

I'm assuming Windows 7, please always include your OS version when posting about anything to do with drivers.

http://android.modaco.com/content/advent-v...iver-installer/

Edited April 19, 2011 by simonta

[Guest pompey007]

I'm assuming Windows 7, please always include your OS version when posting about anything to do with drivers.

http://android.modaco.com/content/advent-v...iver-installer/

It is XP, think I will go back to the guide on installing drivers and ADB - to see if that works.

Just cannot see how I am going to get into recovery mode - have tried numerous times with different techniques as posted on this forum!

[Guest pompey007]

It is XP, think I will go back to the guide on installing drivers and ADB - to see if that works.

Just cannot see how I am going to get into recovery mode - have tried numerous times with different techniques as posted on this forum!

okay, going to persevere with this. I am thinking there must be a reason why I cannot get into recovery mode...it can't be a case of trying the 6 sec trick and hoping it will work, I must have tried every possible combination of power, USB, timings etc.

So going back to square 1 - do I need the drivers and ADB installed on PC before I try recovery mode on vega.

Is there anything else I can try?

[Guest Minimonkey]

okay, going to persevere with this. I am thinking there must be a reason why I cannot get into recovery mode...it can't be a case of trying the 6 sec trick and hoping it will work, I must have tried every possible combination of power, USB, timings etc.

So going back to square 1 - do I need the drivers and ADB installed on PC before I try recovery mode on vega.

Is there anything else I can try?

Have you tried it on a different computer?

[Guest Zebrahead]

okay, going to persevere with this. I am thinking there must be a reason why I cannot get into recovery mode...it can't be a case of trying the 6 sec trick and hoping it will work, I must have tried every possible combination of power, USB, timings etc.

So going back to square 1 - do I need the drivers and ADB installed on PC before I try recovery mode on vega.

Is there anything else I can try?

The only thing I'd suggest is make sure you follow the myadventvega instructions word for word - if it says you need drivers there, then you need drivers.

I'm sorry I can't be of more help when it comes to this, I use linux and have done for a while now so I'm out of touch with drivers etc on Windows.

The myadventvega instructions are kinda the absolute instructions for using the recovery tool (either provided by me, or them) so those instructions should cover everything required.

Good luck,

Zeb ^^

[Guest simonta]

The only way to know if you are in recovery is to look in device manager. If you see "APX" or "NVidia Harmony Recovery Driver" then you are in recovery. Repeat, this is the only way - your Vega will appear to be powered off in recovery.

To install the drivers, search for YAUDIG.

To get into recovery, just follow the instructions and keep trying. It takes patience and practice but once you've got the hang of it, it's easy. I can get a Vega into recovery almost first time, every time, sometimes within a couple of minutes but you WILL get there.

Cheers

[Guest warriorscot]

I have yet to fail getting into recovery but you have to follow every instruction most people skip something or make the schoolboy error of forgetting a two count and two seconds arent the same.

[Guest pompey007]

I have yet to fail getting into recovery but you have to follow every instruction most people skip something or make the schoolboy error of forgetting a two count and two seconds arent the same.

Still on this mission (did read a post earlier that was truly unbelievable in its tone, so hoping to get there by being nice and friendly!!), this is what I have done today:

1. Started again on a different pc (not the one that I installed the r8 rom)

to ensure that I was not getting confused with all the downloads and drivers etc

2. Followed instructions re full system restore

3. downloaded usb drivers to pc

4. downloaded bsodfix as provided by zebrahead - extracted into folder, there is a tools folder

and a ms-dos batch file

5. saved 4 & 5 onto pc under new advent vega folder - so they are easily retrieved

6. Held power button down on vega for 20-30 secs until screen went from dark-grey to black

7. connected vega to pc

8. vega plugged into power socket

9. Attempt to place advent vega into recovery mode

10. new hardware found - APX

11. installed drivers (from location saved in point 5) for nvidia usb boot recovery

12. Ran BSOD fix - fix my broken vega (from location saved in point 5)

13. DOS Command opens and it has message about nvflash etc and that "tools" (see point 4) is not an internal

or external command, operable

I think I am almost there...could really do with a nudge in the right direction...please!!

[Guest Zebrahead]

Still on this mission (did read a post earlier that was truly unbelievable in its tone, so hoping to get there by being nice and friendly!!), this is what I have done today:

1. Started again on a different pc (not the one that I installed the r8 rom)

to ensure that I was not getting confused with all the downloads and drivers etc

2. Followed instructions re full system restore

3. downloaded usb drivers to pc

4. downloaded bsodfix as provided by zebrahead - extracted into folder, there is a tools folder

and a ms-dos batch file

5. saved 4 & 5 onto pc under new advent vega folder - so they are easily retrieved

6. Held power button down on vega for 20-30 secs until screen went from dark-grey to black

7. connected vega to pc

8. vega plugged into power socket

9. Attempt to place advent vega into recovery mode

10. new hardware found - APX

11. installed drivers (from location saved in point 5) for nvidia usb boot recovery

12. Ran BSOD fix - fix my broken vega (from location saved in point 5)

13. DOS Command opens and it has message about nvflash etc and that "tools" (see point 4) is not an internal

or external command, operable

I think I am almost there...could really do with a nudge in the right direction...please!!

Ok, what you can do is

- Move the bat file into the tools folder

- Open it in notepad

- remove every occurence of "tools/" or "tools\" from the file

And try again.

Basically, it tries to find something in the tools folder, but clearly my syntax is wrong. In moving it to the tools folder, and removing all of the "tools\" or "tools/", you tell it to look in the folder it's in. This way, it should find the tools ^^.

Sorry, this is my not being able to test it and lack of windows experience showing through *embarrassed*

Zeb

[Guest pompey007]

Ok, what you can do is

- Move the bat file into the tools folder

- Open it in notepad

- remove every occurence of "tools/" or "tools\" from the file

And try again.

Basically, it tries to find something in the tools folder, but clearly my syntax is wrong. In moving it to the tools folder, and removing all of the "tools\" or "tools/", you tell it to look in the folder it's in. This way, it should find the tools ^^.

Sorry, this is my not being able to test it and lack of windows experience showing through *embarrassed*

Zeb

Firstly, no need to apologise - you have been very helpful!

Right, I did as instructed and removed the reference to /tools and run the BAT file from within the tools folder. The DOS screen opened and said Nvflash started, there were then a few entries and it finished with press enter. So I did this and on the vega in the top left hand side of the screen it said "entering nvflash recovery mode/NV3p server"

Not sure what to do now. Have turned vega off and back on (when connected to pc and not connected to pc) and just get a similar dark grey screen and no message? Obviously something has happened and I feel I am close but not quite there?

[Guest Zebrahead]

Firstly, no need to apologise - you have been very helpful!

Right, I did as instructed and removed the reference to /tools and run the BAT file from within the tools folder. The DOS screen opened and said Nvflash started, there were then a few entries and it finished with press enter. So I did this and on the vega in the top left hand side of the screen it said "entering nvflash recovery mode/NV3p server"

Not sure what to do now. Have turned vega off and back on (when connected to pc and not connected to pc) and just get a similar dark grey screen and no message? Obviously something has happened and I feel I am close but not quite there?

Ok, this is kinda good - Everything worked!

However, this is a tad puzzling as it seems my original diagnosis must have been wrong - this should have solved the problem.

I feel like I should explain what just happened, so that you're not just trying things blindly - you can skip this if you're not interested in it.

With r8, some problems came with the usb host/slave switching. Basically, the ROM was designed for slave mode, and upon switching to host mode things got a little confused internally and this leads to the stuck in boot BSOD. This has been the most common reason for BSODs as anyone who switched into host mode and rebooted, would get stuck.

The advent vega has an internal recovery mode, this is the "entering nvflash recovery mode/NV3p server" that you saw. This allows us to try and restore slave mode, without touching any of the rest of your data.

Once that had completed successfully, slave mode should be restored and you should have been able to boot as per usual.

Or at least this was the intention!!

But if the above wasn't the issue, do you remember what you may have been doing before this problem occurred?

Specifically, modifying anything in /system? Such as the boot animation? Or a new "theme"?

I promise I will fix this, if it's the last thing I do!

Zeb ^^

[Guest pompey007]

Hi, I understand what you are saying in the spoiler...I am increasing my knowledge pretty quickly. Pleased to hear and feel we are getting close.

The vega actually belongs to my 11 year old son, he is very confident with computers so I try and let him learn as he goes, therefore he increases his knowledge of what works and what doesn't. I don't want to hold him back and am happy with him exploring the capabilities...confident he couldn't brick it!!

I installed the ROM so that he could access the android market and he was trying out various apps. He was away with family when it crashed and therefore not sure what he was doing, but he was always mucking about with themes and wallpapers. He is not around at the moment to ask but I wouldn't be surprised if it was a theme issue. I would be surprised if he was messing about with boot animations - but you never know; I would suspect themes!!

[Guest Zebrahead]

Hi, I understand what you are saying in the spoiler...I am increasing my knowledge pretty quickly. Pleased to hear and feel we are getting close.

The vega actually belongs to my 11 year old son, he is very confident with computers so I try and let him learn as he goes, therefore he increases his knowledge of what works and what doesn't. I don't want to hold him back and am happy with him exploring the capabilities...confident he couldn't brick it!!

I installed the ROM so that he could access the android market and he was trying out various apps. He was away with family when it crashed and therefore not sure what he was doing, but he was always mucking about with themes and wallpapers. He is not around at the moment to ask but I wouldn't be surprised if it was a theme issue. I would be surprised if he was messing about with boot animations - but you never know; I would suspect themes!!

Hmmmm, ok. It's a bit more complex as if any of the system files were modified this could lead to a BSOD. The thing that makes it more awkward is that it's hard to provide a generic image of the system which you can just flash as everyone's /system could be different. (This is not so much the case with the boot image, which is what we just tried).

Have you ever backed up using clockworkmod? You'd have a file called clockworkmod with some dates (dates of the backups) in it in your SD card if you did.

If you have this we can try and restore an older system image that you have ^^.

Zeb

[Guest pompey007]

Have you ever backed up using clockworkmod? You'd have a file called clockworkmod with some dates (dates of the backups) in it in your SD card if you did.

If you have this we can try and restore an older system image that you have ^^.

Zeb

No, have not had it that long so no backups to date. THere wasn't anything of importance so is it worth reverting to factory settings and he can start again?

[Guest Minimonkey]

:)