Help – Vega dead after R6 update

[Guest hankhill23]

I put Pauls R5 Rom on my Vega on Boxing Day, no probs (bought the performance pack). Today I notice an R6 with built in USB Host capability, which I’d been planning to do anyway. I installed that this evening and spent an hour playing with various USB sticks. Since reboots seem to be needed most times I installed a reboot app from Market, (can’t remember what it’s called, might have been anboot) this offered a straight reboot or a reboot to recovery. Also, I noticed a Recovery Icon, but I don’t know if that’s part of Pauls R6 or part of the reboot app. Anyway, I accidentally hit that icon whilst scrolling the screen, and without any prompt or confirmation it’s gone straight into some kind of recovery mode and is basically dead.

I have tried the “hold back button 2 secs/power 2 secs/back 2 secs” but nothing. When plugging it into the PC via USB it’s not detected, presumably because it’s still in Host mode. I can get the backlight on or off by holding down the power button but otherwise nothing.

Help! I’d hate to have to admit to the wife that I’ve broken my pressie already!

[Guest swarrans]

You won't have killed it - read some of the other "bricked" threads and with patience I'm sure you'll get it back. Best to keep the status secret from wifey until then!

[Guest gadget_tech]

DELETED.

Edited October 21, 2017 by gadget_tech
DELETED.

[Guest alfe]

I put Pauls R5 Rom on my Vega on Boxing Day, no probs (bought the performance pack). Today I notice an R6 with built in USB Host capability, which I’d been planning to do anyway. I installed that this evening and spent an hour playing with various USB sticks. Since reboots seem to be needed most times I installed a reboot app from Market, (can’t remember what it’s called, might have been anboot) this offered a straight reboot or a reboot to recovery. Also, I noticed a Recovery Icon, but I don’t know if that’s part of Pauls R6 or part of the reboot app. Anyway, I accidentally hit that icon whilst scrolling the screen, and without any prompt or confirmation it’s gone straight into some kind of recovery mode and is basically dead.

I have tried the “hold back button 2 secs/power 2 secs/back 2 secs” but nothing. When plugging it into the PC via USB it’s not detected, presumably because it’s still in Host mode. I can get the backlight on or off by holding down the power button but otherwise nothing.

Help! I’d hate to have to admit to the wife that I’ve broken my pressie already!

Mate don't worry same thing happened to me. Took an hour but basically kept trying to get into recovery, once I did I reinstalled official update then r6. Just working on getting everything back on. Good luck

[Guest hankhill23]

Phew, sigh of relief. I left it charging for 90mins (watched a film to take my mind off it). I think maybe the battery was too low to get into the restore mode before; it was around 20% when this happened. Maybe that’s why other people in this forum have said things like “keep trying; I got it working after an hour”. Maybe they got it working when the battery reached a safe level. When I flash my Windows Phone the software won’t let the flash proceed unless there’s at least 50% battery charge. But at least it tells you…

Anyway, to help anyone else in the same boat here’s what I did.

I read this - http://www.myadventvega.co.uk/full_system_...nstructions.pdf and downloaded the USB drives and restore image files linked in the document.

Many of the threads here (yes I did search) have basically the same info, but even this official one is not totally clearly written. When I did the back/power buttons I got a USB connect/disconnect sound from my PC (Windows7) which I’d never got before, and device manager showed a failed installation of a device “APX”. Nothing on the Vega yet though. In device manager I selected to Update Driver Software and I browsed to the folder where I’d unzipped the USB drivers and it installed, albeit with no confirmation, the Vega was still dead, no backlight nothing.

I then double clicked the restore image file “softwareImage_v1.06_05_Vega_Final” and to my relief it began to install, and I ended up with my Vega just like when I first powered it up on Christmas Day.

