I honestly believe that I have TWO bricked vega's

[Guest jimmo1990]

My son and his girlfriend have a vega each, however they seem to be both rather unwell after a hasty attempted flash by him, (I know we'd all have stopped at one ). However that's my situation.

I have all the tools and drivers and roms, when they initially got them both were flashed with r8 custom rom from modaco.

He has attempted to flash them both with the new vegacomb rom using the rom manager app, all seemed fine I'm told all prgress bars 100%, on re-boot though they failed into a blank screen.

I have attempted to re-flash (with nvflash) them but I get diferent errors each time from bootloader fails to recovery fails (yes i tried the stock rom from the vega home page, along with many other roms). Any help would be most gratefully accepted

[Guest Durbybard]

My son and his girlfriend have a vega each, however they seem to be both rather unwell after a hasty attempted flash by him, (I know we'd all have stopped at one ). However that's my situation.

I have all the tools and drivers and roms, when they initially got them both were flashed with r8 custom rom from modaco.

He has attempted to flash them both with the new vegacomb rom using the rom manager app, all seemed fine I'm told all prgress bars 100%, on re-boot though they failed into a blank screen.

I have attempted to re-flash (with nvflash) them but I get diferent errors each time from bootloader fails to recovery fails (yes i tried the stock rom from the vega home page, along with many other roms). Any help would be most gratefully accepted

Hiya, first of all his big mistake was trying to install Vegacomb 1.7 onto a stock rom, it's not possible, hence the modded stock rom update and being told to install Vegacomb 1.7 ontop of the modded stock rom, also another big mistake was to use rom manager app, i have not used this myself but a read alot say it isn't very good and using the standard revovery app and installing rom updates thru clockworkmod is the best process to be honest.

As for all went well to 100%, well, it's doesn't work like that on some roms, some roms look like they get to 100% and then keep going, i can only assume he thought that the process was finished and restarted the vega before it had actually finished.

As for a fix, ok, i guess you are not putting the vega into flash mode when installing the stock rom aka nvflash, so here's what you do, connect the PC to the vega with the vega switched off, turn you sound up on windows, hold the back button for 2 seconds, then holding the back button hold the power button for 2 seconds, you should here a ding sound on the PC, now let go of the power first then the back button, this means you are in flash mode, windows may now need to install a driver to be able to send the stock rom from the pc to the vega, find the drivers on this forum and install.

Now if you have downloaded the stock rom image to your PC, run it and if should install the stock rom and return the vega to it's original form when they got it, to know if this is working, you will see a small amount of text at the top of the vega saying nvflash........ etc then aload of text code will stream across the screen, the vega will then power down, power it up and lets hope they both work again.

As for bricked, i don't think it's possible, but maybe you could be the unlucky ones.

Also as a thought, if you have an android phone, take the memory cards out of the vega and format them with the android phone, maybe help, maybe won't. but just an idea.

Chris

[Guest simonta]

My son and his girlfriend have a vega each, however they seem to be both rather unwell after a hasty attempted flash by him, (I know we'd all have stopped at one ). However that's my situation.

I have all the tools and drivers and roms, when they initially got them both were flashed with r8 custom rom from modaco.

He has attempted to flash them both with the new vegacomb rom using the rom manager app, all seemed fine I'm told all prgress bars 100%, on re-boot though they failed into a blank screen.

I have attempted to re-flash (with nvflash) them but I get diferent errors each time from bootloader fails to recovery fails (yes i tried the stock rom from the vega home page, along with many other roms). Any help would be most gratefully accepted

You can always get into recovery. There is no such thing as a bricked Vega - in the entire history of Vegas, it's never been done.

Just remember that you will see nothing on the Vega screen, not even the backlight, in recovery. If you see the backlight come on, you've missed it so power off and try again. Search for YAUDIG and AUDI to sort it out.

Also, don't use ROM Manager. Flaky on the Vega and lots of tears because of it. Use clockworkmod instead.

[Guest jimmo1990]

Wow thanks for the fast response, I have read a failry large amount since recieving the 2 tablets, I know how to get them into recovery no-problem, as I said in my post I actually start to re-flash them and watch all the steps in the nvflash however they fail mostly at different image write points. These are not the usual problems that I have read about hence my post :(, any more ideas would be gratefully recieved.

[Guest ViPaSoft]

Are the Vega's Plugged into the mains when flashing. I had similar issues a while ago and someone suggested plugging it in and it worked first time after that.

Also, could be a dodgy downloaded ROM. Maybe re-download it and try again from Advent Vega.

[Guest Durbybard]

Wow thanks for the fast response, I have read a failry large amount since recieving the 2 tablets, I know how to get them into recovery no-problem, as I said in my post I actually start to re-flash them and watch all the steps in the nvflash however they fail mostly at different image write points. These are not the usual problems that I have read about hence my post :(, any more ideas would be gratefully recieved.

Hiya, well, as what has been said about Vegas being unbrickable, my guess is that you have a corrupt download of the stock rom, which i would re download and try again, or if no joy then try another PC, and if that doesn't work, somehow the system memory has been messed up, take them back and have them replaced, i assume they don't boot at all, if not say they worked fine last night, this morning they don't work at all.

But i'm going with corrupt stock rom and maybe PC problems talking to vega, hence try another PC if you can.

Chris...

P.S. You are using the rom from this link http://www.myadventvega.co.uk/ on the downloads tab, the full software update image v1.10 which is file softwareImage_1.10_Vega_Final.exe????

[Guest fatriff]

Are the Vega's Plugged into the mains when flashing. I had similar issues a while ago and someone suggested plugging it in and it worked first time after that.

Also, could be a dodgy downloaded ROM. Maybe re-download it and try again from Advent Vega.

I thought i'd bricked mine at one point but just flashing the original rom fixed it.

[Guest jimmo1990]

Yup plugged into the mains, I have tried both the factory rom, and the modaco rom slightly altered base rom. Here's a screenie of typical nvflash screen I end up with.

[Guest jimmo1990]

Bah missed the button :P

[Guest jimmo1990]

6 Pc's in the house running OS's from ubuntu to xp + 7, tried tham all, I even have back-ups that wont finish flashing. Guess I actually do have the first bricked Vega's ^^

[Guest G0OSE]

6 Pc's in the house running OS's from ubuntu to xp + 7, tried tham all, I even have back-ups that wont finish flashing. Guess I actually do have the first bricked Vega's ^^

There are so far as we know NO bricked vega's. Apparently they are unbrickable. Do you really believe you by some stroke of massive unluckiness have the only 2 bricked vegas in the world?

No. You are doing something wrong/not doing something you should, however I don't know what, sorry.

I have had a similar issue before when loading a rom, but nothing wiping it and starting fresh didn't sort out.

Edited August 14, 2011 by G0OSE

[Guest Durbybard]

6 Pc's in the house running OS's from ubuntu to xp + 7, tried tham all, I even have back-ups that wont finish flashing. Guess I actually do have the first bricked Vega's ^^

Hiya, are you using the same file that you downloaded or have you redownloaded the file again just to test, also remove the sdcard, maybe help, maybe not, you've nothing to lose.

I guess if above options have been done, then you have bricked 2 Vega's, taking them back to Currys and explaining why both don't work is going to be difficult.

I guess you son's repeated install of roms ontop of roms thinking it may work is a sure fire way to brick it, everybody here giving advice about reinstalling stock roms will be thinking that this is a rom update and that a reinstall of the stock rom will fix it, but never guess that this is to repair a vega with rom after rom etc install.

Sorry i couldn't help, Chris....

P.S. Don't suppose you live in or near Leeds do you, would love to get my hands on these two to try sort them out, hehehehe

[Guest jimmo1990]

Yep it's a tricky one, and Goose, I'm with you, I really feel I'm missing something, but after spending the whole night trawling forums I'm starting to doubt that. Taking 2 vegas back would be more than a bit awkward, guess they'll have to go back weeks apart.

I've been using pc's and different techie devices for 20yrs, never had a problem I couldn't fix myself after a good trawl so I'd feel dirty just taking them back to the shop and admitting defeat after 2 decades with a clean record :/.

And unluckily I live in riot free Manchester Chris ;-)

Edited August 14, 2011 by jimmo1990

[Guest G0OSE]

Yep it's a tricky one, and Goose, I'm with you, I really feel I'm missing something, but after spending the whole night trawling forums I'm starting to doubt that. Taking 2 vegas back would be more than a bit awkward, guess they'll have to go back weeks apart.

I've been using pc's and different techie devices for 20yrs, never had a problem I couldn't fix myself after a good trawl so I'd feel dirty just taking them back to the shop and admitting defeat after 2 decades with a clean record :/.

And unluckily I live in riot free Manchester Chris ;-)

The big thing for me is you have 2 that are like it, for me that says it's not the vegas to blame. The chances of having 2 bricked ones (as far as we know the ONLY 2) in one home are astronomical I'd imagine.

Bearing that in mind I'd start looking at some other explanation, but as always without actually watching you do it, is very hard to give advice - most people who have troubles genuinely think they are doing it right, but actually they are doing it wrong somewhere along the line. Finding out where is what will help you out, or I believe there were some kind people on here offereing 'remote' flashing if you were really stuck, perhaps a quick search for that?

Edited August 14, 2011 by G0OSE

[Guest Durbybard]

Yep it's a tricky one, and Goose, I'm with you, I really feel I'm missing something, but after spending the whole night trawling forums I'm starting to doubt that. Taking 2 vegas back would be more than a bit awkward, guess they'll have to go back weeks apart.

I've been using pc's and different techie devices for 20yrs, never had a problem I couldn't fix myself after a good trawl so I'd feel dirty just taking them back to the shop and admitting defeat after 2 decades with a clean record :/.

And unluckily I live in riot free Manchester Chris ;-)

I have only been beaten by one device, a dvd player i flashed with the wrong rom and bricked it, luckly i blagged them saying it worked fine the night before when i used it, but in the morning it wouldn't work, they checked it and gave me a new unit, LOL.

Love the comment about living in riot free Manchester, still laughing now.

Hope you get things sorted,

Chris

[Guest jimmo1990]

I have teamviewer 6 if any of you guys/gals fancy a challenge :)

(teamviewer6, is a hassle free remote access, small footprint and free for home use)

[Guest jimmo1990]

Latest update....nvflash starts fine but fails on the push of the recovery image (from the advent vega site). At least the thing is always failing on the same stage now, is it possible that the image on the vega site is corrupt? As I have DL'd it on 3 pc's and tried them all and it fails at that point on all

[Guest ViPaSoft]

Have you tried the new Modded Stock ROM from Newbie5. It re-formats the partitions giving slightly less user storage space, (in preparation for VegaComb). May be worth a try.

Find it here;

[Guest Durbybard]

Latest update....nvflash starts fine but fails on the push of the recovery image (from the advent vega site). At least the thing is always failing on the same stage now, is it possible that the image on the vega site is corrupt? As I have DL'd it on 3 pc's and tried them all and it fails at that point on all

Hiya, NOPE, as i have just downloaded the file from myadventvega and done a flash recovery just to see and it's all installed fine.

So i have no idea why it fails on the install of the recovery image, guessing something must be messed up with the memory slot given to the vega that the rom install on to.

Armed with this you could take 1 back and argue that you are doing what myadventvega explains you to do but it won't, either they will sort it there and then or replace it if they have stock, wait maybe a week and do the same with the other.

I am starting to think these new vegas that sprung up on PC-World and Currys websites for sale are substandard, a few post have come along on this form with faulty screens, creaking vegas when picked up, faulty internal wifi modules, all supposedly new vegas they just purchased from said retailers, maybe they have pushed the production of the vega to use up a mass of spare parts they had as they were losing sales cos alot of people were wishing to purchase, and they are totally crap compared to a vega built say 6 months ago, i am also thinking they maybe even refurbished vegas that are not tested properly and been boxed and sold as new, which would be illegal if my facts are correct about resale of opened boxed items.

Either way, to have 2 with the same fault is purely bad luck or a lack of understanding of the procedure to update custom roms onto the vega...

Chris

[Guest ursulavasey]

Hiya, NOPE, as i have just downloaded the file from myadventvega and done a flash recovery just to see and it's all installed fine.

So i have no idea why it fails on the install of the recovery image, guessing something must be messed up with the memory slot given to the vega that the rom install on to.

Armed with this you could take 1 back and argue that you are doing what myadventvega explains you to do but it won't, either they will sort it there and then or replace it if they have stock, wait maybe a week and do the same with the other.

I am starting to think these new vegas that sprung up on PC-World and Currys websites for sale are substandard, a few post have come along on this form with faulty screens, creaking vegas when picked up, faulty internal wifi modules, all supposedly new vegas they just purchased from said retailers, maybe they have pushed the production of the vega to use up a mass of spare parts they had as they were losing sales cos alot of people were wishing to purchase, and they are totally crap compared to a vega built say 6 months ago, i am also thinking they maybe even refurbished vegas that are not tested properly and been boxed and sold as new, which would be illegal if my facts are correct about resale of opened boxed items.

Either way, to have 2 with the same fault is purely bad luck or a lack of understanding of the procedure to update custom roms onto the vega...

Chris

My partner was running an nvflash on his newly repaired Vega earlier and it failed on the recovery image. On checking up, he found he hadn't ticked the usb debugging box in the settings. Once he did that, everything ran smoothly. It sounds obvious, but sometimes the obvious things get missed, particularly when troubleshooting a problem. Double check to see if usb debugging is enabled, then try the nvflash again.

[Guest Durbybard]

My partner was running an nvflash on his newly repaired Vega earlier and it failed on the recovery image. On checking up, he found he hadn't ticked the usb debugging box in the settings. Once he did that, everything ran smoothly. It sounds obvious, but sometimes the obvious things get missed, particularly when troubleshooting a problem. Double check to see if usb debugging is enabled, then try the nvflash again.

That's interesting as i thought that usb debugging and nvflash mode used different drivers as they do different things.

Also i have just put my vega into recovery mode and checked my drivers and there is nothing on the screen to do with the Android Phone in the device settings, all that's showing for the vega is the Nvidia USB Boot-recovery driver for mobile devices. So i am abit dubious about your above comment.

If that's not the case, then here lies the problem, i bet that jimmo1990 hasn't got the correct driver installed for usb debugging if he is doing the nvflash on a different system to the ones that where used to install the custom rom in the first place, and if this is not the case then the usb debugging driver that's installed is incorrect, why do i think that, well he has got these vegas which are unbootable, hence he can't get into the debugging option, hence the driver isn't installed or incorrectly installed.

But as i stated above, there is nothing showing in device manager relating to the usb debugging driver that's shown as Android Phone when in USB debugging mode.

Chris

[Guest jimmo1990]

My partner was running an nvflash on his newly repaired Vega earlier and it failed on the recovery image. On checking up, he found he hadn't ticked the usb debugging box in the settings. Once he did that, everything ran smoothly. It sounds obvious, but sometimes the obvious things get missed, particularly when troubleshooting a problem. Double check to see if usb debugging is enabled, then try the nvflash again.

I have tried the modded recovery in the thoughts that the filesystem may have been messed or that the new rom wouldn't fit into the space alloted, and that it would format and re-partition the internal storage for the rom.

I've quoted the above as I'd dearly love to get to the settings on the vega but as all I can do is get to the "recovery" part of the vega it's not in an OS bootable state, therefore anything that can be altered inside the OS on the vega isn't an option for me. As far as I can see the only option is for me to run the NVflash and push the image to the vega and that's where it all falls down.

Funny thing is I have returned 1 of the Vega's to the retailer now and bumped into another Vega owner who tablet was being flashed with the r8 mod (by the tech support in store) as she could't access the marketplace, does this mean that flashing the tablet doesn't in fact void the warranty? Because a normal user wouldn't be aware as to the possible consequences of this and she spoke to me outside telling me he didn't mention that it could cause a warranty problem.

Anyway got way off topic there.....1 vega at the shop but I hate being beat so anymore possibilities to try on the other are still gratefully tried and tested here, I'm not just giving silly auto-responces "yeh yeh blah blah" and not trying them. I'm sticking with it and trying any new options you guys and gals suggest.

I know 1 can be an accident but 2 is no coincidence and this points to me not getting something right, but be aware of this they were "bricked" in the same manner, by the same person, doing the same thing to both......

INSANE but true /sigh

EDIT: Just spotted your post as I was writing mine chris, I'm using vega tools and audi to ensure that the correct drivers are installed for the correct state of the tablet. The tablet is in recovery mode and the driver is the recovery mode driver, let me know if this is wrong.

Edited August 14, 2011 by jimmo1990

[Guest simonta]

My partner was running an nvflash on his newly repaired Vega earlier and it failed on the recovery image. On checking up, he found he hadn't ticked the usb debugging box in the settings. Once he did that, everything ran smoothly. It sounds obvious, but sometimes the obvious things get missed, particularly when troubleshooting a problem. Double check to see if usb debugging is enabled, then try the nvflash again.

Just a co-incidence I'm afraid. USB Debugging is an Android setting and Android isn't running when in recovery!

Jimmo.

The only common thing I can think of is the USB cable. Do you have a spare A-A? Installing the stock ROM does a complete partition and format so there are only 4 possibilities I can think of.

1. The source ROM On myadventvega is corrupt but we can discount this as many others are using it successfully.

2. The downloaded copy is corrupt but you've tried it on several different PCs so we can discount that.

3. The Vegas have a physical memory problem but 2 Vegas, in the same household, with the same problem? Can't be discounted but highly improbable.

4. Something is going wrong in the transfer. Given that 1 and 2 are discounted, and 3 is highly improbable, the only thing left is the cable. I've seen weirder things happen with dodgy cables.

Unfortunately, there is no way to reflash a Vega without going down the USB route.

I do have something you could try. A long shot but you've nothing to lose.

If you don't already have it, install 7ZIP and use it to unzip the stock ROM executable. Download a copy of clockworkmod for the Vega. Take the recovery.img file from clockworkmod and copy it over the reocvery.img in the unzipped stock ROM then run lvds.bat to install it.

Good luck

[Guest Durbybard]

I have tried the modded recovery in the thoughts that the filesystem may have been messed or that the new rom wouldn't fit into the space alloted, and that it would format and re-partition the internal storage for the rom.

I've quoted the above as I'd dearly love to get to the settings on the vega but as all I can do is get to the "recovery" part of the vega it's not in an OS bootable state, therefore anything that can be altered inside the OS on the vega isn't an option for me. As far as I can see the only option is for me to run the NVflash and push the image to the vega and that's where it all falls down.

Funny thing is I have returned 1 of the Vega's to the retailer now and bumped into another Vega owner who tablet was being flashed with the r8 mod (by the tech support in store) as she could't access the marketplace, does this mean that flashing the tablet doesn't in fact void the warranty? Because a normal user wouldn't be aware as to the possible consequences of this and she spoke to me outside telling me he didn't mention that it could cause a warranty problem.

Anyway got way off topic there.....1 vega at the shop but I hate being beat so anymore possibilities to try on the other are still gratefully tried and tested here, I'm not just giving silly auto-responces "yeh yeh blah blah" and not trying them. I'm sticking with it and trying any new options you guys and gals suggest.

I know 1 can be an accident but 2 is no coincidence and this points to me not getting something right, but be aware of this they were "bricked" in the same manner, by the same person, doing the same thing to both......

INSANE but true /sigh

EDIT: Just spotted your post as I was writing mine chris, I'm using vega tools and audi to ensure that the correct drivers are installed for the correct state of the tablet. The tablet is in recovery mode and the driver is the recovery mode driver, let me know if this is wrong.

Hiya bud, i'm not sure if this is winding me up more than you, my head hurts running scenarios in my head.

So to clarify, you have taken one back and that's in for repair? (also you say a female vega owner is having modaco R8 installed by the teckies at Currys so she has access to the market, wonder what that is costing you, no less than £50 i would guess, if for free i'm taking mine down just for the sake of it lol, give them something to do LOL)

