I honestly believe that I have TWO bricked vega's

[Guest simonta]

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

OP has got a failure late in the process so is therefore correctly in recovery and with the correct drivers loaded or the process would not have even started. ADB and USB Debugging are Android functions and have no relevance when flashing.

[Guest Minimonkey]

I think newbe5 once thought he had bricked his vega and tried allsorts to get Nvflash working, even taking the back four screws out and unplugging the battery then plugging back in (bit extreme but maybe worth a go?) also tweeting this: So, neat trick if anyone is ever REALLY stuck to get in to nVflash on the Vega. Unplug the USB, do the keycombo, then plug it back in!

Hope you manage to sort :-)

[Guest jimmo1990]

Next stop battery out, I take it the screws are under the 4 rubber stoppers in each corner?

[Guest Minimonkey]

Next stop battery out, I take it the screws are under the 4 rubber stoppers in each corner?

Yep

[Guest jimmo1990]

Well I disconnected the battery and tried to power it up just to make sure it was fully drained on the board, then tried to flash it and no joy. I do think at this point we might just have the 1st truly bricked vega, kudos to my son for being a muppet as I know he's gonna read this in about an hour :P

I'll keep struggling on and see if anything comes to mind, but I guess the thing with NVram is that in non-volatile so it was a long shot anyway

[Guest jimmo1990]

As from the knowledge I've gleaned this is a ported version of linux, and the fact that I can see another simple basic drive(100GB) in windows drive manager that can't be read by windows I'm wondering if maybe I can go into linux and use Gparted to repair, any thoughts?

[Guest xathras]

Well I disconnected the battery and tried to power it up just to make sure it was fully drained on the board, then tried to flash it and no joy. I do think at this point we might just have the 1st truly bricked vega, kudos to my son for being a muppet as I know he's gonna read this in about an hour :P

I'll keep struggling on and see if anything comes to mind, but I guess the thing with NVram is that in non-volatile so it was a long shot anyway

Can you give us some more info to help us? Does Vega A always fail at the same place during the flash? Ditto for Vega B. Screenshots are a great help. It is also possible that if pushing an image fails that it could be because the partitions have been damaged. I'd strongly recommend trying to flash the ModdedStock_1.10_v2. This repartitions the Vega in preparation for installing VegaComb, which has different partition sizes. I see that you say that you have all the tools, but you may not have the latest versions. Vega Tools v4 will (attempt to ) download and install ModdedStock_1.10_v2 for you. Remember to be careful when handling the Vega when in recovery mode. You must not touch the screen.

http://android.modac...edstock-110-v2/

http://android.modac...vega-tools-v40/

[Guest Minimonkey]

Also is the vega the only thing plugged into the computer? No other USB etc conflicting...

[Guest jimmo1990]

Hi there,

Cheers for the reply, yes I'm using vega tools 4.0 and I've tried flashing with the rom (110v2) you kindly linked for me.

I only have 1 tablet left now and it seems to be failing at the same place each time (shown in the screenie), the reason I wanted to take a look in Gparted was so that I could hopefully see what size the disk partitions are and find out if in fact the modded rom is getting the partitions set up correctly. On the grounds that a pint won't fit in a half pint pot :-)

I'm 99.9% certain that there's no driver/communication issues, it's almost as if there's a bad sector or a size difference or even a file that won't let me overwrite it (only my random musings).

I will try to re-flash and see if it stops at the same point as last time before I go off into the gparted live stick for a look and report back :P

[Guest jimmo1990]

Attempt 1 got much further than normal, as you can see from the screenie all partitions are being created and formatted without incident, it's also sent the bootloader, the recovery and the image without issue, however it has failed at "sending file system.img"

"command failure: create failed (bad data)"

I'll try again and see how far it gets, stay tuned for more hair pulling :-)

[Guest jimmo1990]

Attempt 2 stopped earlier than1 under exactly the same conditions

command failure: create failed (bad data)

But this time with less of the file sent

[Guest simonta]

Attempt 1 got much further than normal, as you can see from the screenie all partitions are being created and formatted without incident, it's also sent the bootloader, the recovery and the image without issue, however it has failed at "sending file system.img"

"command failure: create failed (bad data)"

I'll try again and see how far it gets, stay tuned for more hair pulling :-)

Same kind of problem, different place and different partition so hardware problem with the Vega has receded into the far distance. USB Cable is 3 lengths ahead with a furlong to go.

This will sound bizarre. Any way you can lay the Vega so that the cable is straight and routed as far as possible from anything that could generate interference? You might have dodgy shielding and picking up stray signals. An acid test would be to flash again immediately after a failure and see if the point of failure is different.

[Guest xathras]

Attempt 1 got much further than normal, as you can see from the screenie all partitions are being created and formatted without incident, it's also sent the bootloader, the recovery and the image without issue, however it has failed at "sending file system.img"

"command failure: create failed (bad data)"

I'll try again and see how far it gets, stay tuned for more hair pulling :-)

If you Google for NvError 0x120002 you will get lots of results. Although most of these are for other devices some of the comments may be helpful. In two cases using a different USB cable cured the problem. I havn't been through all of them, so you might want to take a look.

[Guest simonta]

Same kind of problem, different place and different partition so hardware problem with the Vega has receded into the far distance. USB Cable is 3 lengths ahead with a furlong to go.

