[Q] Nexus 7 2012 boot loop with NO USB Debugging - Nexus 7 Q&A, Help & Troubleshooting

Hi,
I have a Nexus 7 2012 with build number JWR66Y and is complete stock.
- No rooting / unlocking done.
- USB debugging is NOT enabled.
Since last 2 days, it's stuck in a boot loop, it simply does not go beyond the screen that shows up a flashing 'x' symbol.
I have my pictures and important documents stored in there and would like to take a backup of the same before doing a factory reset.
What options do I have with me ?
Is it possible to flash a custom recovery tool " twrp2" and take backup of my data ?
If YES I would request the experience guy's to me help here.
Thanks

Issue resolved
crossdomain said:
Hi,
I have a Nexus 7 2012 with build number JWR66Y and is complete stock.
- No rooting / unlocking done.
- USB debugging is NOT enabled.
Since last 2 days, it's stuck in a boot loop, it simply does not go beyond the screen that shows up a flashing 'x' symbol.
I have my pictures and important documents stored in there and would like to take a backup of the same before doing a factory reset.
What options do I have with me ?
Is it possible to flash a custom recovery tool " twrp2" and take backup of my data ?
If YES I would request the experience guy's to me help here.
Thanks
Click to expand...
Click to collapse
I have fixed my Nexus 7 by running 'flash-all.bat' file. This .bat file is part of the archive which was downloaded from google to flash my Nexus 7 3G with the latest version of android 4.3 JWR66Y.
Note : I lost my data after i executed 'flash-all.bat'
Thanks

Nexus 7 stuck in BootLoop, USB Debugging NOT ENABLED
crossdomain said:
I have fixed my Nexus 7 by running 'flash-all.bat' file. This .bat file is part of the archive which was downloaded from google to flash my Nexus 7 3G with the latest version of android 4.3 JWR66Y.
Note : I lost my data after i executed 'flash-all.bat'
Thanks
Click to expand...
Click to collapse
Hi! Can I ask for help? I've the same issue, Nexus 7 (older version) stuck in bootloop. I have NOT been able to ENABLE USB DEBUGGING when it was still on.
I'd just like to know the link to the file you have suggested, the flash-all.bat file? Maybe that'll work for my Nexus.
Thanks a lot.

bashfulburito said:
Hi! Can I ask for help? I've the same issue, Nexus 7 (older version) stuck in bootloop. I have NOT been able to ENABLE USB DEBUGGING when it was still on.
I'd just like to know the link to the file you have suggested, the flash-all.bat file? Maybe that'll work for my Nexus.
Thanks a lot.
Click to expand...
Click to collapse
Hi,
You would need to download android factory image from google specific to your Nexus 7 model.
It will be a zip file which you have to extract, it will contain the file 'flash-all.bat' as mentioned in previous posts.
Thanks

Related