Anyway, as of now, i cannot see anyway of getting the bricked vega up and running (make sure you have the correct driver installed for nvflash mode as stated in my previous post, thats the correct title, nothing else and that flashed my vega with the stock rom with no problems), so i'd wait until you get the other vega repaired and then boot it up and put it into usb debugging via settings/applications/development and the top option and see if the driver in device manager pops up with Android Phone at the top, if you click the triangle it should say Android Composite ADB Interface, if it does then you have the correct driver installed, if you don't see that, then you know that it's not installed properly and use vega tools to do this for you.

But as i stated before, when you put the vega into nvflash, it's doesn't show any reference to using the debugging driver in device manage, hence me being dubious about what was stated.

I am no expert with android, so i could be wrong here.

Anyway, Sorry i couldn't help further, maybe someone who's got more insight into the vega/drivers/debug mode etc come on and reads, could be something simple, as for me i have exhausted all the options i can think of.

Chris

[Guest jimmo1990]

Just a co-incidence I'm afraid. USB Debugging is an Android setting and Android isn't running when in recovery! Jimmo. The only common thing I can think of is the USB cable. Do you have a spare A-A? Installing the stock ROM does a complete partition and format so there are only 4 possibilities I can think of. 1. The source ROM On myadventvega is corrupt but we can discount this as many others are using it successfully. 2. The downloaded copy is corrupt but you've tried it on several different PCs so we can discount that. 3. The Vegas have a physical memory problem but 2 Vegas, in the same household, with the same problem? Can't be discounted but highly improbable. 4. Something is going wrong in the transfer. Given that 1 and 2 are discounted, and 3 is highly improbable, the only thing left is the cable. I've seen weirder things happen with dodgy cables. Unfortunately, there is no way to reflash a Vega without going down the USB route. I do have something you could try. A long shot but you've nothing to lose. If you don't already have it, install 7ZIP and use it to unzip the stock ROM executable. Download a copy of clockworkmod for the Vega. Take the recovery.img file from clockworkmod and copy it over the reocvery.img in the unzipped stock ROM then run lvds.bat to install it. Good luck

2 vega's 1 house I agree whole heartedly but the bad thing in the equation is 1 idiot common to both problems :).As I mentioned I've been to the retailer to drop 1 vega off and was hoping to purchase anther A to A cable but they don't sell them and he's lost the other so. I do actually have only 1 other thing common to the failed attempts to flash and that the USB cable used to attempt each flash on each machine, however as I dont actually have another cable on hand I'm going to give you other suggestion a try I'll let you know shorlty. Cheers

EDIT: that's the read from the suggestion, damn nice thought though Simonta.

Edited August 14, 2011 by jimmo1990