This will sound bizarre. Any way you can lay the Vega so that the cable is straight and routed as far as possible from anything that could generate interference? You might have dodgy shielding and picking up stray signals. An acid test would be to flash again immediately after a failure and see if the point of failure is different.

EDIT. BTW, your son is of the hook. The fact it's running NVFLash at all proves it's not bricked.

[Guest Minimonkey]

If you Google for NvError 0x120002 you will get lots of results. Although most of these are for other devices some of the comments may be helpful. In two cases using a different USB cable cured the problem. I havn't been through all of them, so you might want to take a look.

Surely your on to something here... Gotta be the cable :-)

[Guest jimmo1990]

I don't doubt the fact that it could be the cable and the thought of breaks and sheilding has occured to me so I've layed the cable and the tablet on the floor to avoid interference and hopefully reduce the kinks or breaks that might well exist, the only way I can prove it is with another cable.

As I mentioned before I couldn't buy an A to A USB cable from the shop earlier and as it's Sunday I'll have to wait till tommorow. The fact that it was the least likely culprit kept me trying throughout the day, but as each of the possible causes are rejected it seems the only sensible option is to give up till I can grab 1 from a decent shop in the morning.

Thanks for all the help and suggestions folks, as usual if anything else pops into your heads let me know, loving the forum seems like a nice little community of vega addicts

Kind regards to one and all

I'll keep you posted

[Guest richardmlea]

Jimbo, where are you in Manchester? You are welcome to come and borrow my usb cable to eliminate/comfirm the cable as the culprit.

I am in openshaw (in the ghetto) just outside the city centre. PM me if you want to borrow it and I'll send you my phone number.

[Guest Pdragon]

I don't doubt the fact that it could be the cable and the thought of breaks and sheilding has occured to me so I've layed the cable and the tablet on the floor to avoid interference and hopefully reduce the kinks or breaks that might well exist, the only way I can prove it is with another cable.

As I mentioned before I couldn't buy an A to A USB cable from the shop earlier and as it's Sunday I'll have to wait till tommorow. The fact that it was the least likely culprit kept me trying throughout the day, but as each of the possible causes are rejected it seems the only sensible option is to give up till I can grab 1 from a decent shop in the morning.

Thanks for all the help and suggestions folks, as usual if anything else pops into your heads let me know, loving the forum seems like a nice little community of vega addicts

Kind regards to one and all

I'll keep you posted

I think you have an audience now rooting for you to get this sorted.

To me it also sounds like a USB cable issue. I have a USB External hard drive that randomly used to loose connection even though the cable wasn't moved. It drove me crazy as I thought it was my computer, the drivers or a faulty hard drive. I chanced another cable and presto-chango everything worked fine.

Fingers crossed for you!

[Guest fatriff]

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 ;-)

Here's what I used, Audi Tool, it shows you when your device is connected properly plus you can also install the drivers with it Audi Tool

Then I installed the modded stock

ModdedStock

And my device was back functioning again.

I can't see what retailer is going to accept a vega back when you will have to admit that you tried to flash it.. Voiding the warranty?

I've heard of people with laptops who are not very computer lit who have accidentally or purposefully formatted the drive taking it back to the shop and saying it's broken! It really does happen, because to them, it not loading the OS means it's broken. Then the person at the store informs them that they wiped it and they just need to re-install it.. And the person says something like.. Oh, I shouldn't have to do that, I'll just take my money back all the same.

Sorry, but that's not a valid reason to return it.

Edited August 15, 2011 by fatriff

[Guest premieral]

Here's what I used, Audi Tool, it shows you when your device is connected properly plus you can also install the drivers with it Audi Tool

Then I installed the modded stock

ModdedStock

And my device was back functioning again.

I can't see what retailer is going to accept a vega back when you will have to admit that you tried to flash it.. Voiding the warranty?

I've heard of people with laptops who are not very computer lit who have accidentally or purposefully formatted the drive taking it back to the shop and saying it's broken! It really does happen, because to them, it not loading the OS means it's broken. Then the person at the store informs them that they wiped it and they just need to re-install it.. And the person says something like.. Oh, I shouldn't have to do that, I'll just take my money back all the same.

Sorry, but that's not a valid reason to return it.

Flashing doesn't void the warranty

[Guest jimmo1990]

Well here's the story, it seems that both USB leads were lost and unknown to me I was using a £3.00 USB lead V1.1. So today I popped to the shop grabbed a replacement (with power spur) V2.0 USB lead a hey presto we have a working tablet on the modded stock ROM.

So thanks for all the advice and kind offers of help, I didn't really know anything about these tablets till Friday and now I think I'd like to own 1 myself :P

Thanks again folks

The moral of the story: Find out the real story, never use cheap cables, and kids keep your bedrooms tidy or you can make your dad bald with stress.

Gonna give vegacomb a try now :-)

[Guest phil8715]

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

Have you got it sorted out yet?

If not myself and my partner live not too far from Manchester and could pop over and take a look if you want us too?

If you're interested PM me and we'll make some arrangements.

Phil

[Guest jimmo1990]

Yep all fixed full cause and effect written above your post but thanks for the offer

[Guest simonta]

Yep all fixed full cause and effect written above your post but thanks for the offer

Glad it's sorted. This was one of those mini sagas and as someone else said, lots of people rooting for you. Cheers

[Guest gh69]

Was reading this saga last night in bed, on my Vega, and I have to say I am amazed a cable could cause such an issue, but glad it's all sorted now. :D

Perhaps you should confiscate your sons Vega as payment ;)