[Q] Can't Update To 4.4 :( - Nexus 7 Q&A, Help & Troubleshooting

Hey guys,
So I tried looking around in the forum but can't seem to get an understandable answer.
I have a Nexus 7 (2012). I was running CM 10.2, but wanted to move up to KitKat. I downloaded the new ROM, and did the wipe and everything. But none of the new ROMs will install on my Nexus 7. Every time, it will start to install, then it will say "status 7, installation aborted" and that little android guy in the background will be lying down with a red triangle over him.
I have tried several different ROMs, but they all seem to have the same effect.
I THOUGHT about ADB sideloading, but my computer does not recognize the device. So there's that.
.....Any ideas? Please?

Update your recovery
Sent from my Nexus 5

Kangaji said:
Hey guys,
So I tried looking around in the forum but can't seem to get an understandable answer.
I have a Nexus 7 (2012). I was running CM 10.2, but wanted to move up to KitKat. I downloaded the new ROM, and did the wipe and everything. But none of the new ROMs will install on my Nexus 7. Every time, it will start to install, then it will say "status 7, installation aborted" and that little android guy in the background will be lying down with a red triangle over him.
I have tried several different ROMs, but they all seem to have the same effect.
I THOUGHT about ADB sideloading, but my computer does not recognize the device. So there's that.
.....Any ideas? Please?
Click to expand...
Click to collapse
make sure you are on the latest TWRP recovery and if it still gives you problems, make sure your using the latest bootloader, I have heard reports of an older bootloader causing problems with some rom installs....

THANK YOU THANK YOU
It works PERFECT now, looks like. Thanks again!!

THANK YOU THANK YOU
It works PERFECT now, looks like. Thanks again!!

Related

I am in the needof some help...

Hello, i have just rooted my nexus 7 (With wugs toolkit) an i installed a theme (Not a ROM, but a theme) and i am stuck in a bootloop. I have pushed roms to the device, Installed them but nothing works. I am currently going to install the stock ROM and lose root. I just want to know what has happened.
*5 mins later* changed the name of my new ROM... fixed now
0l1v3rof said:
Hello, i have just rooted my nexus 7 (With wugs toolkit) an i installed a theme (Not a ROM, but a theme) and i am stuck in a bootloop. I have pushed roms to the device, Installed them but nothing works. I am currently going to install the stock ROM and lose root. I just want to know what has happened.
*5 mins later* changed the name of my new ROM... fixed now
Click to expand...
Click to collapse
To avoid future problems the best idea is to take a little time to learn hot to root with adb. Wugs is great for getting out of a bootloop situation, but you will not have much luck with rom flashing. Nexus just doesn't get along with rootkits. Besides its always great to learn how everything works, especially if you want to make roms.
Im glad you fixed, its very annoyng when you get stuck.:victory:

[Q] Accidentally Patched stock kernel 4.1 for multirom on 4.3 Nexus 7

Hey all, I was installing MultiRom so that I could try out different roms with the primary purpose of getting GameCih working on my Nexus 7 (1st Gen). I went through the first steps but got the "Kernel: doesn't have kexec-hardboot patch!" message. So following the guide at http://forum.xda-developers.com/showthread.php?t=2457063, I went ahead to patch that kernel. However, when I hit install, I realized it said it was a 4.1 stock kernel. The install ran and when the boot started, it just sat on the colorful X for 10-15 minutes. I booted into recovery and tried to figure out a way to get the proper kernel on the device and install that, but had no luck. Unfortunately, I backed up using the Wugs Nexus Toolkit and forgot to do it within the recovery on the device. So are my only options to wipe the device and start over or can I install the proper kernel, or is there another solution? Thanks so much for your help.
Sorry for the double post, but I waited several days to reply. I ended up going ahead and doing a wipe. It kept the rom, but did seem to fix the issue. I also tried installing the AOSP 4.2.2 ROM in MultiRom, but that one isn't working. And once I did that, several of the apps stopped working in the PAC Rom. It doesn't look like I'm going to get much help here, but I thought I'd at least respond to my original post

My Custom Mod Misadventure

Okay, I gave this a shot.
I used the Nexus Root Toolkit and rooting the thing went pretty well. I downloaded a Cyanogenmod rom, actually 2, and that was the start of my issues I think. I accidentally loaded the nightly instead of the stable.
I also didn't realize that adb would not boot anymore with 4.2.2 so I was stuck. I checked in the settings of the Nexus and it loaded up various roms you could use. I would select them and it would start to load, but then show the error message with the little android on his back.
I followed the tutorial "Root and Install CWM On Nexus 7 Running JB 4.2.2" in an attempt to get some control back and it went well until I was supposed to find the zip on the device. I had copied it over, separate from any folder, but I could not find it while in bootloader.
I ended up manually putting it in bootloader and using the Nexus Root Toolkit to restore the stock rom.
I liked certain things about the custom rom, but it was a pain not having the Google Apps, and I could not get the Gapps to install either.
Obviously I knew just enough to get halfway there. I am not sure when I will try this again, although I would like to learn more. I guess I better read some more tutorials on here.
Why didn't you just flash gapps in recovery?
Sent from my Nexus 7 using Tapatalk
Well first off there isn't Android 4.2.2 for the new Nexus 7, you must have followed a tutorial for the old one.
I used the nexus 7 toolkit.... There lies your problem
You used a toolkit not knowing what you're actually doing. Or what any of the terms mean / how and what they're used for etc.
Adb doesn't boot... Um what. Fastboot couldn't flash cm11...um what 4.2.2 um what

[Q] "Bootloop" Nexus 7

