Database Users

How to manually push factory image to nexus 7? Help.

So here is my dilemma. I was having problems with my Google apps for whatever reason. Manually updated to 4.2 and still has the same problems. Did a factory reset and the problems went away. Decided I wanted to get rid of root and relock the bootloader since I'm going to give her thus one because I'm upgrading to the 32GB model. Wanted to get rid of the superuser icon in the app drawer mainly. I went to googles site and downloaded the factory images for 4.2. Used it in conjunction with the nexus 7 toolkit. Long story short for whatever reason the process didn't complete. Pretty sure I don't have a factory image at all at this point. I tried to use the nexus 7 toolkit but of course now it won't see my device. My tablet is still unlocked. I'm assuming I'm going to have to manually push the image to the phone. If any body can start me off in the right direction it will be greatly appreciated. Especially if someone were able to provide links to the info I may need. In the mean time I'm looking around on Google. Haven't found anything concrete yet. As a side note if anyone could tell me how to actually turn off the tablet do I can preserve the battery it would be appreciated. I can only get it to show fast boot mode or the Google screen. Can't power down.
Sent from my SCH-I535 using Tapatalk 2

Nexus 7 toolkit?
Fastboot mode?
That's all you need.
Sent from my GT-I9300 using xda premium

Alejandrissimo said:
Nexus 7 toolkit?
Fastboot mode?
That's all you need.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Dunno... after trying to update yesterday, twrp, cwm, stock wasn't having it, had to put stock boot loader back on, everything wiped, not a problem....nandroid backup....toolkit shows it working but nothing, toolkit said everything was there....only unlock and root worked, everything else was borked.
And I had to use Windows for the tool kit. Doh.
Toolkit has been a bane for me, finally got 4.2 using root keeper.
Off-topic.... maybe.
Lesson learnt... definitely.
Motorola Atrix (AOKP JB)
Nexus 7 (Stock+ Root)
Desire HD ~ overheating rebooting.
N900 ~ usb broken off.

Alejandrissimo said:
Nexus 7 toolkit?
Fastboot mode?
That's all you need.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can't use the toolkit bcuz it doesn't see my device. Can't enable USB debugging. Unless there is a way around that?
Sent from my SCH-I535 using Tapatalk 2

4.2.2 install error.

So I got the OTA update for 4.2.2 on my Nexus 7, went to install it. It got about halfway through the updating and error'd out. The device is pretty much stock apart from being rooted. I seem to be the only one with this issue at this early stage of deployment. Any ideas?

GoneTomorrow said:
So I got the OTA update for 4.2.2 on my Nexus 7, went to install it. It got about halfway through the updating and error'd out. The device is pretty much stock apart from being rooted. I seem to be the only one with this issue at this early stage of deployment. Any ideas?
Click to expand...
Click to collapse
What error did you get? I got error 7. Duno why everything is stock.

grieshmp said:
What error did you get? I got error 7. Duno why everything is stock.
Click to expand...
Click to collapse
It just said "Error!" below the android with a red exclamation point. No codes or anything.

Same here.
Sent from my Nexus 7 using xda premium

GoneTomorrow said:
So I got the OTA update for 4.2.2 on my Nexus 7, went to install it. It got about halfway through the updating and error'd out. The device is pretty much stock apart from being rooted. I seem to be the only one with this issue at this early stage of deployment. Any ideas?
Click to expand...
Click to collapse
Same here. Got about halfway through and android went face down with the word ERROR. Rooted/stock

I had the same issue. Mine was related to an error flashing the radio.
So I'm stuck on 4.2.1 and now when I try to check for an update, it says the Device is up-to-date. I'm going to try sideloading it via ADB.

[Q] Updated Nexus 7 to 4.4, stuck with the bouncing circles logo

Hi everyone,
I let my Nexus 7 update via the OTA update. It seemed to go OK but now when I boot I just got the Google logo, then these "bouncing" circles that appear to have taken the place of the original boot animation.
It doesn't seem to boot any further? Can anyone help?

I had this last night when my device updated, I just turned out off and back on and it seemed fine but I did lose root access,
Sent from my HTC One using XDA Premium 4 mobile app

Foxman2k said:
Hi everyone,
I let my Nexus 7 update via the OTA update. It seemed to go OK but now when I boot I just got the Google logo, then these "bouncing" circles that appear to have taken the place of the original boot animation.
It doesn't seem to boot any further? Can anyone help?
Click to expand...
Click to collapse
Do you have twrp or cm installed?
Sent from my Nexus 7 using Tapatalk 4