What really hacks me off is how easy it was to get to this sorry state. I had pressed an icon called “recovery” by mistake when scrolling, and with no “are you sure” or any other prompt it just sent my Vega into a coma. Is that recovery icon part of Paul’s R6 ROM? If it is, shouldn’t there be some kind of safeguard? It’s all too easy to accidentally select an icon while scrolling, and this one seems to be basically a self destruct button! Edit – I’ve just restored Paul’s R6 Rom and the recovery icon is there so it’s part of that. I’m now terrified of accidentally hitting it again! I’ve noticed there’s an option to cook a ROM without it, so I will. I’m sure it’s probably a useful feature that I should learn about, but as far as I’m concerned it’s a self destruct button and I don’t want it.

Having really got my Vega how I liked it, email setup, bookmarks, etc. I’ve now got to start all over again. Grrrrr…..

As an experiment, since I now know how to restore to factory settings, I pressed the restore icon again. Without any confirmation whatsoever it went into restore but this time instead of putting my Vega into a dead coma it showed a restore icon (box with an arrow and an Android figure) so at least I knew something was happening. However, nothing else happened, this icon just stayed on the screen for several minutes and I ended up rebooting the Vega. Luckily this time it booted cleanly.

Am I missing something here, or is this recovery feature broken in R6? I’ve now baked a new ROM without it.

[Guest hankhill23]

Another edit – I had created another version of Paul’s R6 ROM without the Recovery “Self Destruct Icon” feature, but when I installed it, the Recovery icon was still there. The only way I could get rid of it was to do a full system restore again, and then install the R6 "without recovery" ROM. It looks like these ROMs are not ROMs in the true sense, but just copy files on top of the OS that is already there.

Correct me if I’m wrong, but the only way you can actually remove anything is to go back to a fresh factory restore and then install the new ROM (having removed the features you don’t want) on top of that. I don’t wish to appear to be running down the excellent work done by Paul and Modaco, the main reason I went for the Vega is the excellent community here at Modaco, and I have happily paid my tenner with no regrets, but this is a wasted evening I could have done without :(

[Guest remlap]

I just hide the apps I don't want but need or don't use often with Launcher Pro.

Edited December 30, 2010 by remlap

[Guest alfe]

I uninstalled that 'self destruct Burton's button as soon as I got r6 reinstalled! Glad I was not the only one in that pickle! You can uninstall through app settings manually. Glad your sorted.

[Guest Dayzee]

Another edit – I had created another version of Paul’s R6 ROM without the Recovery “Self Destruct Icon” feature, but when I installed it, the Recovery icon was still there. The only way I could get rid of it was to do a full system restore again, and then install the R6 "without recovery" ROM. It looks like these ROMs are not ROMs in the true sense, but just copy files on top of the OS that is already there.

Correct me if I’m wrong, but the only way you can actually remove anything is to go back to a fresh factory restore and then install the new ROM (having removed the features you don’t want) on top of that. I don’t wish to appear to be running down the excellent work done by Paul and Modaco, the main reason I went for the Vega is the excellent community here at Modaco, and I have happily paid my tenner with no regrets, but this is a wasted evening I could have done without :(

I TOTALLY agree and said as much on the Clockworkmod recovery thread here -http://android.modaco.com/index.php?s=&showtopic=324601&view=findpost&p=1534759

What is MORE worrying is that Paul is aiming to have his next update ONLY WORK VIA THIS RECOVERY ;)

I'm hoping enough folk will complain for him to change his mind and leave the recovery alone on the Vega as rebooting is so unreliable and that recovery app is bloomin deadly!! Me Personally, I'm not changing my stock recovery for Clockwork - wayyyy to easy to brick and like you say, have to reflash stock, then MCR then restore everything if you've been canny enough to use Titanium Backup!! So I'll either have to find a way to do it via adb or stay on r6 ;)

Dayz xx

[Guest simonta]

Guys. Settle down.