I panicked and probably did something quite stupid...
So I tried to flash the new cyanogenmod rom to have a taste of kit kat, but then I had the status 7 error.
This never occurred to me before, I didn't keep a backup to fall back onto... ( yes, I am an idiot, I learned my lesson, the hard way)
Than the device won't boot, it shows the Google logo twice, and then goes into the clockwork mod, where you choose to flash roms
and I am stuck.
I tried Nexus Root Toolkit, doesn't help because my device is not booting up, no way can it install the drivers properly...
and I think I did something more ingenious... I just tried anything on the Toolkit, and I got my rooted Nexus 7 locked...
But it's still the same, I am stuck at the clockwork mod thing just as before... Wiped whatever I can. and even formatted the sdcard and system...
Some Android Wizard out there... Please help...
If at boot you go to recovery directly... You have had to flash new version of recovery in wrong partition. You must flash it last version of recovery with "fastboot flash recovery yourrecovery.IMG" (see 'recovery' as partition to flash). Then flash boot and system partitions from factory image (in XDA have you multiples threads about it) if you want to keep your data. If not, flash factory image from usual ways (this wipes your data) and then flash recovery like I say above.
After that, try to flash CM again.
PS: I recommend TWRP instead of CWM.
Sent from my Nexus 7 (grouper) using Tapatalk.
but its more serious than that... My computer doesnt recognize the tablet because of some driver issues... I am not sure, at this moment, whether the USB debugging thing still works
i can only get to the clockwork mod page, bootloader and thats it.
I cant flash anything, I cant transfer files from the PC to tablet....
please, please help.
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Vishnuisgod said:
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Click to expand...
Click to collapse
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
dangercl0se said:
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
dangercl0se said:
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
Click to expand...
Click to collapse
it was already on computer....
make sure you look for "android tool kit"....

Stuck on Cyanogen loading screen.

Hi everyone,
Apologies for asking what is probably a utterly noob question, but I'm hoping someone can help.
I have a 2012 Nexus 7, that was fine until the updates through to Lollipop. At 5.1 it became a rechargeable paperweight! I guess we all know about that!
I have looked up loads of online videos etc. and decided to stick Cyanogen 10.2.1 on it as that seemed to be a good choice.
I installed Rom manager, got the Clockwork recovery bit installed at 6. something, and placed the CM 10.2.1 and G apps zips into the tablet, and then navigated through to the clockwork recovery bootloader, through to install from SD card.... selected the CM zip and let it get going.
An hour later and it's still flashing a Cyanogen loading screen at me and nothing more.
What the hell do I do now? Other than throw the damn thing in the bin(Which I'm resisting atm!).
alex.mc said:
Hi everyone,
Apologies for asking what is probably a utterly noob question, but I'm hoping someone can help.
I have a 2012 Nexus 7, that was fine until the updates through to Lollipop. At 5.1 it became a rechargeable paperweight! I guess we all know about that!
I have looked up loads of online videos etc. and decided to stick Cyanogen 10.2.1 on it as that seemed to be a good choice.
I installed Rom manager, got the Clockwork recovery bit installed at 6. something, and placed the CM 10.2.1 and G apps zips into the tablet, and then navigated through to the clockwork recovery bootloader, through to install from SD card.... selected the CM zip and let it get going.
An hour later and it's still flashing a Cyanogen loading screen at me and nothing more.
What the hell do I do now? Other than throw the damn thing in the bin(Which I'm resisting atm!).
Click to expand...
Click to collapse
Perform a dalvik cache wipe.
Sent from my YUREKA using Tapatalk
alex.mc said:
Hi everyone,
Apologies for asking what is probably a utterly noob question, but I'm hoping someone can help.
I have a 2012 Nexus 7, that was fine until the updates through to Lollipop. At 5.1 it became a rechargeable paperweight! I guess we all know about that!
I have looked up loads of online videos etc. and decided to stick Cyanogen 10.2.1 on it as that seemed to be a good choice.
I installed Rom manager, got the Clockwork recovery bit installed at 6. something, and placed the CM 10.2.1 and G apps zips into the tablet, and then navigated through to the clockwork recovery bootloader, through to install from SD card.... selected the CM zip and let it get going.
An hour later and it's still flashing a Cyanogen loading screen at me and nothing more.
What the hell do I do now? Other than throw the damn thing in the bin(Which I'm resisting atm!).
Click to expand...
Click to collapse
Did you wipe cache amd dalvik?
And try twrp recovery! Much better.
Also do factory reset in clockwork or twrp recovery.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Some info I should have mentioned, I rooted first successfully. I did a factory reset and wiped the caches.
Then I installed the Rom manager. I had to do some faffing around to get the current clockwork recovery installed.
Then I went into the recovery boot bit, wiped the Dalvik cache as I'd seen it mentioned.
Then I went for the sd card install, and it's still currently on the loading screen!
Ok guys....... it seems to have worked!
I went back in and cleared Dalvik, cleared the Cache, factory reset.
I couldn't then find the CM zip in install from sd card? But just hit reboot as I couldn't think what to do?
Same Cyanogen loading screen... yet this time it's loaded! And is working!
Thanks for the suggestions eveyone..... I'm not sure what I did but it seems to work now!
Thanks again.
try to use an old recovery and a old bootloader?
Just bumping up my thread the once,to say thanks for all the help.
It's all working well now, and CM10.2 is a revelation in comparison to the laggy, virtually unuseable lump of metal and plastic that my tablet was beforehand!
I am still slightly gobsmacked that Google sold me a very decent device, and then progressively crippled it to the point it wasn't useable! But hey ho, I got it sorted in the end.
I am a technically okay guy in most things, but was struggling with this a little, so I'd recommend anyone attempting this to have a good read around and then go for it. Like me, if you run into problems, there's always good advice available if you just ask.
Thanks again all....

Categories

Resources