Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
Related
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu
Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?
chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.
chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!
Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.
I have two Nexus 4s. Both were running 4.2.2, rooted, with custom recovery and the Franco Kernel. On a Mac, using the command line, I flashed stock recovery and the stock kernel in preparation for taking the 4.3 OTA.
First, on the newer N4, which has far less thing loaded on it and doesn't have a SIM card...
I tried to install the OTA letting the device/OS do it via the prompt after it was downloaded. But though it tried to start the process, it failed.
So I tried to install the full OS using the command line on a Mac following efrant's instructions in http://forum.xda-developers.com/showthread.php?t=2010312. Fastboot commands have always worked there, but I've never been able to execute adb.
Code:
./fastboot-mac flash system system.img
This is something I've done successfully before. But not this time. I flashed recovery and the radio, but when I tried to flash the system, I got an error message (usb_write failed with status e00002be or something about a partition not existing). So I took the phone to a Windows machine and used Wugfresh's tool. I couldn't successfully set up the drivers, but fastboot worked. So I did the return to stock and root thing. And it worked, getting me back to 4.2.2 in an out of the box state. I ran the OTA right away and easily got to 4.3.
Then, since I was already on the Windows machine, I used Wug's tool to try and root. No success. I can't seem to install custom recovery, either temporarily or permanently. I don't get an error message, but I can't boot into it, either. I just get the dreaded lying down Android icon with the red exclamation point.
Any ideas why I couldn't install system.img on the Mac command line? And why can't I get custom recovery? And what I can do to get it right?
Now, the older N4, which is my main phone. I have a current Titanium Backup, but not a Nandroid, at least not a current one. I haven't tried, yet, to update it to 4.3. But as mentioned, I did try to go back to the stock kernel and recovery in preparation. The problem there is that I also get the lying down Android instead of stock recovery and even worse, occasionally slow and laggy performance, which I hadn't had to begin with. Otherwise, it's 4.2.2 with that radio and kernel.
Any thoughts or help on this would be much appreciated.
I'm still hoping someone can offer me some sort of insight on this.
Dev Options and USB Debugging have been enabled on these N4s. I also want to say that I'm not trying to do anything I haven't done a bunch of times before both with NRT and from the command line with N4s and N7s. But I'm stuck in ways I haven't been before and I don't understand why or what to do about it.
I dont know exactly what you mean but the android laying down is the stock recovery.
Sent from my Nexus 4 using xda app-developers app
Hmm. I thought there was another, simple, volume key driven recovery interface from prior experience with this. I'm probably confusing a non-touch version of CM Recovery. Thanks for clarifying.
I finally got drivers working on the Windows 8 machine (the Universal Naked Driver that I found here at XDA). I was able to use the command line through NRT to get custom recovery onto the first of the N4s I described. I couldn't do that on the Mac via the command line or through the NRT interface before that. It just didn't work. Once that was in place, rerooting was easy. But it was a long road to get there with obstacles I hadn't encountered on earlier rooting and updating adventures.
I haven't tried to update my daily driver, yet. I may wait until things stabilize more with 4.3 and the various ROMs. Since I may have little choice other than to start over, I might do something other than the stock ROM.
One thing I've discovered is that running a more recent version of fastboot and adb helps. I can do some things on the Mac from the command line that I couldn't do with versions a few month older. (April, 2012 vs. November, 2012).
I still can't successfully run the OTA on one of my N4s, though. Maybe I need to unroot first, though I never have before.
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.
My OTA update showed up on my old 2012 Nexus 7, I told it to install, and it just sat there bouncing color disks forever after the first reboot. Perhaps something about being rooted and and having TWRP is what screwed it up.
Anyway, I was able to use fastboot to flash the stock kitkat images, so it is back now and even running kitkat. I think I'll leave it alone till I have some reason to root it again.
Same Problem
Claghorn said:
My OTA update showed up on my old 2012 Nexus 7, I told it to install, and it just sat there bouncing color disks forever after the first reboot. Perhaps something about being rooted and and having TWRP is what screwed it up.
Anyway, I was able to use fastboot to flash the stock kitkat images, so it is back now and even running kitkat. I think I'll leave it alone till I have some reason to root it again.
Click to expand...
Click to collapse
I have the same problem, but i can't fix it. Should i flash the KRT16S from JWR66Y zip to make thing right? Thank you for your help
I basically followed the instructions in here:
http://forum.xda-developers.com/showthread.php?t=1907796
But since it couldn't boot to use adb to get to bootloader, I powered it off and then held down power and vol-down to get to the bootloader so I could talk fastboot. Instead of the old image mentioned in that post, I searched for the latest kitkat image for my wifi 2012 Nexus 7 and used it.
Claghorn said:
I basically followed the instructions in here:
http://forum.xda-developers.com/showthread.php?t=1907796
But since it couldn't boot to use adb to get to bootloader, I powered it off and then held down power and vol-down to get to the bootloader so I could talk fastboot. Instead of the old image mentioned in that post, I searched for the latest kitkat image for my wifi 2012 Nexus 7 and used it.
Click to expand...
Click to collapse
Thank you very much! So i have to do the same. But isn't it a problem that i have KRT16S?Do I have to download the KRT16S from JWR66Y? Sorry for asking that much, i'm a newbie.
Claghorn said:
I think I'll leave it alone till I have some reason to root it again.
Click to expand...
Click to collapse
Good move. These devices seem to have a number of issues once rooted. I was rooted, bricked, RMA number, & now stock. Don't see much benefit to rooting, so plan not to re-root for now.
I've already searched the forums and found no thread with the solution to my problem. People have had a very similar issue, but not exactly mine, so prior solutions I've found seem to not solve it:
I have a Nexus 7 (2012 WiFi).
It is rooted, clockwork mod.
I have a mac (that seems to not want to detect my Nexus 7 anymore).
I got the update for KitKat, like an idiot, I jumped at it, let it update overnight, and now I'm stuck in the 4 circles loading screen. Since I have CWM, I'm stuck in the CWM recovery mode when I try to do a factory reset. The factory reset does nothing, I was hoping to get back into the stock recovery mode, but have no idea how to get there (nor do I think it's possible).
Keep in mind, I'm semi-tech savvy, but when it comes to "flashing blah blah" I have no idea what the hell anyone is talking about if it's not broken down step by step in layman's terms. If you say, "open the terminal, and type exactly this", then I'm golden, but otherwise, I'm just googling tab after tab to figure out what it means.
As stated above, my mac does not want to even acknowledge the existence of my tablet either with ADK or Android File Transfer. Is there maybe a way I can put a zip on an sd and somehow use an SD reader to mini-usb adapter to sideload a fix? Anyone have any other ideas of how I can fix this issue? I'm not enjoying my Nexus 7 as a paper weight.
Thanks.
Phillustrate said:
I've already searched the forums and found no thread with the solution to my problem. People have had a very similar issue, but not exactly mine, so prior solutions I've found seem to not solve it:
I have a Nexus 7 (2012 WiFi).
It is rooted, clockwork mod.
I have a mac (that seems to not want to detect my Nexus 7 anymore).
I got the update for KitKat, like an idiot, I jumped at it, let it update overnight, and now I'm stuck in the 4 circles loading screen. Since I have CWM, I'm stuck in the CWM recovery mode when I try to do a factory reset. The factory reset does nothing, I was hoping to get back into the stock recovery mode, but have no idea how to get there (nor do I think it's possible).
Keep in mind, I'm semi-tech savvy, but when it comes to "flashing blah blah" I have no idea what the hell anyone is talking about if it's not broken down step by step in layman's terms. If you say, "open the terminal, and type exactly this", then I'm golden, but otherwise, I'm just googling tab after tab to figure out what it means.
As stated above, my mac does not want to even acknowledge the existence of my tablet either with ADK or Android File Transfer. Is there maybe a way I can put a zip on an sd and somehow use an SD reader to mini-usb adapter to sideload a fix? Anyone have any other ideas of how I can fix this issue? I'm not enjoying my Nexus 7 as a paper weight.
Thanks.
Click to expand...
Click to collapse
If your recovery is broken you need to boot into the Bootloader (Hold power until you see the Google logo, then press Vol down.) and then use fastboot to flash a good image from there. You can then do a factory reset etc. You could also do a factory reset from fastboot directly, but you'll want to fix your broken recovery at some point.
Or.. Possibly the better method, since your device is in an unknown state.
https://developers.google.com/android/nexus/images
Get the image FOR YOUR EXACT DEVICE. Don't get the LTE version for the WIFI, etc. Then just run the batch file. It will reset everything (including the internal SD card) and reflash the stock OS. This will leave your bootloader unlocked, with a stock ROM, kernel, recovery. You can flash the custom recovery and supersu.zip if you wish to re-root it.
khaytsus said:
If your recovery is broken you need to boot into the Bootloader (Hold power until you see the Google logo, then press Vol down.) and then use fastboot to flash a good image from there. You can then do a factory reset etc. You could also do a factory reset from fastboot directly, but you'll want to fix your broken recovery at some point.
Or.. Possibly the better method, since your device is in an unknown state.
Get the image FOR YOUR EXACT DEVICE. Don't get the LTE version for the WIFI, etc. Then just run the batch file. It will reset everything (including the internal SD card) and reflash the stock OS. This will leave your bootloader unlocked, with a stock ROM, kernel, recovery. You can flash the custom recovery and supersu.zip if you wish to re-root it.
Click to expand...
Click to collapse
Thank you so much for the response. I apologize for my ignorance: My secondary issue is that my computer does not even recognize when I plug in my Nexus 7. It did previously before my tinkering with it, and before the KitKat update, but now it's like I'm plugging in a brick. I did get to the point of downloading the proper factory image, but it does me no good since I can't load it on there. I don't know how to flash the drive when my computer can't even load anything on to it.
Is it possible to load it through a micro-usb to SD reader adapter? I'm thinking I can load the factory image on to the SD card, and then "sideload" the factory image from there.
To add information so I maybe can get help:
I think the reason my mac doesn't detect it is because I can't get the device into MTP mode so that my mac will see it as a storage device.
I would have to be able to get into the Android OS settings to actually be able to change this setting. I can get into bootload mode, and cwm recovery, but nothing else. I just need some way to get this factory image file onto the Nexus 7, but can't figure out how since this connection does nothing.
Fastboot and recovery do not require any settings configured in the OS. They are independent of the OS. You need to update your sdk on your Mac for the device to be seen in terminal
Sent from my Nexus 5
Pirateghost said:
Fastboot and recovery do not require any settings configured in the OS. They are independent of the OS. You need to update your sdk on your Mac for the device to be seen in terminal
Sent from my Nexus 5
Click to expand...
Click to collapse
It is up to date. It is not recognized either in sdk, android file transfer, or just in finder as a device at all.
You should never see it in a file browser of any sort while in recovery or fastboot mode. Use adb in recovery and fastboot commands in fastboot
Sent from my Nexus 5
I fixed it and recovered it back to 4.2.2, but I will take it!!! NOW I'm going to update to KitKat.
Unfortunately, I can't post links right now since I'm such a new member, but to anyone that has this same issue, I used this guide to get me through it:
Google "nexus 7 factory image restore" written by 2DefMouse. You should find it there.
Also, there's a youtube video counterpart, Google/Youtube this: "How to return to Stock / Updating with Factory Images / Unbrick your Nexus 7"
I'm sure this is fairly common and usual, but for some reason I couldn't figure it out, but to any morons like me, I recommend the guides I followed.
As a tip, for mac, when you type terminal commands, always put the ./ before every "fastboot"... so "./fastboot"
Also, in the guide, it says to type "./fastboot-mac"... I left out the "-mac".
Thanks everyone.