Guest extrememonkey Posted January 27, 2011 Report Posted January 27, 2011 Hello all, Problem here... Tried switching to USB slave mode via the switcher widget.... and I have got stuck on a Black Screen saying "Starting Fastboot USB download protocol" in the top left corner - this has hung here for at least 30mins and nothing is happening. I hard reboot by holding the power button for 8 secs, but when I power back on I just get the same. When I plug my vega into my PC it "pings" to say it has picked up my device but I cant see it anywhere How do a get my baby back up and running????
Guest Lennyuk Posted January 27, 2011 Report Posted January 27, 2011 Hello all, Problem here... Tried switching to USB slave mode via the switcher widget.... and I have got stuck on a Black Screen saying "Starting Fastboot USB download protocol" in the top left corner - this has hung here for at least 30mins and nothing is happening. I hard reboot by holding the power button for 8 secs, but when I power back on I just get the same. When I plug my vega into my PC it "pings" to say it has picked up my device but I cant see it anywhere How do a get my baby back up and running???? run a stock rom on it (or Higgsy 1.08 on xda) via booting into recovery mode.
Guest extrememonkey Posted January 27, 2011 Report Posted January 27, 2011 run a stock rom on it (or Higgsy 1.08 on xda) via booting into recovery mode. Obviously gonna loose all data settings etc???
Guest olionair Posted January 27, 2011 Report Posted January 27, 2011 run a stock rom on it (or Higgsy 1.08 on xda) via booting into recovery mode. so usb switching is breaking it then?
Guest extrememonkey Posted January 27, 2011 Report Posted January 27, 2011 (edited) OK, really really need help here I cant boot into recovery mode (back for 2secs, power for 2secs - whilst still holding back, release power and hold back for a further 2secs) as soon as I let go over the back button up pops the "Starting Fastboot USB download protocol" screen When I plug my Vega into my PC, I get the ping that the pc sees my Vega. In Device Manager it pops u as ANDROID Phone - Android ADB Interface..... I have no idea what I can do to get my baby up and running again...... PLEASE PLEASE help me..... Edit: I think I have got it into recover. Blank screen but pc sees it in device manager under other devices as APX with a yellow ! On it??? Edited January 27, 2011 by extrememonkey
Guest extrememonkey Posted January 27, 2011 Report Posted January 27, 2011 ok back up and running on stock 1.06.5 .... now just to add the super powers again!!!
Guest Logseman Posted January 28, 2011 Report Posted January 28, 2011 ok back up and running on stock 1.06.5 .... now just to add the super powers again!!! Could you bring it back to life as per the instructions? And which operative system did you use in the computer you used to restore it?
Guest Cwmdu86 Posted January 28, 2011 Report Posted January 28, 2011 I had a similar problem a while ago and fixed it by flashing the boot.img Extracted the contents of the 1.06.5 image to a folder (run the exe without the vega plugged in and it will show you the path where the contents of the exe file were extracted to. e.g. c:\docume~1\Mark\locals~1\Temp) Then managed to restore the boot image from the extracted exe and reboot using command below fastboot flash boot boot.img fastboot reboot Haven't lost any applications or settings as far as I can tell.
Guest extrememonkey Posted January 28, 2011 Report Posted January 28, 2011 Could you bring it back to life as per the instructions? And which operative system did you use in the computer you used to restore it? I used my old windows xp desktop, comes in useful every now and then.... My vista machine didn't work, never has when its anything to do with Android......
Guest MaxiP Posted January 31, 2011 Report Posted January 31, 2011 (edited) I've just had this same message !!! After weeks of successfully switching between the 2 modes, it has hung today when trying to switch from host to slave. The only thing that I can think I have done recently (???) to the system / desktop, was to use ADW 'Lock Desktop' to stop me moving / deleting icons by accident. I can't think of any other changes that have been made. Annoying but if I have have to re-install, then that's what I'll do but can't understand why this has just happened. Anyone else getting this error as if it's a coding error, I would have expected many more users to see it. edit - I have CWM installed and it has been working previously. Now, can't even seem to boot into recovery !!! Edited January 31, 2011 by MaxiP
Guest Cwmdu86 Posted January 31, 2011 Report Posted January 31, 2011 (edited) I've just had this same message !!! After weeks of successfully switching between the 2 modes, it has hung today when trying to switch from host to slave. The only thing that I can think I have done recently (???) to the system / desktop, was to use ADW 'Lock Desktop' to stop me moving / deleting icons by accident. I can't think of any other changes that have been made. Annoying but if I have have to re-install, then that's what I'll do but can't understand why this has just happened. Anyone else getting this error as if it's a coding error, I would have expected many more users to see it. edit - I have CWM installed and it has been working previously. Now, can't even seem to boot into recovery !!! See my post 3 above this one. As long as you can see Vega in windows it should work. Mine had problems exactly the same when I used gscript to switch between host and slave. Edited January 31, 2011 by Cwmdu86
Guest yabbas Posted February 26, 2011 Report Posted February 26, 2011 (edited) I had a similar problem a while ago and fixed it by flashing the boot.img Extracted the contents of the 1.06.5 image to a folder (run the exe without the vega plugged in and it will show you the path where the contents of the exe file were extracted to. e.g. c:\docume~1\Mark\locals~1\Temp) Then managed to restore the boot image from the extracted exe and reboot using command below fastboot flash boot boot.img fastboot reboot Haven't lost any applications or settings as far as I can tell. Cheers - having tried to switch USB modes just now on 1.09 with FUJI 0.3 - I got the Fastboot message. 2 by 2 by 2 flash recovery wouldn't work no matter how many times I tried it! (I thought this was a hardware flash step, odd that!) Fastboot the kernel worked a treat :huh: kudos to you - I wondered where the hell fastboot was :) Edit: Hmmm ... tried USB switch again knowing I can recover. This time I got stuck on "Booting . . . ." with a quick flash of the screen (instead of loading into the OS.) Think my only issue was having the "disk is full" message as I'd installed a helluva load of Apps. I'm not convinced with the USB switcher is foolproof - if space was an issue for switching kernels it should throw up an error, which is a real shame. Edited February 26, 2011 by yabbas
Guest Bradmax57 Posted February 28, 2011 Report Posted February 28, 2011 Cheers - having tried to switch USB modes just now on 1.09 with FUJI 0.3 - I got the Fastboot message. 2 by 2 by 2 flash recovery wouldn't work no matter how many times I tried it! (I thought this was a hardware flash step, odd that!) Fastboot the kernel worked a treat :huh: kudos to you - I wondered where the hell fastboot was :) Edit: Hmmm ... tried USB switch again knowing I can recover. This time I got stuck on "Booting . . . ." with a quick flash of the screen (instead of loading into the OS.) Think my only issue was having the "disk is full" message as I'd installed a helluva load of Apps. I'm not convinced with the USB switcher is foolproof - if space was an issue for switching kernels it should throw up an error, which is a real shame. I had this on friday eventually on sat evening I got it sorted by reinstalling 1.09 and then installing r8. All seemed good and managed to use the usb switcher mode without problems, just tried to switch and bang, same message at the top of the screen, here goes again....... and to top it off, i left my usb transfer cable at work, what can be causing this problem as it works fine then doesnt, hopefully get a proper fix soon otherwise ill just not bother with the swaping
Guest mrguest Posted March 1, 2011 Report Posted March 1, 2011 I had this on friday eventually on sat evening I got it sorted by reinstalling 1.09 and then installing r8. All seemed good and managed to use the usb switcher mode without problems, just tried to switch and bang, same message at the top of the screen, here goes again....... and to top it off, i left my usb transfer cable at work, what can be causing this problem as it works fine then doesnt, hopefully get a proper fix soon otherwise ill just not bother with the swaping Yep, ive had the same thing. Once I tried to read from the USB port I find that the Vega gets stuck in "Booting" and I have to resinstall. Was a nightmare last week as I had gone away and copied loads of stuff to watch and didnt have it for a week as I couldnt reinstall. Its happened twice to me and both times after using USB Switcher, so I am sure that is the problem. I dont mind reinstalling, but I am seriously thinking about buying the Dock as I can copy things without worry that way.
Guest Deftknight Posted March 1, 2011 Report Posted March 1, 2011 Yep, ive had the same thing. Once I tried to read from the USB port I find that the Vega gets stuck in "Booting" and I have to resinstall. Was a nightmare last week as I had gone away and copied loads of stuff to watch and didnt have it for a week as I couldnt reinstall. Its happened twice to me and both times after using USB Switcher, so I am sure that is the problem. I dont mind reinstalling, but I am seriously thinking about buying the Dock as I can copy things without worry that way. The same happened to me when switching USB modes, again I struggled to get into recoverery. I eventually managed it but being very newbie I am still struggling with updating the ROMs - I got there eventually. I needed several attempts and I seemed to notice that if I shutdown ie hold down power key and the back key together then reboot, shutdown again, then do the 2 sec thing it worked and gave me recovery mode. Yes it could just be coincidence but its such a horrible situation and just thought I'd share. In recovery it showed up as nvidia USB recovery so I ran the Vega update from the site then rc8 (which is great but I'm getting Honeycomb envy!). Titanium backup to restore.. It was a painful evening so I'm waiting until USB mode switching is safe.. Is there a way of warning newbies like me that this might lead to problems in a sticky under the rc8 download? A known issues sticky?
Guest Ste_B Posted March 6, 2011 Report Posted March 6, 2011 Same has just happened to me. Trying to install offical USB driver from advent site so I can flash with the latest version from them. It isn't happening for me because I can't remember which one it is. Is it 'android debug bridge'? Think I tried them all but didn't find device. I have searched the forum that's how I ended up here. Any advice would be great. I'm going for a few beers now, my head hurts. lol
Guest Buzing Bee Posted March 7, 2011 Report Posted March 7, 2011 Ok iv been stuck in fastboot mode a few times the best way i found of getting out of it is :- 1) holt power for 10-15 sec to power off unit 2) unplug usb and power for ~10sec 3) plug power and usb in and wait ~10sec 4) use the apx combo (back (2sec) --> back + pwr (2sec) -- pwr (2sec) ) you should get blank screen and apx mode show up on your computer :-D This may take 3 - 4 attempts to get timeing right :(
Guest Ste_B Posted March 7, 2011 Report Posted March 7, 2011 Ok iv been stuck in fastboot mode a few times the best way i found of getting out of it is :- 1) holt power for 10-15 sec to power off unit 2) unplug usb and power for ~10sec 3) plug power and usb in and wait ~10sec 4) use the apx combo (back (2sec) --> back + pwr (2sec) -- pwr (2sec) ) you should get blank screen and apx mode show up on your computer :-D This may take 3 - 4 attempts to get timeing right :( Thanks mate.
Guest MattElliott Posted March 8, 2011 Report Posted March 8, 2011 I had a similar problem a while ago and fixed it by flashing the boot.img Extracted the contents of the 1.06.5 image to a folder (run the exe without the vega plugged in and it will show you the path where the contents of the exe file were extracted to. e.g. c:\docume~1\Mark\locals~1\Temp) Then managed to restore the boot image from the extracted exe and reboot using command below fastboot flash boot boot.img fastboot reboot Haven't lost any applications or settings as far as I can tell. Thanks for that, it seems to have restored my vega without loosing anything as well :( You can also get a copy of fastboot if you download the android SDK, at least it's in the windows version, but you need to run it from the platform-tools directory so it can pick up the AdbWinApi.dll that's located with adb. Also thanks to Paul and everyone contributing to this site, it's the only reason I bought a vega and I'm glad I did. Matt
Guest Mogedwards Posted March 10, 2011 Report Posted March 10, 2011 I have exactly the same problem and have tried everything sugested with no success. The problem occured when I switched the USB ready to install the latest Rom but this is the message I get in the DOS window: "Waiting for device...ensure 'USB debugging' is enabled in Settings-Applications-Development and connect to PC" The trouble is, I did set it to USB debugging but now I can't get into the Vega to do anything, although that is what my PC is asking me to do. The Vega shows up in device manager as as Android phone and I am using XP. Any suggestions
Guest nex1 Posted April 5, 2011 Report Posted April 5, 2011 I had a similar problem a while ago and fixed it by flashing the boot.img Extracted the contents of the 1.06.5 image to a folder (run the exe without the vega plugged in and it will show you the path where the contents of the exe file were extracted to. e.g. c:\docume~1\Mark\locals~1\Temp) Then managed to restore the boot image from the extracted exe and reboot using command below fastboot flash boot boot.img fastboot reboot Haven't lost any applications or settings as far as I can tell. Thanks for that. This worked for me too. Instead of the 1.06.5 stock image, I used the one from the r8 pack and got everything back OK.
Guest ace_dynamo Posted April 9, 2011 Report Posted April 9, 2011 Thanks so much, I also just used the boot.img from mcr rom and everything restored absolutely fine - luckily I had USB debugging enabled when it crashed, though not sure if this would have mattered???
Guest hwaggers Posted May 25, 2011 Report Posted May 25, 2011 How did you get it back up and running from not been able to recover it? id appreciate the help
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now