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!
Related
Using the terminal in Linux Mint 12, I unlocked, rooted, and flashed a custom recovery to my Nexus 7. The first time I did this, I neglected to use the OEM cable, and the recovery that I flashed did not take, bricking my Nexus. I reflashed the recovery, with the OEM cable, and from CWM recovery I installed the latest cm10 with gapps. The first time I booted it, I went through the setup procedures and logged in. After about a tenth of a second of the homescreen being visible, my Nexus crashed. And by crashed, I do not mean it went black and showed my the Google screen, I mean that it went black, then he screen fuzzed with visual artifacts, and was unresponsive until the battery drained completely.
I then, using the terminal, reflashed the recovery, went in and reflashed the cm10 ROM, then the gapps, and booted. Now, it works fine.
However! Upon rebooting to the bootloader, either through the on device menu, or through ADB, fastboot is dead. It displays the device information, the little android man, and the arrows pointing to the Power button and volume rocker. When I press either of these buttons, nothing happens. If I am connected to ADB, I cannot see the device, even after restarting the server.
Has anyone had similar issues? Does anyone have any advice?
Yes, I am running everything as root, and yes, I have checked that USB debugging is on.
I need help. I was on stock android 4.1.2 while rooted and unlocked with cwm. I was using it this morning when I got the notification for the ota 4.2.2 I accepted it and the device rebooted. I got a message saying if I wanted to install the update because it wasn't signed. It looked like I was in cwm at this point. I said yes, and it proceeded to try and install, halfway through it just rebooted and brought me back to that screen again. I tried a few times before saying cancel. I was then brought to the main cwm menu, I selected device reboot. It booted into android after a lengthy time, but when it loaded android it's a black screen with the clock lock screen widget, and anytime I try to get past the screen shuts off. I don't have any way of booting into cwm, I can't do it by powering down then powering up holding the volume down button had to use rom manager. Please, any ideas on how to un**** this up. I was able to get my computer to list it in adb devices, but when i typed in reboot-recovery it says android debug bridge 1.0.31 and the lists all the commands. After being connected to the computer for a few minutes it just shuts off and won't turn back on unless I plug it into the wall for a few minutes. If while in adb I type adb reboot-bootlader it reboots but not into the bootloader.
Update, about the 3rd time I tried the adb reboot bootloader it worked, I was able to get into fastboot and flash a stock image, works fine now. No idea how it got so bad from just that though
So to answer the first question, yes I followed the stickied guide up top, and yes, it successfully flashed the bootloader, wiped all data, and flashed stock ROM all to success. It appears my case is unique. I was told that it could be the battery connection, so I've done no fewer than half a dozen times of taking the back off, resetting the battery connection, and closing back up. It does not appear to be the battery.
I am stuck on the fastboot screen, the one where the android is lying down and blue squares project from an body. It shows me the controls I can make with the volume switches and the selection choice of 'Start'... but I cannot do anything. Before I went to flash I could move through the selection with Vol Up ONLY, but now I cannot even do that. Here's all the mode says:
Code:
FASTBOOT MODE
product name - grouper
variant - grouper
hw version - er3
bootloader version - 4.23
baseband version - n/a
serial number - ###############
signing - not defined yet
LOCK STATE - UNLOCKED
I've pretty spent the past twenty four hours on google searching through all the threads I've seen. They are either all dead, or most of them found the sticky fixed their problem. Has anyone heard of it coming to this?! All I can do is access fastbook VIA a DOS prompt and do fastboot commands, and if I disconnect the tablet from my PC, it'll remain in this mode with the screen on until the battery dies. Charging appears to charge the tablet, but again, no controls work. And yes, the buttons were set properly when I closed my tablet.
Anyone?
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
...Awesome... said:
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
Click to expand...
Click to collapse
I'm just trying to boot up! I don't know what happened, but I haven't been able to use it for school all week!
I cannot boot into the OS. Any time I plug this device in it sends me to the fastboot screen with no controls.
OK I just flashed CWMR 6.0.4.3 and it did not fix the problem.
Any other ideas?
I just repeated all the steps again to see if any of them failed before, they have not worked. So recap:
Stuck in fastboot mode
Android will not boot
Loose battery connection is not the problem
I am able to access fastboot on my computer
I have followed everything from the sticky (wipe everything, flash bootloader, flash image)
I have flashed a new recovery
I am still stuck in fastboot
I cannot control options in fastboot with the volume and power buttons
I can only access fastboot by charging my tablet
The only way the tablet will power down is when it completely depletes it's battery
As far as I can tell, nothing was wrong with the tablet when it was functioning
This happened when I went to charge my tablet, presumably when the battery ran flat running android
If I charge too long the tablet gets fairly hot.
That's about all the information I can provide. Is there anything else I can try? Please, I need a tablet for school and I cannot afford a new one!
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
Alright, I just got my Nexus 6P up and running again and wanted it to be my secondary phone for work, but now I'm facing an issue I'm not familiar with.
So, the phone works just fine, I have PureNexus 7.1.0 installed on it along with Magisk and I am sure I have TWRP installed on it as well. But I'm not 100% sure.
The issue is that I can't get my phone to boot into bootloader or recovery mode. As soon as I try to enter bootloader or recovery I only get a black screen, nothing else.
To boot back into the phone I have to keep holding my power button down and enter my charging cable or my PC and with some fiddling around it boots just fine into OS.
So, how can I, or, how am I supposed to fix something like this? I can't get adb to work since I can't get into bootloader. Although it still finds my device when I enter the black screen when using adb reboot bootloader command but it won't do anything with the device. So, if I want to install a new recovery it won't do anything, just saying "error: device not found".
Edit: I just want to add that if I do a wipe (factory reset) nothing happens. The device turns off, I insert the charging cable and spam the power button and it just boots like nothing happens, everything remains on the phone.