Nexus 7 Stuck in Boot Animation Loop--Please Help - Nexus 7 Q&A, Help & Troubleshooting

***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.

As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here

NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.

simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.

He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine

NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data

If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own

The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P

Does fastboot detect the device?

janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?

Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in

the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.

VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.

NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.

it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.

VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.

janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?

Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)

Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk

comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.

Related

[Q] Fully Bricked n7?

Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you ill try that. it was at 33% battery when this happened though
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
i know about the screen time out, i tapped the screen for it to rewake and it didnt work, then i tried pressing the sleep button once for it to unlock and that didnt work. so it indeed shutoff
frap129 said:
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Click to expand...
Click to collapse
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Anyway, I would proceed with a dead battery or loose battery connector hypothesis first. It's not obvious why writes to /boot, /cache, /data, or /system would affect the bootloader.
Anything is possible at a low enough probability I suppose, but you should start troubleshooting operations with the high-probability scenarios first.
For instance - with the power off, will the "charging screen" display when you plug the tab in? How about APX** mode? (Plug in to PC and start with Power+Vol-up). If you didn't see either of those, it's likely a power supply or hardware problem.
good luck
** make sure you exit APX mode by holding down the power button for at least 20 seconds. I'm not sure if it shuts itself down after an inactivity timeout - you don't want to be draining power while trying to charge the tab.
bftb0 said:
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Click to expand...
Click to collapse
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
frap129 said:
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
Click to expand...
Click to collapse
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
bftb0 said:
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
Click to expand...
Click to collapse
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
frap129 said:
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
Click to expand...
Click to collapse
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Odin is Samsung only
Sent from my Galaxy Nexus
You can hold the power button for 10 seconds and wait till you see the Google logo. Then release and hold it 10 seconds again, when the screen turns off hold the volume down button and wait for it till it automatically boots again. You'll enter bootloader mode. Download wugfresh' nexus root toolkit and install it. When the program is loaded there is a flash stock option on the right side of the program. Select the soft brick / boot loop option under the flash button. While in boot loader mode connect your nexus and press the flash button.
This is all I know!
Sent from my Nexus 7 using xda premium
NEXUS 7 Bricked - NO OS - tried everything but...
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
USB debugging doesn't mean **** when you are in a custom recovery. It has adb already. Your problem is your computer. Fix your computer by following one of the bajillion threads and posts about the nexus 7 drivers issues.
Installing drivers does not need android to be booted.
Your best bet is to put it in fast boot mode and follow Google's own instructions to flash it back to stock.
Sent from my Galaxy Nexus
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
I must admit I'm a little 'hazy' myself when it comes to ADB related issues... I've never had much cause to use ADB. (Think I've used 'adb pull' on a couple of occasions). And I've never been in the invidious position of not having a bootable Android OS on my Nexus 7 either - which does seems to happen a quite lot with TWRP users, less so with CWM users.
Anyway... just had a tinker... and you could try the following workaround... this seemed to work to for me.
----------------------
Locate the folder on your PC where you keep your FASTBOOT and ADB .exe files...
Copy whatever ROM .zip you want into this folder.
The following example uses SmoothROM-v5.0.zip ... There is nothing to stop you from renaming this to something shorter, for ease of typing later... so, in my case, just smooth.zip.
Boot your Nexus 7 into the BOOTLOADER (Vol down [hold] + Power button), and then into RECOVERY (TWRP) and hook it up your PC.
Open a command prompt window on the aforementioned folder... and type...
Code:
adb devices
...which should yield something like the following...
Code:
List of devices attached
012345679ABCDEF recovery
(If you don't see a serial number... then you definitely have a driver problem...)
Otherwise, it's just...
Code:
adb push smooth.zip /sdcard
Or whatever ROM you wish to 'push' to the emulated SD card.
This will likely take a fair few minutes for a 300Mb+ size file (typically the size of your average ROM)... on my Windows XP box it took 4 minutes (1328 KB/s, 32565894 bytes in 239.486s) to copy over. And there are no 'progress gauges' of any kind, either... So season your patience a liitle. You can always pull up another command prompt window and type adb devices again to ensure you still have an ongoing ADB connection.
Once copied over, and still in TWRP, you can just flash it.
Good luck.
Rgrds,
Ged.
Still nothing on mine. im just about to give up and wait to see if google releases the N7 second generation at the i/o
If You familiar with Linux, You can try to understand the logic of
changing the modes.
You need to run udevadm monitor in one terminal. Then press some
combinations of key/s and look for changes with usb-devices.
The better, if You run wireshark and sniff USB interface with your device.
Put attachment here, with a comments what was pressed.
since it seems to be a hardware problem, not software, im just going to send it to asus and see what they can do.

[Q] SOLVED - No touch input - Need to wipe phone

Hello all.
I dropped my N4 the other day, breaking the digitizer. Screen is fine, receives calls and texts etc, but I have no touch functionality at all.
I am not sure I want to fix the phone as it looks a little beyond what I can do. So, I want to sell it as it is for someone else to fix. I am rooted etc on stock rom. Phone is recognised as an android device when connected to my laptop (win 8.1) but I can't access my data at all. I have tried to flash the stock rom again using Nexus 4 Toolkit, but it doesn't find my nexus. I have uninstalled and reinstalled drivers etc. Still no luck.
I booted into recovery, but for some reason I chose a the touch recovery twrp, so that is unusable for me. All I want to do is format the thing to sell it on and be done with it.
Any ideas?
mgolder said:
Hello all.
I dropped my N4 the other day, breaking the digitizer. Screen is fine, receives calls and texts etc, but I have no touch functionality at all.
I am not sure I want to fix the phone as it looks a little beyond what I can do. So, I want to sell it as it is for someone else to fix. I am rooted etc on stock rom. Phone is recognised as an android device when connected to my laptop (win 8.1) but I can't access my data at all. I have tried to flash the stock rom again using Nexus 4 Toolkit, but it doesn't find my nexus. I have uninstalled and reinstalled drivers etc. Still no luck.
I booted into recovery, but for some reason I chose a the touch recovery twrp, so that is unusable for me. All I want to do is format the thing to sell it on and be done with it.
Any ideas?
Click to expand...
Click to collapse
Download the 4.3 factory images, boot your phone in fastboot, connect it to your PC, and use the "Flash-all" script in the factory images zip. It should restore and wipe your phone, and you don't need any touching.
abaaaabbbb63 said:
Download the 4.3 factory images, boot your phone in fastboot, connect it to your PC, and use the "Flash-all" script in the factory images zip. It should restore and wipe your phone, and you don't need any touching.
Click to expand...
Click to collapse
Phone is in fastboot, windows beeps when connection phone up, clicking on 'flash all' brings up the command prompt telling me fastboot isn't recognised as an internal or external command . . . .
Things like debugging are on, as I have the jellybean logo also.
mgolder said:
Phone is in fastboot, windows beeps when connection phone up, clicking on 'flash all' brings up the command prompt telling me fastboot isn't recognised as an internal or external command . . . .
Things like debugging are on, as I have the jellybean logo also.
Click to expand...
Click to collapse
Ok. Install these drivers, then try again:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
abaaaabbbb63 said:
Ok. Install these drivers, then try again:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Click to expand...
Click to collapse
That description really helped on that link. Using that, and then the Nexus 4 Toolkit, it all came together and I have put it back to the stock ROM now. Thank you :good:

[Q] CM installer bricked my nexus

As the title says, I wanted to try CM installer, and I was on everything stock, not rooted. I downloaded PC, and android programs, followed the instructions, however at one point CM installer on my PC said it cannot communicate with my phone, and it was when it was trying to flash recovery. It said I should try different cable, or USB port, but no luck with either, and now it says my phone is not supported.
I tried to enter recovery, but I only get CM guy and it's stuck, even when I turn off the phone, it turns itself on automatically, and to fully turn it off I need to enter fastboot mode, and then turn off. I tried flashing full stock image (I know how to do that, and I have previous experience on this phone), but my fastboot crashes (Fastboot.exe Has stoped Working), tried to download fastboot again, but nothing helped. I also tried to flash recovery only, and I get the same thing... Also tried to do that with custom recovery, but nothing....
Is there something I can do, or do I need a new phone?
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Looks more like issues with your pc communicating with your device, which might have causes other side effects due to that. But I have not tried CM Installer yet.
You should see about getting fastboot working correctly first and getting the right adb/fastboot driver (such as latest Universal Naked Driver, link in my sig). You should also use the latest adb/fastboot .exe from Google, download their latest ADT package. If it still crash, use it on a different machine, if you're on Windows 8 try Windows 7 or Ubuntu.
Also make sure the factory image isn't corrupt, I always have issues downloading it from Google.
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Click to expand...
Click to collapse
If the battery goes to 0%, just charge it, do you think everyone throw away their N4 when the battery goes to 0? There is the red light problem, but its an easy fix.
Thanks for answering, I fixed it with a strange method (to me). On CM forum j_cor told me this:
"Your device appears to be stuck in sideload. So the good news is no, you are not bricked. Here is what I would try to do:
1. Boot the device - wait for the "stuck" CM guy to display
2. Plug phone to PC and open a command prompt to the directory to C:\Users\enter_your_name\cminstaller\bundle\win32
3. from the prompt "C:\Users\enter_your_name\cminstaller\bundle\win32>" type "adb.exe sideload ClockwordMod.cer" (no quotes) and hit enter
4. This will try and sideload this .cer file and will fail - but it should kick you out to the main recovery screen. Select the Reboot option from Recovery
5. Device should boot back up. It will most likely still be the stock ROM. My guess would be that something disrupted the sideload process when installing the system.zip with CM."
However, this did not fix my problem, but it got my phone to communicate with fastboot. So I was able to flash custom recovery, and do a factory reset, which brought me to the stock ROM, I flashed CM the old-fashioned way then.....
And my PHONE IS UP AND WORKING AGAIN!!!
The main problem in communication was that phone blocked every time I booted into fastboot, and plugged USB cable in.... It immediately became unresponsive to any commands, after I did this, phone wasn't getting stuck in fastboot, so that solved my issue.

No Command Error

I went to update to KitKat and it was nearly done and then the "No Command" error came up. My tablet has an unlocked boot loader but isn't rooted. However it was before but I updated it from an OTA and that got rid of it. I've tried booting into recovery etc but the same thing happens.
Anyone have any advice please?
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
tgearhar said:
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
Click to expand...
Click to collapse
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
gunner1937 said:
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
Click to expand...
Click to collapse
I can get to the menu but when trying the reboot option, it just cycles the same way again. Back to the android with a red ! and says "No command." I also tried clearing cache and data to no avail. I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
I spent too much time messing around with and learning how to do things with my SIII and not enough time with this
Same deal here! Not sure what to do short of wiping and losing my info.
Same here...any advice? Not sure what happened. OTA update too.
Significa said:
Same here...any advice? Not sure what happened. OTA update too.
Click to expand...
Click to collapse
Wow, this seems to be widespread, at least somewhat. I'm in same situation. Toolkits, adb, nothing works. I thought this was a soft brick, but now I'm thinking it's toast. Probably doesn't help that I didn't have Dev options enabled along with USB Debugging. I can't even turn it off. Just bootloops after Google logo shows up twice, then to No Command error, then starts over again. I wonder what the hell is causing this. (Device was locked and unrooted)
Same boat here, even sideloaded the factory image via ADB.
[QUOTE [/QUOTE]
I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
If you have android-sdk-windows installed on your computer do not forget to update it through "SDK Manager.exe".
Pushing via ADB didn't work for me. That also failed.
I caved and called Google. Tech support is stumped as well.
Sent from my Nexus 5 using Tapatalk
Could this be a widespread issue? Like I don't even understand why it happened at all!
Sent from my Nexus 5 using XDA Premium 4 mobile app
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
My wife's 2012 N7 is having this same problem. Unlocked bootloader, but I reflashed factory image and unrooted before giving it to her. She got the OTA last night, and now stuck at No Command.
I've subscribed to this thread, hoping that you guys will have it solved before I get home from work tonight! Would love to not have her lose all her data.
(I was kinda mad that she got the OTA last night and I haven't got it yet on my 2013 N7, but that's another gripe for another thread)
killswitch11 said:
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
Click to expand...
Click to collapse
Unfortunately I'm not sure on the SDK manager part. As far as the USB Debugging, I'm 98% sure that I did not have it enabled either. I think I did at one point but after doing several OTA upgrades, I'm sure it got unchecked.
---------- Post added at 01:34 PM ---------- Previous post was at 01:01 PM ----------
kr33mo said:
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Click to expand...
Click to collapse
I don't believe there is a way. Maybe someone smarter than myself can chime in but I had to let the play store do it's thing and re-download all of mine.
tgearhar said:
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
Click to expand...
Click to collapse
Worked for me! Thanks, I don't believe I had USB Debugging enabled either. Shame it wiped all my data though.
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
Click to expand...
Click to collapse
Worked for me as well. Really appreciate that.
Sent from my Nexus 5 using Tapatalk
killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
Click to expand...
Click to collapse
I'll give that a go tomorrow. Missed my tablet! Hope it works!

I know it's the wrong forum, but....please take a look

I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Try fastbooting a recovery like TWRP thati s updated then flash a rom.
disclaimer: I might be no help at all!
You have fastboot -- go learn all the fastboot commands... you need to know the tools and figure a solution!
erase... hmm? why? What about factory reset? I see you are not using LOS 13 but stock image... need root? Basically, I would factory reset/wipe sdcard, then install recovery (TWRP) [okay, so first you would need to use fastboot to install custom recovery)...THEN, push (fastboot an image.zip (LOS or stock) to sdcards, install, and reboot!
Good to have WUG... another tool in the chest (I have never seen it or used it)
Ok, so one clue is that if your computer cannot see it, that says to me RED FLAG... ADB drivers? but you say fastboot works, hmm... I think this is the problem... Koush's universal ADB drivers? official Google drivers? Could these help!
Erasing screen? Hmm...
I would say, for the hell of it, try flashing different ROMs, Recoveries, and Drivers.... you are basically trying to...
Factory Reset/wipe SDcard [system, cache, ... everything], Flash custom recovery (optional), then, some how (fastboot or mycomputer) get an image on to /sdcard, then, install, then, reboot!
Good luck!
luckyheel said:
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Click to expand...
Click to collapse
Why not try this
I have not had this problem with my Nexus 10 but I did once with my Nexus 7 and it may help you.
Instead of trying to flash TWRP and run it (which is not working for you) why not boot into a temporary copy of TWRP and then work from that? To flash TWRP normally (persuming you had renamed the img file to TWRP which makes it easier) you would enter 'fastboot flash recovery twrp.img'. Instead of doing that type 'fastboot boot twrp.img'. This boots into TRWP and from there you will be able run all the options and from there flash TWRP and other images as normal.
If you are having problems with drivers have you used 'USBDeview' ? Run this as Administrator and delete all references to any phone or tablet USB driver and particularly look for devices with Vendor ID '18d1' or '04e8'. Just select them, right click on them and select 'Uninstall Selected Devices'. When they are all cleared reboot your computer and plug your tablet in and it should install the correct driver.
Another option I used successfully with a Nexus 7 in a boot loop was to connect it while running Linux. I don't have a Linux on a computer so I installed one in 'Oracle VM VirtualBox' I don't know Linux but after Googling for help I installed Peppermint Linux and then ADB for Linux. I downloaded the 'TWP' image into a folder in Linux and any other images I wanted. Connect your tablet to the USB port and then on the top menu in VirtualBox select 'Devices' then 'USB' and tick the option which shows your tablet. I then went into what we call a command prompt in Windows but which they call 'Terminal'. Then type 'ADB devices' and if you see it on the list use ADB instead of fastboot. As I mentioned my Nexus 7 was in a boot loop so I typed 'ADB wait-for-device' and as soon as it looped to a point where ADB could see it then the looping stopped and I could flash the images and recover the tablet.
All the best. I hope you are successful.
As long as you can get into bootloader mode, your good.
NOW
If you can't get into boot loader mode? as far as I know...
You're ****ed.
Unless you want to set up usb boot (might not work on Exynos, idk, this is magic to me) and solder the connectors and flash it like they do in factories. That's next level **** too, and considering an N10 is 100$ on amazon you're better off just grabbing a new one.

Categories

Resources