Foxman2k said:
Hi everyone,
I let my Nexus 7 update via the OTA update. It seemed to go OK but now when I boot I just got the Google logo, then these "bouncing" circles that appear to have taken the place of the original boot animation.
It doesn't seem to boot any further? Can anyone help?
Click to expand...
Click to collapse
I had this problem when I had a custom kernel on the device. If that's the case for you, just fastboot flash the boot image from the Nexus Binaries page.
Otherwise, you might need to adb logcat to see what's going on. For me it wasn't obvious what was up, it just kept getting to a certain spot in the boot and dalvik was crashing. I just figured it out by trying stuff.
If all else fails, you can try flashing the whole system as well, start fresh in case you've made other modifications to the ROM, although OTA's usually fail in those cases.

I do have cwm installed.

Foxman2k said:
I do have cwm installed.
Click to expand...
Click to collapse
I had/have twrp.
I chose the quickest path by using the "nexus root toolkit".
Saved a lot of hassle in the long run
Sent from my Nexus 7 using Tapatalk 4

Foxman2k said:
I do have cwm installed.
Click to expand...
Click to collapse
You need the latest version.
Sent from my Nexus 7 using Tapatalk 4

zard said:
You need the latest version.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I ended up just flashing the stock image file. Kind of wanted to do a stock install anyway.

Stuck in Recovery

Let me start off by saying I apologize if this is posted somewhere already.
Here's my situation. A couple days ago I lgflashed back to stock. All went well. I then rooted and installed TWRP. No issues at all. I didn't take an update, modify the stock ROM or even flash another ROM. Just ran stock rooted. Today, I pick my phone up, go to turn it on and I'm in recovery. No big deal, right? Well I can't get out of TWRP. My backups are still showing, but when I restore it and reboot the phone I'm right back in recovery.
I can't get into download mode either. Not sure what happened and everything was fine earlier in the day. Any thoughts?
Sent from my Nexus 5 using Tapatalk

I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk

droidiac13 said:
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd

dcillusions77 said:
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
Click to expand...
Click to collapse
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.

droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
Tried it but it didn't work :\.....
Mine is stuck in fastboot mode whenever I try to reboot it into recovery what files are missing? Anyone know why whenever I reboot it into recovery it boots fastboot instead? Any help would be much appreciated

If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app

droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk

cccho said:
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
Click to expand...
Click to collapse
Got it up and running by downloading the FreeGee app from play store and installing TWRp that way. I had tried it before just didnt stick the first time

mrm43 said:
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk

droidiac13 said:
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes it might seem that way. Thanks
Sent from my LG-D802 using Tapatalk

OOPS, stuck at fastboot

if I'm posted in the wrong spot please move me
wife's phone started acting weird. it's been on 4.1.2 for a long time. it was rooted but no BL unlocked.
so after trying numerous ways to fix it I decided to try and move to KK. so I defrosted all my bloat and the updater then accepted the first OTA. all worked great. then accepted the second OTA and it installed and was halfway through installing when it rebooted and then went to a more dim version of the same screen. open chested droid with spinning item inside. when it finally finished it rebooted to the Red M and will not go any further.
I can get into fastboot and I have pushed a few commands to see if it works but I cannot get it to allow me to do much else. I have RSD but it seems the device but doesn't show any information. tried to flash something via RSD and it says PHONE RETURNED FAIL
is there a way to get this phone back to some workable form? BL is locked.
===================================================
lots of reading.
it appears that with locked bootloader only signed official MOTO system and boot.img can be loaded thus the fails. downloaded official files
running RSD now and it's gone through 15/17 steps, now loading system for last few minutes.
fingers crossed....

Let us know what happens
Sent from my DROID RAZR M using XDA Premium 4 mobile app

Got it working. Then had to redo it because I flashed 182 not 183. Then that meant I had to delete getvar, got it working and it's perfect EXCEPT WiFi sucks. It doesn't see or stay connected to access points that are best in house. Makes me want to Revert just for that.
Sent from my SCH-I535 using Tapatalk

dyskinesia said:
Got it working. Then had to redo it because I flashed 182 not 183. Then that meant I had to delete getvar, got it working and it's perfect EXCEPT WiFi sucks. It doesn't see or stay connected to access points that are best in house. Makes me want to Revert just for that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It's pretty easy to downgrade back to jb
Sent from my DROID RAZR M using XDA Premium 4 mobile app

Ultimately phone had h/w issues. So swapped for another just like it still on jb. Rooted and unlocked so golden.
Sent from my SM-G900V using Tapatalk