Guest katopp Posted March 22, 2011 Report Posted March 22, 2011 (edited) Well, I just moved from the iPad to Android and thought the Advent Vega 10 would be a nice toy. Then I learned, that the Android Market did not work and that I had to install a modified ROM. And I did install the r8 custom ROM from this site here. Which worked nicely, al;l files copied, tablet rebooted and .... ..... it only says "Booting ..." Nothing else. Did I brick it? Can I revive it? Edited March 22, 2011 by katopp
Guest simonta Posted March 22, 2011 Report Posted March 22, 2011 (edited) Reboot it. Hold power for > 6 seconds, release, press power until the back light comes on, release. PS. You will learn that the Vega is unbrickable :D Edited March 22, 2011 by simonta
Guest Lennyuk Posted March 22, 2011 Report Posted March 22, 2011 Looks like Simonta beat me too it, yeah the vega is unbrickable, at least there is no known way to brick it yet... so don't worry just take a deep breath and follow instructions. If its not working then leave it for a few hours and then go back and try again.
Guest katopp Posted March 22, 2011 Report Posted March 22, 2011 Looks like Simonta beat me too it, yeah the vega is unbrickable, at least there is no known way to brick it yet... so don't worry just take a deep breath and follow instructions. If its not working then leave it for a few hours and then go back and try again. Any idea, how long it'll take if you just "leve for a few hours"? The reset did nothing but, well, a reset and it still shows up only the "Booting ..." message, but it doesn't boot.
Guest rvdgeer Posted March 22, 2011 Report Posted March 22, 2011 (edited) Any idea, how long it'll take if you just "leve for a few hours"? The reset did nothing but, well, a reset and it still shows up only the "Booting ..." message, but it doesn't boot. I think you should leave it just long enough to give you the opportunity to read all the "Help, I've bricked my Vega [solved]" and "Step by Step Guide to whatever" topics and topics containing any of the words "instructions", "flashing", "boot loop" and/or "firmware". If you feel the need to take a break in between, you can always play around with the search function... I strongly believe you can really benefit from this! It's not my intention to rant, so please don't feel offended! There are lots of valuable information on this forum, so please feel free to read ans use it... And don't worry about your tablet: it's not bricked unless it's literally broken! Edited March 22, 2011 by rvdgeer
Guest katopp Posted March 22, 2011 Report Posted March 22, 2011 (edited) I think you should leave it just long enough to give you the opportunity to read all the "Help, I've bricked my Vega [solved]" and "Step by Step Guide to whatever" topics and topics containing any of the words "instructions", "flashing", "boot loop" and/or "firmware". If you feel the need to take a break in between, you can always play around with the search function... I strongly believe you can really benefit from this! It's not my intention to rant, so please don't feel offended! There are lots of valuable information on this forum, so please feel free to read ans use it... And don't worry about your tablet: it's not bricked unless it's literally broken! Yes, did read some of the forum posts before and some now, could get it to talk to my Win7 host again adb-windows shell gives me some sort of a primitive sh, but I can't see in the Android where it got stuck - no /var/log :-( Tried to re-flash it, the transfer progressed, but it said it would not flash the boot.img since it's the same. It seems, though, that the boot.img is the root of this evil. Downloaded the original ROM executable from the Advent site, but this EXE won't run, because it can't talk to the ADB, but the drivers that Advent delivers are 32 bit only and my Win7 is - guess what - 64 bit. So, how do I either get the boot.img re-flashed or the original ROM re-installed? Edit: re-flashed, now it says "Booting ..." then blinks shortly, comes back with "Booting ..." and that's it. ADB is still working and I can talk to it. Tried to flash the original ROM by utilizing a 32 bit XP and the USB drivers from the Advent site, but the installer says that there is an "unknown device" and won't continue. Edited March 22, 2011 by katopp
Guest katopp Posted March 22, 2011 Report Posted March 22, 2011 So I created a custom ROM in the kitchen. Installed it and it - by sheer magic - worked. The question now is: Why did the standard ROM fail while booting and the custom ROM from the kitchen not? Any means of debugging?
Guest simonta Posted March 22, 2011 Report Posted March 22, 2011 The mcr, despite it's name, is not a ROM. A ROM is a complete image of the firmware, the mcr is an installer. How did you install mcr8? What confuses me is that there are 2 ways to install the mcr, both of which require your Vega to be booted???
Guest rvdgeer Posted March 22, 2011 Report Posted March 22, 2011 So I created a custom ROM in the kitchen. Installed it and it - by sheer magic - worked. The question now is: Why did the standard ROM fail while booting and the custom ROM from the kitchen not? Any means of debugging? I believe you need the ClockWorkMod recovery to be able to start logcat, but am not entirely sure about that! The reason why the MoDaCo Custom ROM worked is probably because it's pushed to the device using ADB, which needs Paul's USB drivers, while the official ROM is being 'pushed' to the device using NVflash, which needs the official USB drivers. While, according to what I understand from you, you were unable to install the official USB drivers, you were unable to flash an official ROM. This should be easily solvable by searching this forum for a (video) guide on how to install the official USB drivers on win 7 x64 (64 bit)... What helps me in most cases is: Ask myself this question: "Is it likely I am the first or only person that has to deal with this problem?" If not: There probably is a solution available somewhere, so search for it! If yes: There's probably no solution for available yet, but search for it anyway. Ask questions later... :D
Guest simonta Posted March 22, 2011 Report Posted March 22, 2011 I believe you need the ClockWorkMod recovery to be able to start logcat, but am not entirely sure about that! The reason why the MoDaCo Custom ROM worked is probably because it's pushed to the device using ADB, which needs Paul's USB drivers, while the official ROM is being 'pushed' to the device using NVflash, which needs the official USB drivers. While, according to what I understand from you, you were unable to install the official USB drivers, you were unable to flash an official ROM. This should be easily solvable by searching this forum for a (video) guide on how to install the official USB drivers on win 7 x64 (64 bit)... What helps me in most cases is: Ask myself this question: "Is it likely I am the first or only person that has to deal with this problem?" If not: There probably is a solution available somewhere, so search for it! If yes: There's probably no solution for available yet, but search for it anyway. Ask questions later... :D FYI, you don't need clockworkmod for logcat, it's part of ADB. There are logcat viewers on the market to view on the Vega, "adb logcat" from a command prompt to view it on your PC. Cheers
Guest bennji_boy Posted March 22, 2011 Report Posted March 22, 2011 Any idea, how long it'll take if you just "leve for a few hours"? The reset did nothing but, well, a reset and it still shows up only the "Booting ..." message, but it doesn't boot. Have a beer, go back and try again. It worked for me!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now