Do not flash stock with Nexus 7 Toolkit!

Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Well.. I've never had any problems fastboot flashing 4.2.2 myself.
------
I would suggest you don't use toolkits...at all... period!
Learn FASTBOOT...
...and be extremely cautious when it comes to FLASHING the BOOTLOADER...
A corrupted BOOTLOADER flash will 'hardbrick' the device in a heartbeat - make sure you have a secure USB connection...
Test along these lines..
Code:
fastboot flash boot <a boot.img>
or
fastboot flash recovery <a recovery.img>
If these go across, the new BOOTLOADER probably will.
The worst that's going to happen (with these two) is a 'softbrick' - a headache at worst.
A headache you can get over...
Hardbrick is death - and nobody get's over that.
Rgrds,
Ged.
I know this. Thanks.
I flash 4.2.2 with fastboot. Because nexus 7 toolkit is buggy, when i upgrade android from 4.2.1 to 4.2.2 with toolkit i got brick. Just read my 1 post
I give link to this thread creator of toolkit, maybe he fix this bug. Maybe no, anyway, start from this day i will flash firmwares ONLY with fastboot.
Good decision, i never used this kind of tool for flashing something.
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
I can't give you list of "errors" etc, just because i don't wanna again "brick" my nexus :/
What i did:
1. I enter in toolkit
2. Choose version (4.2.1 or 4.2.2, don't matter, i got "brick" on both versions)
3. Choose "download and flash stock"
4. Download stock from toolkit, or from google developers site
5. Flash downloaded firmware
After this i got "Booting failed".
Then i flash stock 4.2.2 with FastBoot - and all is ok. But when i again try to flash stock 4.2.2 with toolkit - im again got Booting failed.
That's all.
Ofcourse i have last ver. of toolkit.
Current ToolKit [V4.3.7], Latest Available [V4.3.7]
Current Mods Section [V2.5.0], Latest Available [V2.5.0]
Click to expand...
Click to collapse
I'm getting this samething to happen to me except I can't even get manual fast boot to work either. Both are giving errors about no such device found or timeouts.
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
walliester said:
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
Click to expand...
Click to collapse
Hicksy994 said:
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you use toolkit for flashing stock 4.2.2?
Never, ever had a problem with Wug's toolkit, that thing is written brilliantly and it has saved my ass more times than I can care to count.
I was totally new to android development before I tried the nexus toolkit. Now I have a rooted n7 and prime, though I gotta say, rooting the prime took from me more time. I would suggest that you run the test-like driver check before attempting the one click magic.
Sent from my Nexus 7 using xda premium
The sequel of flashes you made is confusing for me but you should flash stock no matter the version 4.1 or 4.2 cuz you can get to latest by OTA updater.
Sent from my Nexus 7 using Tapatalk 2
In last update:
+Added MD5 hash checks before flashing for ALL stock images to avoid bad flashes
+Added selection to flash Radio images in the Flash Image section (gsm models)
Good, any1 can test?
No problem for me, I used last tookit to return stock rom 4.2.2 from cyanogenmod 10.0.1 with franco r65kernel.
I desired to return factory rom, because of low charging issue and fast battery drain.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
I HAVE flashed stock using the toolkit multiple but no problem for me.....
More, I wanna tell you guys that battery so slow in charging issue is solved after flashed stockrom 4.2.2 from google server. B4 with Cm 10.1 and franco r65, I have to charge it more than 10 hours to full, but now only 5 and half hour with Stockrom 4.2.2 . Problem is relevant to custom rom and modded kernel as I think
hassam_tariq2003 said:
I HAVE flashed stock using the toolkit multiple but no problem for me.....
Click to expand...
Click to collapse
Nexus 7 Turn On Problem
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
saqibyk said:
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
Click to expand...
Click to collapse
I'm in the same boat exactly the same thing. i hope there is a fix for this.
ChrisHRocks said:
I'm in the same boat exactly the same thing. i hope there is a fix for this.
Click to expand...
Click to collapse
You should flash the stock bootloader, when connected, find this amongst the advanced utilities, and if the drivers are not working then use the driver diagnostic tool. You will not lose your apps doing this.
One other thing is that once your bootloader is returned to stock, you can use the Google Framework cache and data clearance mthod, described in other posts, to force the 4.3 Update. This really does work, and means that your apps and data remain intact.

[SOLVED] Restore a Nexus 7 with no OS (and trouble with adb) driver

Hi!
I've messed up with my tablet and I've ended up with a Nexus 7 with TWRP 2.6 but no OS installed.
I did some research but didn't find a solution to get 4.3 working in this case.
Any help?
Three things you'll need to restore your Nexus 7.
-Fastboot and ADB (Android SDK, platform-tools)
-Nexus 7 4.3 factory image (here)
-USB cable
First, you need to download the factory image. After that, you need to extract the zip into /platform-tools in your SDK.
Now you see a file named flash-all.bat, before you run that you need to connect your Nexus 7 to the computer. If you have your Nexus 7 plugged in, and the PC recognizes it, you can run flash-all.bat. Now you should see a CMD window popping up, with some commands. After the process is finished you've got a brand new Nexus 7. :good:
See the sticky that says flashing a factory image with fastboot/returning to stock. It is a couple from the top and walks you through fixing it.
Sent from my Nexus 4 using Tapatalk 4
Thanks, but stuck in the stage 7 :
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
Click to expand...
Click to collapse
However my PC recognize an android device but can't install the driver.
The Android Composite ADB Interface Driver 8.0.0.0 driver from SDK is for when in bootloader and booted into ROM. Naked Driver 0.72 is needed for when in recovery or else the computer would show "Nexus 7" under Unknown Devices in the Device Manager. With Naked Driver 0.72 installed, ADB can be used in recovery to copy a custom ROM zip to the internal storage then flash it.
Solution
Issue solved by the Nexus 7 Toolkit.
For people in the same situation:
1) Install the adb drive with the toolkit.
2) Flash a stock image with the toolkit.
You'll end up with a restored Nexus 7
Thanks for the help!
Lost OS in my Nexus 7
Hi there,
I accidentally wiped out my Nexus 7 (2012) and lost the OS in there of course. Cannot boot up from Nexus. Followed the steps you listed but I don't see the "flash-all.bat" in the platform-tool folder.
Also, I have tried other ways to push the img to Nexus 7 thru my laptop or a OTG cable with USB drive but seemed the Nexus 7 cannot be found or linked to any of the external devices.
As for the img, what kind of format should be extracted into the platform-tool folder? The original download is .tar and should I rename the extracted file to .img?
Need help...please. Thanks!!!
I assume you downloaded the proper factory image (nakasi from wi-fi, nakasig for 3g) from here: https://developers.google.com/android/nexus/images
It's a tgz file, but you can open and extract it with winrar (maybe others work too).
Boot your device to bootloader mode and connect it to your computer.
no luck...
Hi Erovia,
Thanks for replying. I am sure that I downloaded from that google site and I had the rev from 4.1.x ~ 4.4.2 and all of them are in .tar format. I used 7z to unzip and they got no extension after unzipping and all came out 1 file only. Does Flash-all locate in the image from google after unzipping?
I think I am having 2 problems now before I can move forward.
1.. Don't have the right image with .tgz as you described.
2.. Can never get the flash-all file.
Thanks.
1) All images are in tgz on that official site.
2) I can't help you with 7zip, try WinRar, it's very staightforward with it.
<No OS Issue Resolved>
Issue resolved and wanted to share lesson leant here:
For some reason, all the image I downloaded from Google developer site were in TAR format. I had a co-work with MacBook Pro and another Dell with Unix installed, when he downloaded the images, all of them came with TGZ and were able to unzip to a folder with files in it.
I came back and manually changed the extension file name from .tar to .tgz then it worked. I don't know why all windows laptops I tried had this same problem BUT fortunately I got it figured out.
I also ran into issues using SDK tool. after I click on Flash-all.bat, the cmd window popped up but it got stuck after few seconds.
I tried alternate method by locating the files unzipped from the image to the folder where I saved the adb, fastboot tools. Then I went to windows search type in CMD for DOS and went to the folder by using the DOS commend "cd" change directory. to the folder. Then typed in Flash-all.bat and it worked!!! Unbelievable I successfully installed the 4.4.2 to the device and rooting it with the "Nexus Root Toolkit" now.....
I think it just does not work too well with Windows for both image downloading as well as pushing the image to device.
Again, thanks for the help.
Help!
hcy97 said:
Issue resolved and wanted to share lesson leant here:
For some reason, all the image I downloaded from Google developer site were in TAR format. I had a co-work with MacBook Pro and another Dell with Unix installed, when he downloaded the images, all of them came with TGZ and were able to unzip to a folder with files in it.
I came back and manually changed the extension file name from .tar to .tgz then it worked. I don't know why all windows laptops I tried had this same problem BUT fortunately I got it figured out.
I also ran into issues using SDK tool. after I click on Flash-all.bat, the cmd window popped up but it got stuck after few seconds.
I tried alternate method by locating the files unzipped from the image to the folder where I saved the adb, fastboot tools. Then I went to windows search type in CMD for DOS and went to the folder by using the DOS commend "cd" change directory. to the folder. Then typed in Flash-all.bat and it worked!!! Unbelievable I successfully installed the 4.4.2 to the device and rooting it with the "Nexus Root Toolkit" now.....
I think it just does not work too well with Windows for both image downloading as well as pushing the image to device.
Again, thanks for the help.
Click to expand...
Click to collapse
Hi!
I just had a question. I have deleted my OS on Nexus 7 (2012) except that the tablet was also encrypted. Do the steps to flash the stock image still remain the same or do i need to do something differently? Sorry if this is a trivial question, I am a noob and totally regretting all the **** I have done to my tab. Would appreciate it if you could help out.
Thanks
Worked perfectly...thanks buddy! Just need to root now!
AFAIK you can proceed as usual.
hi guys please i lost my OS of my new nexus 7 wifi
when i was downgrading my new nexus 7 2013 wifi model i didnt know what i did but it is stuck in google and down of that some lock symbol but it not starting at all i dont know what happen please help me guys i think my OS has crashed help please guyzzzzzz ............:crying:
maheshchinna313 said:
when i was downgrading my new nexus 7 2013 wifi model i didnt know what i did but it is stuck in google and down of that some lock symbol but it not starting at all i dont know what happen please help me guys i think my OS has crashed help please guyzzzzzz ............:crying:
Click to expand...
Click to collapse
poor friend... I have the same issue, After the starting graphics, I see the lock screen for a second and it reboots. Again. And again, and again...
Let's try to fix it together. Stay in touch.
I'm really happy to say that I managed it with the Android Toolkit by Skipsoft. Although I did the same process many times (1. unlock the bootloader & 2. flash a stock image), it worked the 6th or 7th time.. Don't know why. Maybe because I reinstalled (and repaired) the drivers. Also, I was unable to flash the 4.4.2, so I did it with thw 4.1.2
Good luck dude!
How to Restore your Device
Anmar21 said:
Hi!
I've messed up with my tablet and I've ended up with a Nexus 7 with TWRP 2.6 but no OS installed. I'd like to put 4.3 Back on it Again!
Please help me!
Click to expand...
Click to collapse
To do this steps you don't need to be a Professional.
Simply read it all through and try to Understand it.
You need 3 Things for this WugFix Guide to Work.
1.Download WugFresh'S Nexus 7 Root Toolkit from wwW.WugFresh.Com
2.MicroUSB-Cable that fits in to your Computer and your Tablet.
3.The Android 4.3 Factory Image File for your Nexus 7 (2012?) with Build Number „JWR66N"; „JWR66V" or „JVR66Y" or maybe JWR66L.
1.Install the Nexus Root Toolkit (I've got 1.8.4 but right now, the Newest program Version is 1.8.6.)
2.In the Window "Your model type:" you choose „Auto Detect Device + Buidl"
2.1.If that does not work, then choose your Options Manually.
NASAKI-GROUPER Android 4.3.0 has a Build of 6 Letters and/or Numbers that starts with JWR66 and ends with a „V";„N"„L" or „Y"."
Now it depends on WHAT DO YOU ACTUALLY WANT...
BEFORE DOING ANYTHING, if you want to Backup first, read THIS [http://forum.xda-developers.com/showthread.php?t=1766475&page=102]
If you wanna get the Nexus 7 back as it was like after Purechas(eI)ing, then Choose
„Soft-Bricked or Bootloop" in the „Back to Stock"-Menu on the Main Window with the title „Nexus Root Tooklit v.[Version Number.]"
Then click on the „Flash to-Stock + Unroot" --Button and then Open (Launch) the Image File
You can DOWNlOAD THE IMAGE FILE HERE: „htt ps : / / developers.google.com/android/nexus/images?hl=de&Hnh=1"
The File is Probably Saved here: „%USERPROFILE%\Downloads\FIREFOX DOWNLOADS\" or without „FireFox Downloads" the Path is „%userprofile%\DownLoAdS\".
There is no difference betwéén a or A, DoWnlOaDs or Downloads, but there is Actually a Diff. between "é" and the Nomral „e".
After the Process Progress is done, try to boot up your Nexus.
Hmmmmm..... let's see!
If you are still not OK, then try the Option Relock>OEM LOCK in the Main Window Panel of the Program.
Click to expand...
Click to collapse
I hope i could help you.
(I) Wish you a Nice day
and have a Nice day with your Nexus 7!
Hopefully i've been able to Hélp.
♥HA❤NN❤AH♥
My Recommendation for any case: IsoBuster, made ONLY BY Peter van Hoove!
Click to expand...
Click to collapse
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Nexus 7 os wiped by mistake
Hello guys
I have a similar problem here. I wiped out Nexus 7 2012 (mobile) OS by mistake and now all it does is switch on and display "Google" and an open padlock below. i tried my Nexus Root Toolkit to stock recovery, actually i tried even recovery but ADB connectivity cannot be established (tried all usb ports).
Currently the tablet cannot even switch off, switches back on on its own...in simple terms, my tablet is dead, its like a computer without OS. My computer recognize it though but with the exclamation mark in the device manager.
please help

[Q] Nexus 4 Bootloop Troubles!!

There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk
Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back
This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.

Nexus 7 bricked ??? please help

Please help me... I have a Nexus 7 wifi edition (old version).
I installed wugfresh toolkit and tried to install factory 4.4
After about 15 minutes nothing was happening so I tried to reboot my Nexus 7. Now it is stuck in bootloader mode. It does not want to start. I tried reflashing stock again but it says USB debugging needs to be enabled, but I can't boot my device... how do I revive it please.. thank you
My device was already bootloader unlocked, and running 4.2 grouper JDQ39
Thank you
nm8 said:
Please help me... I have a Nexus 7 wifi edition (old version).
I installed wugfresh toolkit and tried to install factory 4.4
After about 15 minutes nothing was happening so I tried to reboot my Nexus 7. Now it is stuck in bootloader mode. It does not want to start. I tried reflashing stock again but it says USB debugging needs to be enabled, but I can't boot my device... how do I revive it please.. thank you
My device was already bootloader unlocked, and running 4.2 grouper JDQ39
Thank you
Click to expand...
Click to collapse
Did you tried flash stock+Unroot (Device is on/Normal ) mode ?
KrilanPL said:
Did you tried flash stock+Unroot (Device is on/Normal ) mode ?
Click to expand...
Click to collapse
yes, but it does not work because the software says it needs USB debugging enabled... but I can't boot to android
Hi try this i watched in you tube. Mine was stuck in bootlop after ota to 4.4. I hope this will help you and sorry if i am wrong about it. http://m.youtube.com/results?q=return to stock nexus 7&sm=3
Sent from my MB855 using xda premium
deny_kei said:
Hi try this i watched in you tube. Mine was stuck in bootlop after ota to 4.4. I hope this will help you and sorry if i am wrong about it. http://m.youtube.com/results?q=return to stock nexus 7&sm=3
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Hi
thanks for the link, good informations there, but I already solved the problem by using MSKIP's software.
Thanks for helping though...
nm8 said:
Please help me... I have a Nexus 7 wifi edition (old version).
I installed wugfresh toolkit and tried to install factory 4.4
After about 15 minutes nothing was happening so I tried to reboot my Nexus 7. Now it is stuck in bootloader mode. It does not want to start. I tried reflashing stock again but it says USB debugging needs to be enabled, but I can't boot my device... how do I revive it please.. thank you
My device was already bootloader unlocked, and running 4.2 grouper JDQ39
Thank you
Click to expand...
Click to collapse
Hi I recently bricked my nexus 7 too and unbricked it myself. there aren't a lot of people willing to help here as I know, and I know I can help you. First thing first, there is noway you can brick your nexus 7, no matter what you have done, so just clam down.
to unbrick your nexus 7, there is what I suggest you to try>
1, download fastboot, adb. make sure they are the newest version.
2, download recovery-clockwork-touch-6.0.4.3-grouper. this is a recovery img that you install into your nexus 7
3, get Google android USB driver!! uninstall every before you install this!!
4, put your neuxs 7 into boot loader mode by holding about 3 buttons.
5, connect your nexus 7 to your PC
6, If you are a windows using, using command prompt "fastboot.exe devices"
7, something should come up. then you are in the right track.
8, type fastboot.exe flash recovery recovery-clockwork-touch-6.0.4.3-grouper
9, you should get a message saying everything is install correctly.
10, using vol down to go the recovery mode on your device. The CWM should be installed!!!
11, Download any android ROM for nexus 7, and simply install it using CWM!!
12, Adb doesn't work on me because I can't get into USB debug mode. You have to use an OTG USB cable. Copy the ROM to an USB driver and connect that USB to your nexus using this OTG USB cable.
13, install!!! done!!!
nm8 said:
Hi
thanks for the link, good informations there, but I already solved the problem by using MSKIP's software.
Thanks for helping though...
Click to expand...
Click to collapse
Could you elaborate a little more on what step you picked from the main menu of that software? I'm not having any luck getting my Nexus fixed.
Posted my thread for help here http://forum.xda-developers.com/showthread.php?t=2560975
Guess I will try megapig's suggestions next. I've tried so many procedures and none of them are working.
EntityPacket said:
Could you elaborate a little more on what step you picked from the main menu of that software? I'm not having any luck getting my Nexus fixed.
Posted my thread for help here http://forum.xda-developers.com/showthread.php?t=2560975
Guess I will try megapig's suggestions next. I've tried so many procedures and none of them are working.
Click to expand...
Click to collapse
I just uninstalled all the crap that the other software installed, then on MSKIP's software, I chose no. 1, then after that, I installed stock, can't remember the number but it is there...
Thanks, I did manage to get it fixed last night. Posted update in my thread.
Whew

Help! Boot loop

Hi, I have a fully stock nexus 7 1st gen which is stuck on a boot loop, I am able to get it into fast boot mode where I've tried the wipe data/factory reset and wipe cache partition but it just freezes. I've searched around for solutions I've even tried flashing the stock images with wugfresh toolkit with no luck, most fixes it seems need the debugging enabled on the device which I can't do because I can't get into the menu. If anyone can help me it would be fantastic
mikebolton said:
Hi, I have a fully stock nexus 7 1st gen which is stuck on a boot loop, I am able to get it into fast boot mode where I've tried the wipe data/factory reset and wipe cache partition but it just freezes. I've searched around for solutions I've even tried flashing the stock images with wugfresh toolkit with no luck, most fixes it seems need the debugging enabled on the device which I can't do because I can't get into the menu. If anyone can help me it would be fantastic
Click to expand...
Click to collapse
Hey Mike, it sounds like you have no other option than to restore back to factory using the official Google Factory Images. That will completely wipe your N7, SDCard and all
Go ahead and download the nakasi image of your choice from Google: https://developers.google.com/android/nexus/images#nakasi... make sure that you don't accidentally get the nakasig firmware as it is for the Tilapia 3G model.
Extract it with 7-zip or WinRar (or whatever) and with your tablet plugged in and in Fastboot Mode, (you will also need the fastboot/ADB drivers installed) run the flash-all.bat batch file. (You may need to enable the Windows function "Show File Extensions" to see the .bat part after the file name. There is also a flash-all.sh in the folder as well but that one is for Linux users so you wont be able to use it unless you're on Linux.
Good Luck! :good:
Hi Tim, Thanks for replying,
I'm not too worried about losing data I'm just desperate to get it working again.
I have downloaded the flash image but where would I find the download for the fast boot drivers?
mikebolton said:
Hi Tim, Thanks for replying,
I'm not too worried about losing data I'm just desperate to get it working again.
I have downloaded the flash image but where would I find the download for the fast boot drivers?
Click to expand...
Click to collapse
They should be included in the Wugfresh Toolkit that you downloaded. Just follow the steps to install the device drivers and I believe that the Fastboot drivers installs with it.
How weird, I am fixing my Dad's tonight, exact same issue! Have had it a week or so but just found time to do it now... I will do with you if you like. I already downloaded the wugfresh NRT and worked through the steps, obviously missing out the debug mode parts. Currently downloading the nakasi kot49h which is taking a while, so came on here to see what to do if this fails and saw your post!
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:29 PM ---------- Previous post was at 11:24 PM ----------
If you download the nexus root kit v1.8.2 from www.wugfresh.com follow the steps on there to uninstall various drivers, then click the initial setup - full driver installation to get the correct driver for your device.
Sent from my Nexus 5 using xda app-developers app
In the wug toolkit when installing drivers step by step guide to configure MTP drivers you need to disable USB debugging then disable MTP mode then re enable debugging all of which I can't do because I can't get into the menu to do anything
Hi Tom,
I can't seem to figure it out ive tried the wug toolkit a number of time with no results it seems most fixes need you to be able to enable debugging, if you find out how to do it let me know and if I by some miracle get it working I'll let you know
I have just run the flash stock and unroot option on wugfresh in the log everything has been erased but when it has tried to send bootloader is says failed<remote: bootloader is locked.>
Yes, you are up to where I got to. I fixed mine last night eventually. Next I tried a risky extra step which I won't tell as I don't think it did anything, then directly on the left of Flash and unroot there is a button to unlock bootloader. Run that, it gave me an error message but appeared to do the trick because the next time I ran flash + unroot it worked finally. Let us know how you get on!
Sent from my Nexus 5 using xda app-developers app
No it still isn't working everything I try doesn't work it all comes down to the locked bootloader and no matter what I do I can't find a solution to open it
Has anyone come across the same problem and found a solution?
mikebolton said:
No it still isn't working everything I try doesn't work it all comes down to the locked bootloader and no matter what I do I can't find a solution to open it
Has anyone come across the same problem and found a solution?
Click to expand...
Click to collapse
Open a command prompt in the folder with Fastboot. Type in "fastboot oem unlock" without quotes. That will unlock the bootloader and also you to flash factory image.
Doesn't work I've tried it before it just comes up with unlock bootloader screen where you have a choice yes (may void warranty) or no I click yes then I am directed back to fastboot mode with a message at the top left corner saying unlocking now....... but nothing ever happens, I restart device and I'm back to where I started.
Someone must know how to fix this

Categories

Resources