Jump to content

Can't boot into recovery...


Recommended Posts

Posted (edited)

So before all the various responses, I'll just say that 'yes' I have searched the forums, 'yes' I have read all the relevant threads, 'yes' I have tried to boot into recovery following Advent instructions and no, nothing has worked........

Anyway, Vega has been running very well with 1.06.05 with MCR R6 & PP. Originally I had some issues with USB switching so used the standalone switch APK and this has been working perfectly for weeks; I probably switch modes 2-3 times per week so am fairly sure it's been OK.

Ran switcher today (host-slave) to copy some e-books across and at reboot, got the error message "Starting Fastboot USB protocol screen". 'Bugger' I thought so read a few posts and through that I *might* get away with reboot to recovery then reflash boot.img However, try as I might, I just can't get the Vega to boot into Recovery. I have tried the back / power / release back combination using a combination of timings from 1-5 seconds and after 40-50 attempts, can't get anything to boot except the darn "Fastboot USB" message.

Vega is now left on (unplugged) to see if running the battery down has any effect but any useful suggestions for getting into recovery or past the Fastboot error gratefully received.

Edited by MaxiP
Guest gingercat
Posted

Did you definitely connect the power adapter when trying the advent instructions? I know I didn't the first time I tried it but it won't work if you don't.

Posted

power connected / not connected......USB cable connected / not connected and every possible combination

Guest trevor432990
Posted

When you connect the Vega to the PC does anything come up about the device and what PC OS are you on Max? ;)

Guest Yogimax
Posted

I know it's obvious, but have you tried the sequence from the Advent Vega manual which states power button first for 6 seconds? ;)

Turn the Vega off by holding down the POWER button for 6 seconds

o Once off, hold the BACK button down for 2 seconds

o Then, whilst keeping the BACK button held, press and hold the POWER button for 2 seconds

o Then release just the POWER button but keep holding the BACK button for a further 2 seconds

o Release the BACK button

Posted

At first I had a lot of problems trying to get into recovery mode too. After some testing I wrote a procedure that works for me:

  • USB cable must be connected to the PC. If you're using Windows, you must have the proper USB drivers installed (covered in other posts).
  • Power connector must be plugged (and the battery possibly must have reached a certain charge level, although I'm not sure about this, since I always have my tablet nearly 100% charged when flashing).
  • The proper button combination is not well described in the manuals. I always had problems when they told things like "press for 2 seconds". What does that mean? Up to 2 seconds? 2 seconds or more? 2 seconds plus/minus half a second? After some play time, I have a non-ambiguous procedure that works for me every time:
    1. Press BACK button for AT LEAST 2 seconds and keep pressing it
    2. Press POWER button for AT LEAST 1 second while keeping BACK pressed
    3. At this precise moment, the USB device is detected (in Windows, you hear a sound; in Ubuntu, using "nvflash --wait", you'll see text appearing on your terminal).
    4. Once the device is recognized, you can release the buttons in any order or timing you want. The manual tells otherwise, but beyond this point the timing and order of the release of the buttons don't seem to have any effect.
    5. If this doesn't put you in APX mode, press POWER for 6 seconds or more until the device is fully powered off. Then unplug the power connector, wait a few seconds and plug it again. Wait until the blue LED turns on. Repeat the procedure from the beginning.

Posted (edited)
When you connect the Vega to the PC does anything come up about the device and what PC OS are you on Max? ;)

Windows 7 x64 - PC 'beeps' to show that a device is connected and 'Android ADB Interface appears in device manager'

Yes, I've tried the Advent sequence 'as is' as well as doing the button combinations for 1/2/3/4/5 seconds

I've removed / uninstalled PC drivers and when I connect, get a new device called NVIDIA Android Fastboot Device, which says it has the right drivers; if I uninstall & delete drivers, I can install the original Advent ones, reboot and start the process again.....

The error message appears before I release the back key and / or Windows has signalled that a device has been attached.

Confused, annoyed, etc

Edited by MaxiP
Guest trevor432990
Posted (edited)
Windows 7 x64 - PC 'beeps' to show that a device is connected and 'Android ADB Interface appears in device manager'

Yes, I've tried the Advent sequence 'as is' as well as doing the button combinations for 1/2/3/4/5 seconds

I've removed / uninstalled PC drivers and when I connect, get a new device called NVIDIA Android Fastboot Device, which says it has the right drivers; if I uninstall & delete drivers, I can install the original Advent ones, reboot and start the process again.....

The error message appears before I release the back key and / or Windows has signalled that a device has been attached.

Confused, annoyed, etc

From what I've read from other people the fact it appears to be recognised by the PC is a step forward at least though I don't know what that Fastboot Device is. Have you got a Windows XP device available as well cos I know a number of people have corrected their bricking only when reverting to XP?

Edited by trevor432990
Posted
From what I've read from other people the fact it appears to be recognised by the PC is a step forward at least though I don't know what that Fastboot Device is. Have you got a Windows XP device available as well cos I know a number of people have corrected their bricking only when reverting to XP?

XP - unfortunately not. All my PC's are Windows 7

Just to be clear, the device connects to the PC BUT I don't get a chance to recover as the error message 'Starting Fastboot download protocol' before the devices boots into recovery. No matter what key combination or USB / power mix I try, I just simply can't get anything apart from that error message - it appears before the PC has confirmed that a device has been attached / started. I'm very IT literate and have been working with Android for a couple of years so understand many of the niggles getting it to work properly - the nearest I can describe this is bricked with a nice error message on the screen.

Posted

Don't know how / why but on the 143rd (or thereabouts) attempt to get into recovery, it finally did it.

Have reflashed with Higgsy_Modded_v1.08_Vega_RC2 and I'll then decide what bits to layer on top.

Guest Yogimax
Posted
Don't know how / why but on the 143rd (or thereabouts) attempt to get into recovery, it finally did it.

Have reflashed with Higgsy_Modded_v1.08_Vega_RC2 and I'll then decide what bits to layer on top.

Hallelujah....

Guest trevor432990
Posted

Well done Max it might be worth installing that wireless ADB app in case it has another hiccup ;)

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.