This is not a self destruct button, and you have voluntarily chosen to hack your Vega using stuff which, whilst well tested, does carry an element of risk. I believe it to be impossible, using Pauls patch (which is not a ROM, it simply copies new files onto an existing build) to brick your Vega and far from being "wayyy to easy to brick", it's exactly the opposite. In fact, it's one of the most difficult to brick devices in existence. Sadly, pushing my hacking beyond the mcr patches, I seem to have found one method to truly brick a Vega and it is not something you can do with the information on these pages.

Please also do some more reading. Your inability to load device drivers driven by your choice to hack and lack of knowledge of Windows is not the fault of anyone on here. I can assure you that with the correct knowledge and experience, it is always possible to get the correct drivers loaded and to get into the recovery mode needed to flash back to the stock build.

Finally, you talk of complaining to Paul - the guy who has worked hard to liberate our Vegas and let them use their potential when you voluntarily chose to use his work? Bizarre, especially given the statements that he is working with the author of clockworkmod to make sure that the incompatiblity with the Vega is sorted. I've been using clockworkmod for a long time on my HTC Desire and believe me, getting it working reliably will be a great thing, as will the ability to use it to flash Pauls updates. I absolutely support that effort.

If complaining is your goal, then I respectfully suggest that you flash the stock ROM and forget about the efforts underway here.

Cheers

Edited December 30, 2010 by simonta

[Guest swarrans]

I have to say I'm with you Simonta to a large extent - I think Paul and a lot of the posters on here have the patience of saints with some people (not the above posters I have to say) who really shouldn't be trying to update roms when they don't understand windows basics AND can't even be bothered to read the posts which answer their questions.

Having said that we're all capable of posting something that is open to different interpretations (i made the mistake of posting something that made others think I was complaining about Paul not releasing new roms fast enough when it wasn't what I truely meant!)

This really is a fantastic support group - I don't normally pay for stuff like this but was happy to in this case

[Guest alfe]

Guys I was not complaining I think the work Paul has done for our Vegas is priceless. Was just sharing my first bad experience!

I don't mind what way our next update comes as I know it will be awesome!

[Guest .stu]

