[Explicit]

This is my fiancee's moms phone and USB debugging is not enabled. She was promoted the update and this is the end result. I've tried reflashing the image files through adb with no end result. I've tried wugs toolkit which is useless because USB debugging is not enabled. I'm at wits end with this phone. Any ideas on what I can do? Also when in recover mode the language is not in english. Did Google botch the update that was sent to her phone?

The Android recovery system <3e> is KRT16S

[Explicit]

I followed this

I was in the same situation and ran into that issue as well. What I did was download the 4.3 factory image from here: https://developers.google.com/androi...s/images?hl=vi

Make sure you get the correct one for your device. I have a 2013 wifi so I chose: Android 4.3 (JSS15R)

Inside that downloaded file, you'll find image-razor-jss15r.zip. It's a couple of levels down. Unzip the files from there to your SDK folder (should be boot.img, recovery.img, system.img, userdata.img, and cache.img).

Boot your Nexus 7 to the bootloader (volume down + power) and connect to your PC with USB cable. Do NOT go into Recovery mode yet.

From the command prompt, make sure you can see your device: fastboot devices

Then, run the following commands:

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img

At this point you have a clean install of 4.3 JSS15R.

Now go to Recovery mode and sideload the 4.4 OTA as you originally tried and it should work this time.

I followed these steps and was able to update to 4.4 without losing any data. YMMV

It took away the random foreign language stating "No Command", but I'm still stuck in the boot animation. I really thought it was going to work and while I feel I took a step forward, it is no where that i'd like to be at. Any ideas on what I can do next?

[someguy01234]

I assume your mom phone bootloader was unlocked before you did the steps you mentioned to save her datas.

There is some changes in your /data partition that cause it. I fixed it by factory reseting. However, if you reset using stock recovery it will wipe the entire /data partition, which means not only your apps data, but also everything in your internal storage.

Factory reseting with a custom recovery will wipe the /data partition, but not /data/media, leaving internal storage alone.

You don't have to install custom recovery, but just boot into it one time using: fastboot boot recovery.img

You can get TWRP recovery for N4 here: Techerrata Downloads - Browsing mako

Boot into it and create a backup image of your device Then you can do a factory reset, the phone should boot then. You'll just have to accept to lose your apps data.

You could backup your apps data using the command: adb pull /data/data C:\backup\appsdata.

But it's not going to be too useful because it could be a pain to restore since you have to fix the file permissions for the files after restoring them.

[Explicit]

Followed this and it finally worked. What a 4 hour ordeal smh

I also managed to fix my Nexus 7 2012 Wifi using Wug's Nexus Toolkit. ( I assume this toolkit will work with Nexus 4,7 and 10 as it is a unified toolkit.) NB: As you will flash stock you will loose all your apps and settings. At least it is better than being stuck with the "No Command" screen.

1. Download and install Nexus Root Toolkit v1.7.8: Nexus Root Toolkit v1.7.8 | WugFresh
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will have a working Nexus again. I thought I was going back to stock and would have to install 4.4. But ended up with 4.4. .

I hope this helps someone else.

Nexus 7 (2012) stuck in "no command" bootloop

[someguy01234]

If you had followed my advice you wouldn't have to lose all your datas.

[Explicit]

If you had followed my advice you wouldn't have to lose all your datas.

Actually the bootloader wasn't unlocked. It was as stock as stock can be. I attempted to save anything on the phone, but I couldn't even get the phone to be recognized as a MTP device. Seemed like the OTA was screwed up and essentially wiped her phone when the phone first failed. Without USB debugging enabled, it seemed like losing everything was bound to happen. Sucks, but at this point the fact that I got the phone back into working state is good for me. I have made sure the USB Debugging is now enabled incase this starts to go to hell again. I know my fiancee's mom has lost all trust in Google products. Nothing I can do about that sadly.

[O12]

Explicit: I just want to say thank you because this method worked perfectly on my girlfriend's Nexus 4. Now, it's running Android 4.4. Google Support was useless. The representative said that rooting may have caused it but I argued that there are locked bootloader, unrooted N4 owners out there that are having the same issue after applying the update OTA so it is clearly something wrong on Google's side. The rep also doesn't seem to be that knowledgeable about Android anyway, she probably read and pasted answers from a FAQ. Once again, WugFresh's toolkit relieved my anxiety because my girlfriend was going to be mad at me for soft-bricking her phone I bought for her, haha. Cheers!

[entersanjay]

Hi,

I've got my Nexus 4 stuck in a boot loop as well after I tried to update to 4.4.3 OTA. I was just wondering how did you manage to use the toolkit without USB debugging being enabled?

Thanks

[Shalgi]

Hi all,
I'm aware I'm reviving an old post.
The same thing happened to me with my dad's Nexus 4 a few hours ago.
I tried doing exactly as you described (don't care if our stuff would be deleted or not, I just need the phone to work).

I've ran the ToolKit and got a message that nothing happened and that I should run with "Full Force" in the options.
Ran with Full Force and still nothing happened - got a message that a locked phone can't be written to by the Tool Kit.

Any advice anyone?
Please!

Thank you,
Shalgi

[Wilkin Del Rosario]

This is my fiancee's moms phone and USB debugging is not enabled. She was promoted the update and this is the end result. I've tried reflashing the image files through adb with no end result. I've tried wugs toolkit which is useless because USB debugging is not enabled. I'm at wits end with this phone. Any ideas on what I can do? Also when in recover mode the language is not in english. Did Google botch the update that was sent to her phone?

The Android recovery system <3e> is KRT16S

[Wilkin Del Rosario]

Hi there i got a nexus 4 and it was stuck at the boot animation until i downgrade it from lollipop to android 4.2.2 but when i update it by ota it gets stuck again at the boot animation so i flash it with toolkit and nothing happened it is still stuck at 4.2.2 and o don't like it o want to install android 6 or 7 on it and u tried many times with chroma rom and slim roms and many more but it nevar boots up. Some help please. Also i receive the ota 4.3 and changed the radio from 84 to 48 and it boots up but now. I am stuck again.

[Wilkin Del Rosario]

That happened to you because you did not unlock the boot loader.