Guest .stu Posted April 5, 2011 Report Posted April 5, 2011 Got my vega today, but it seems to be faulty. Firstly it wouldn't boot at all - only got the backlight on for a few seconds and that was it. I did manage to get it inot recovery mode and flashed 1.09 with no errors. However, it still wouldn't boot, and I would get is a green android for a few seconds then it would go off. After some persistence, and fiddling with the buttons I found that if I enabled the rotation lock it booted ok, and now I had 1.09 running fine. So I tried to put r9 on, which all went fine except it complained about /system/lost+found not being empty (on checking tho it is empty so don't know what's up with that?). On rebooting tho it just hung with the advent logo on the screen. Adb worked so I connected but on running top I could see that nothing was actually using any cpu. The last thing to run was the boot_animation then nothing. However, I noticed the process id going up by 200 or so every time I ran ps, so I ran it repeatedly and noticed a few irq processes running. When back to 1.09, installed cwm and then CyanogenMod 7, but that also got stuck on the boot animation. Going to put 1.08 on now then retry r9. If no luck then I'll be calling Dixons tomorrow and they can have it back. This is the second faulty one I've had, and I'm wondering if it is the last...
Guest simonta Posted April 5, 2011 Report Posted April 5, 2011 Got my vega today, but it seems to be faulty. Firstly it wouldn't boot at all - only got the backlight on for a few seconds and that was it. I did manage to get it inot recovery mode and flashed 1.09 with no errors. However, it still wouldn't boot, and I would get is a green android for a few seconds then it would go off. After some persistence, and fiddling with the buttons I found that if I enabled the rotation lock it booted ok, and now I had 1.09 running fine. So I tried to put r9 on, which all went fine except it complained about /system/lost+found not being empty (on checking tho it is empty so don't know what's up with that?). On rebooting tho it just hung with the advent logo on the screen. Adb worked so I connected but on running top I could see that nothing was actually using any cpu. The last thing to run was the boot_animation then nothing. However, I noticed the process id going up by 200 or so every time I ran ps, so I ran it repeatedly and noticed a few irq processes running. When back to 1.09, installed cwm and then CyanogenMod 7, but that also got stuck on the boot animation. Going to put 1.08 on now then retry r9. If no luck then I'll be calling Dixons tomorrow and they can have it back. This is the second faulty one I've had, and I'm wondering if it is the last... Strange given everything you've tried. As you know, you've completely replaced all software/firmware so I agree that you're looking at a hardware issue. Sounds like a boot device borked.
Guest Auzdigger Posted April 5, 2011 Report Posted April 5, 2011 Strange given everything you've tried. As you know, you've completely replaced all software/firmware so I agree that you're looking at a hardware issue. Sounds like a boot device borked. I must have the same problem except I never got past the booting screen, despite trying the button pressing combinations
Guest simonta Posted April 5, 2011 Report Posted April 5, 2011 I must have the same problem except I never got past the booting screen, despite trying the button pressing combinations I think you might be confused about something. There are no button combinations needed to get past booting. What are you trying to do?
Guest .stu Posted April 5, 2011 Report Posted April 5, 2011 (edited) Ok so I tried 1.08 and then r9 but no joy. Last thing to try was to use cwm to install r9... and to make doubly sure once I got into cwm I formatted all the partitions under the mounts option. Finally I got past the boot screen!! However, on pressing home the vega crashed and got stuck on the boot screen again B) So I thought once last thing to try - CM7 via cwm (again). This time it worked and I am just setting everything up :D However, I seem to have an intermittent problem with the back button, which requires me to toggle the rotatin lock to get it working again. I'll keep an eye on that and if it gets any worse I'll get Dixons to exchange it. Anyway, at least there's a happy ending. Dunno why this tablet was such a pain tho I suspect there was something wrong with the system partition on the nvflash which Paul's cwm script sorted out (I noticed it spent a while erasing the partitions rather than just formatting the fat). Edited April 5, 2011 by .stu
Guest Auzdigger Posted April 6, 2011 Report Posted April 6, 2011 I think you might be confused about something. There are no button combinations needed to get past booting. What are you trying to do? I turn on the vega, it says booting, then blinks, then says booting again, gets to the advent logo then seems to switch itself off. I have tried all the back and power button pressing advice in the first bricked vega thread, and it seems to be making no difference. I am despairing here...I have the Modaco R8 rom on it - does that mean the warranty is voided if I take it back to Currys?
Guest .stu Posted April 6, 2011 Report Posted April 6, 2011 I turn on the vega, it says booting, then blinks, then says booting again, gets to the advent logo then seems to switch itself off. I have tried all the back and power button pressing advice in the first bricked vega thread, and it seems to be making no difference. I am despairing here...I have the Modaco R8 rom on it - does that mean the warranty is voided if I take it back to Currys? This sounds similiar to what I had last night. If you're getting to the boot screen then recovery mode will work, just make sure the charger and usb are plugged in, hold power for 10 seconds to make sure it is completely off, then do the back/power/back combo and keep trying till you here the 'ding' on your pc to say new hardware found. Then reapply 1.09 from advent vega. At that point you should be able to reinstall the MCR r9. If it still won't boot take it into store and get them to exchange it. If they try to send it off for repair tell them that you rang customer services earlier and they told you that it was a code 5 and you should take it into store for an exchange.
Guest Auzdigger Posted April 6, 2011 Report Posted April 6, 2011 This sounds similiar to what I had last night. If you're getting to the boot screen then recovery mode will work, just make sure the charger and usb are plugged in, hold power for 10 seconds to make sure it is completely off, then do the back/power/back combo and keep trying till you here the 'ding' on your pc to say new hardware found. Then reapply 1.09 from advent vega. At that point you should be able to reinstall the MCR r9. If it still won't boot take it into store and get them to exchange it. If they try to send it off for repair tell them that you rang customer services earlier and they told you that it was a code 5 and you should take it into store for an exchange. Thanks for that - could you please explain exactly how to do the back/power/back thing as I can't seem to get that to work. Thanks
Guest WelshPhil Posted April 6, 2011 Report Posted April 6, 2011 I had a similar problem yesterday, went to the booting screen, advent logo came on then screen went blank, tried a few times but with no joy. In the end I just plugged it in and left it to charge for a while, hey presto it fired up first time, the battery must of been completely dead.
Guest Auzdigger Posted April 6, 2011 Report Posted April 6, 2011 This sounds similiar to what I had last night. If you're getting to the boot screen then recovery mode will work, just make sure the charger and usb are plugged in, hold power for 10 seconds to make sure it is completely off, then do the back/power/back combo and keep trying till you here the 'ding' on your pc to say new hardware found. Then reapply 1.09 from advent vega. At that point you should be able to reinstall the MCR r9. If it still won't boot take it into store and get them to exchange it. If they try to send it off for repair tell them that you rang customer services earlier and they told you that it was a code 5 and you should take it into store for an exchange. I managed to figure out how to get into recovery mode and reflashed the stock rom 1.09.I then transferred the R8 image successfully but the vega doesn't seem to be loading it properly. The android symbol comes up goes off comes up....any ideas anyone?
Guest simonta Posted April 6, 2011 Report Posted April 6, 2011 I managed to figure out how to get into recovery mode and reflashed the stock rom 1.09.I then transferred the R8 image successfully but the vega doesn't seem to be loading it properly. The android symbol comes up goes off comes up....any ideas anyone? Charger in and working? If so, flash stock and install r8 again, watch closely for any errors.
Guest .stu Posted April 6, 2011 Report Posted April 6, 2011 (edited) I managed to figure out how to get into recovery mode and reflashed the stock rom 1.09.I then transferred the R8 image successfully but the vega doesn't seem to be loading it properly. The android symbol comes up goes off comes up....any ideas anyone? I had exactly this last night. Try toggling the screen lock button - dunno why but it seemed to work for me. Thought mine was dead but I kept trying and eventually it booted up and now here I am replying to you on it. Even if it won't boot at least you got it back to stock so no worries about getting it exchanged. Edited April 6, 2011 by .stu
Guest bojjob Posted May 19, 2011 Report Posted May 19, 2011 LOVE. +Rep a billion if there was an option. :rolleyes: I AM ACTUALLY GOING TO CRY WITH LOVE. I thought i was screweeed with void warranty, managed to get into recovery with help here and wack on 1.10, just about to redo onto pauls R8 to :P
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now