Ok this might seem strange, and just bare with me if I'm being thick...
I have had a nose around the forums and done a search but I couldn't find a solution to my problem.
I installed CM6 (by bumblebee) on my vega via CWM and instantly got BSOD - I didn't really think this was a problem because I knew the risk that it might happen and I had already done a backup etc.
However, all the parts for my new computer arrived the next day so I forget about my BSOD vega for a week as I started building my new computer and setting it up etc etc
I just got round to sorting my vega out when I realised I had completely wiped my old laptop with all the adb drivers on it etc (because I was going to sell it). Therefore, I cant get into recovery or flash anything to it because I cant use any adb commands :s (I cant reinstall the drivers - windows wont recognise the device as adb, only as a mobile device...).
Any suggestions? Am I being thick? Thank you for taking time to read through my rambling post anyway
You should be able to get into recovery and re-flash a stock rom. Make sure the device is plugged into the power and usb. Open device manager in win 7. Then hold down the back button for 2 secs then while still holding back hold power for 2 secs then release power but keep back button down for 2 more secs under universal serial bus controllers a new device should pop up. Point that at the usb drivers from the advent website. When the drivers have installed the screen on the vega will still be black but you should be able to flash the stock rom and start again.
Hope that helps
I will give that a try thanks for your help
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
willk22 said:
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
Click to expand...
Click to collapse
Keep trying to put it into recovery mode. At times it gets picky and you have to time it just right. Took me several attempts before it worked correctly again, so keep at it
Also, be sure to keep the USB plugged in while you are attempting to get it into recovery-mode and your sound turned up so you hear the infamous hardware-connected sound. Once you hear it, immediately plug in the power and start the recovery-flash. Do not wait too long or you'll have to start from scratch again
Keep at it, you're almost there.
Got there in the end thanks for your help!
I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.
Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?
I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.
Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.
Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.
first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.
I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.
lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT
I literally just got the 4.3 OTA update. Phone was fully charged... like 98%. I went ahead and let it update. It rebooted, and it got about 75% into updating and then the icon switched to the sideways android with the red caution symbol and said "Error". I let it sit there for awhile hoping it would do something. It didn't, so I held down power to reboot. It rebooted to the same icon, but now says "No command". I did the vol up/power to get into the wipe/reboot options. I went ahead and rebooted. Every single time... I see the Google logo for like a min, then to the sad android logo w/ "No command". Now I can't even get that far, the indicator light flashes red. I've read that indicates a totally drained battery. Not sure how it can go from full charged to fully drained in a matter of minutes. However on the issue of the error and no command, is my device dead? I've never rooted it or used custom roms. I got the N4 for the pure vanilla stock experience, so I never felt rooting was needed. Any advice? Should I just call Google and request replacement?
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Mercado_Negro said:
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Click to expand...
Click to collapse
It's been charging now for a little over an hour. No animation or indication the battery may be drained other than the red indicator light when I try to go to into the boot loader. Still can't do anything. If I power it on, I see Google logo for awhile, then sad Android icon and "no command". If I try to go into bootloader, just red indicator light and black screen. All while plugged in.
I just don't understand how it went from fully charged to drained in minutes. It was plugged in for hours today. In fact I initiated the OTA update only about 20-30 min after taking it off the charger.
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Mercado_Negro said:
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Click to expand...
Click to collapse
Alright, it's now been charging for 3 hours. I did what you just suggested. All that happens is I see a white Google logo for about 10 seconds, then it goes black. I think the device is off at this point. Stupid question I'm sure... I can't dock my phone to my computer to get any of my data at the "no command" screen can I? It needs to be fully booted, right?
Get into recovery, wipe cache, then it "should" boot.
ksilver89 said:
Get into recovery, wipe cache, then it "should" boot.
Click to expand...
Click to collapse
Like I said above, I'm not able to. I hold down power + vol up and it just shows white Google logo then goes black.
Well hmmm. I just did power + vol down for the hell of it, and I have a menu. Selected "recovery mod" and it just went straight to the sad Android icon with "No command".
I'm not sure what to make of all the stuff I see on this menu...
https://dl.dropboxusercontent.com/u/28754710/20130730_100302.jpg
Here is a short video of what I get from that menu when trying to go into recovery...
https://dl.dropboxusercontent.com/u/28754710/20130730_100936.mp4
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
ksilver89 said:
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
Click to expand...
Click to collapse
Again... like I said before vol up + power does nothing. I can take a video if you like.
Disregard the above. Got it into recovery. I guess my pushing was off or something. I took the rigid case off and made it easier to press the vol button. Let's see what happens now.
Alright. Got into recovery, did a wipe data/factory reset, still no dice. This time it rebooted several times, Google white logo each time, then finally a sad Android icon with "No command". Guessing next step is to download it and try updating via ADB?... or just say screw it and call Google and initiate a replacement?
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
ksilver89 said:
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
Click to expand...
Click to collapse
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
Yes, what he suggested should get you up and running again (if not, then yes your phone needs a replacement). I saw the video and the image. I'm pretty sure your system was wiped somehow and that's why you can't boot to it anymore. If what he suggested fails I can walk you through the steps to flash each factory image separately.
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
unplug your phone. reboot into bootloader (vol down + power) but don't plug it in
downloaded the file posted in this topic from the google website.
http://forum.xda-developers.com/showthread.php?p=44088784
once you download it, extract it to a folder
then open up flash_all.bat in notepad, and it will say -w near the end. remove that (leaving it would wipe all of your data) and save the file
then run it, it will say waiting for device. plug your phone in and it will start updating
flipfamous said:
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
Click to expand...
Click to collapse
Which driver did you try to install? Naked Drivers 0.72? What OS (Win8, Win7, etc)?
Plug your device in, go to control panel, click on Device Manager, scan for hardware changes or select the device with a yellow exclamation mark. Click on "Update driver" and search for the drivers in your PC (where you downloaded them). That should work.
Just Boot from a ubuntu live cd, install fastboot with apt-get and get started
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
Hi there,
I was able to boot the Q fine. I enabled USB debugging, used ADB to reboot into bootloader ran the oem unlock/unlock_accept command successfully. I rebooted and flashed CWM recovery v 6.0.2.7 steelhead. Once this was done, I rebooted into recovery and used adb to push the latest stable release of CM 10.1 to the sdcard. I then flashed this via CWM recovery, and performed a factory reset.
Now that I have rebooted system, it just sits on the cyanogenmod loading splash screen. I left it for over 2 hours at first, then I power cycled device and left it over night. I attempted to go back into recovery, but covering the LED on the top does not seem to result it anything. I power cycled the Q again, and held my hand over the LED from boot to attempt to get into recovery but I am not able to. I also powered device up and waited until the ring LED began to light up, then covered the top LED to see if this allowed to boot into recovery but still no change.
I let the Q boot up once more, and after sitting on the splash screen loading for about 10 minutes, I connected the device back to my PC, and found that adb can see the device. However now that it is running CM 10.1, adb security is enabled and my PC is unauthorized. I am unsure how to proceed at this point. Do I need to try a different PC than the one that was originally used to flash to see if it works (I doubt it will as that wont be authorized either, right?) or am I doing something wrong while trying to get into recovery?
If anyone can shed some light, or assist even getting into recovery, or providing a way to get around the adb authority requirement it would be greatly appreciated.
Ok scratch the above.. I managed to tap on the top LED about 50 times during boot, at which point it turned to red solid LED ring and loaded enough for me to get in using fastboot. I flashed the recovery again, ran a factory reset/wipe cache on it twice, and rebooted. it is now sitting at the home screen ready for me to purchase an OTG USB cable tomorrow and set up cyanogen mod!
So I pulled out my XT907 to test a new cable I have. The port on the phone has been damaged and it won't charge and won't be recognized by my PC. The port stopped working ages ago during a reset to stock using RSDlite. So when the device tries to boot, it goes straight to the fastboot screen and tells me there was a flash failure. This screen also tells you if you have a USB cable connected. Heres where I am confused. According to this screen, when I plug in a cable, the device registers it as being plugged in (or not plugged in), but the PC won't say anything. Since then I thought I also lost TWRP as a result of the flash failure. Today I found out I was very wrong. I got the device to boot to TWRP without issue, the red Motorola logo even appears at boot which hasn't happened since RSDlite failure. From there I went to the file manager and discovered the whole system is still there. So I am confused as to what is really happening here: 1) Either the USB port on the phone works or it doesn't, depending on what you believe (the phone or the PC) 2) If RSDlite did fail, as fastboot says, how would I even be able to boot to TWRP? 3) Given number 2, if the flash really did fail would it cause the device not to be recognized? 4) Also given number 2, the logo shouldn't even appear period. EDIT: 5) With the device powered off and I plug it into an outlet or my PC, it will power on into fastboot and also says USB connected.
So I decided to dig out the phone and play around with it. I can still get into TWRP so I managed to flash system and boot. Here's the weird part. I thought the phone wouldn't charge. I was wrong. It charges on almost every cable, but my PC will not recognize it in AP fastboot or TWRP. I had forgotten about the 3 button trick, volume up + volume down + power brought me to the recovery menu. I just let it sit there for the few seconds it stays and suddenly the red logo appeared...and the phone booted...normally. So it does charge, but adb or fastboot is a no go. Looks like if I keep this phone, I'll be flashing what I can or am able to with TWRP, on an external SD card if I can't download it to internal.
So it appears only the AP fastboot partition is damaged...every time It boots to it (if I didn't intentionally do it) it says "fastboot flash failure". So since I can't use RSD lite, what are my options?
So the only thing that was damaged was AP fastboot and anything beyond that, including 'charging mode' (thanks for that trick @sd_shadow though it didn't work). For a couple years I thought the clip inside the charging port on the phone was too badly damaged to take a charge or be recognized by my PC. So with intentions of fixing it myself, I put it in a drawer until such time. I knew there was some hope in salvaging it despite the 'flash failure' because every cable I tried, would only charge the phone so no PC means no RSD Lite. I was convinced TWRP would save me and I would find a way to flash everything I needed, but was only able to get as far as the boot.img and system.img. So last night I started to play around with the phone after having plugged it in and noticed the green light in the upper left corner turned on. I spent a few hours flashing and reading and flashing some more before I found another post by @sd_shadow referencing to three buttons, press and hold in this order: volume down, volume up and power. That got me to the stock Motorola recovery screen, which only hangs around for abut 10 seconds, so you have to be quick at selecting an option. I did not select an option, and much to my surprise the phone booted all the way and properly. And that was the only issue. I still had TWRP too. However anytime I needed to reboot, it would go straight to the AP fastboot screen. The 3 buttons bypassed that.
I looked inside the charging port on the phone as I had many times before, and noticed what looked like a piece of foil stuck inside of it. I tried to dig it out but I just managed to push it between the crack in the clip. I plugged it back into my PC and I was even more surprised when it made the familiar connect sound. So I assume that piece of foil was actually a pin, and I managed to seat it just right that the phone charges, is recognized by my PC and i was able to SUCCESSFULLY recover using RSD Lite. We're back in business