... this is a wasted evening I could have done without :(

Or you could look at it as an evening spent learning some very important information.

[Guest terminaljunkie]

Guys. Settle down.

This is not a self destruct button, and you have voluntarily chosen to hack your Vega using stuff which, whilst well tested, does carry an element of risk. I believe it to be impossible, using Pauls patch (which is not a ROM, it simply copies new files onto an existing build) to brick your Vega and far from being "wayyy to easy to brick", it's exactly the opposite. In fact, it's one of the most difficult to brick devices in existence. Sadly, pushing my hacking beyond the mcr patches, I seem to have found one method to truly brick a Vega and it is not something you can do with the information on these pages.

Please also do some more reading. Your inability to load device drivers driven by your choice to hack and lack of knowledge of Windows is not the fault of anyone on here. I can assure you that with the correct knowledge and experience, it is always possible to get the correct drivers loaded and to get into the recovery mode needed to flash back to the stock build.

Finally, you talk of complaining to Paul - the guy who has worked hard to liberate our Vegas and let them use their potential when you voluntarily chose to use his work? Bizarre, especially given the statements that he is working with the author of clockworkmod to make sure that the incompatiblity with the Vega is sorted. I've been using clockworkmod for a long time on my HTC Desire and believe me, getting it working reliably will be a great thing, as will the ability to use it to flash Pauls updates. I absolutely support that effort.

If complaining is your goal, then I respectfully suggest that you flash the stock ROM and forget about the efforts underway here.

Cheers

APPLAUDS...or get an iPad :(

Edited December 30, 2010 by terminaljunkie

[Guest Dayzee]

I'm just letting people know how easy it is to mess this up - especially all the folk who gota Vega for chrimbo and have never done any flashing before.

this tablet is brilliant, but only with pauls great rom. That much is being rightly shouted from the hilltops. Because of that, people are more wiling to take the risk, especially new people.

I'm certainly not new to this having had G1, hero, google ion, milestone, nexus one, San Francisco and vega - andf yet this process went wrong very easily for me, and if I was a newb, id have had to return and been very put off.

The probs are these -

1 - Usb drivers to use adb, and to use recovery and stock flashing are not straightforward, and are easier on some platforms than others.

2 - getting the Vega into its stock flashing mode, to flash official updates or recover from problems, is tricky to say the least.

3 - the clockworkmod recovery bootloader has presented prices for some - seems to either not work from the start, stopping the Vega from booting or it fails after a couple of go's and so far, I don't think there has been a clear reason why it works fine for some and not others.

The first two mean that problems with point 3 are not easily recovered from.

added to this is the fact that the Rom will soon only be updatable using the clockwork recovery.

its not about complaints, its about reporting experiences, so that anyone having similar problems can solve them, or decide not to take the risk.

Dayz

Edited December 30, 2010 by Dayzee

[Guest terminaljunkie]

Hey Dayz, not having a pop at anyone mate - just being flippant...all of this is very new to many people and we will all fall over until it is refined. All input is more than useful and welcome, but we have to be patient whilst development proceeds - and also realise that we do this with some risk attached as you have indicated you accept!

Think we have a decent product here, and with all this dev stuff and the feedback it will only get better :(

[Guest Dayzee]

Hey Dayz, not having a pop at anyone mate - just being flippant...all of this is very new to many people and we will all fall over until it is refined. All input is more than useful and welcome, but we have to be patient whilst development proceeds - and also realise that we do this with some risk attached as you have indicated you accept!

Think we have a decent product here, and with all this dev stuff and the feedback it will only get better :(

;) didn't think anyone was having a go, I just really want new folk to know that this has some pitfalls to avoid and stuff is still being ironed out. I know this will be sorted in the future, android devs are gods in my eyes ;) just making sure us mortal folk keep from deading our tech... ;)

love you all, but as they say in Hill Street Blues, be careful out there.... xx

[Guest Mogedwards]

If I can add a comment about the recovery button.

I did exactly the same, accidentally. I was looking through the apps in R6 and accidentally touched the screen. (I often do this when I sit with a finger hovering over the screen, but normally it is no more than a nuisance)

My Vega immediately shut down and now I am trying all the suggestions to get it working again. So far unsuccessfully, but it is now 1a.m. and I should go to bed.

I had no idea the recovery app would do that and it gave no second chance. It just immediately shut the system down. So I have added this just to re-enforce the warning not to touch it.

[Guest simonta]

If I can add a comment about the recovery button.

I did exactly the same, accidentally. I was looking through the apps in R6 and accidentally touched the screen. (I often do this when I sit with a finger hovering over the screen, but normally it is no more than a nuisance)

My Vega immediately shut down and now I am trying all the suggestions to get it working again. So far unsuccessfully, but it is now 1a.m. and I should go to bed.

I had no idea the recovery app would do that and it gave no second chance. It just immediately shut the system down. So I have added this just to re-enforce the warning not to touch it.

Hi Mogedwards.

I know what happens when you press the recovery icon. In essence, it reboots into clockworkmod recovery which, if you don't have, leaves the machine hanging.

But what happens when you try to reboot? I'd like to take a deeper look at this problem and try to understand why people can't simply power off and restart. I don't have clockworkmod and when I click the icon, the machines reboots and doesn't come back. Then I pull out the charger, hold the power button for about 8 seconds to ensure that it's powered off then restart.

What happens when you do this? Does the backlight come on? Do you see "Booting...."?

Cheers

[Guest Mogedwards]

Hi Simonta.

I am trying now. So far all I am getting is the backlight. I have downloaded the USB file and the image file from the Advent Vega support site, but when I plug the Vega into my PC it is not recognised, even when I use 'Install New Hardware' or look in 'My Computer'.

I have rebotted my PC a couple of times and gone through the Vega 'Key Press' cycle a few times, but I am getting nowhere.