I read how there are no stupid questions, well I'm about to test that I think. I'm a complete newblet to this sort of thing but I have an N7 2012 running like a dog on 5.1.1. So like many, many other posters here I want to make her fast again but would rather not rollback to 4.4.
So I found this: http://forum.xda-developers.com/nexus-7/development/rom-6-0-android-marshmallow-pure-aosp-t3226012
I wonder firstly, I didn't see a step on backing the current environment up in case of brickage. Is that something the author thinks anyone wanting to flash their unit should know how to do already?
And if so, are there any other steps that would be beneficial to do prior to the actual flashing that any experienced ROM alterer would do that I should as well?
Thanks guys!
I'm about to go down the same route.
I have TWRP recovery installed and am using it to backup the more or less stock setup. (except for TWRP recovery, custom kernel and SuperSU.)
I'm seeing that my backup will take 2.6 gigs though, which almost runs me out of SDCard space.
But since 5.1 is pretty much unusable I probably won't keep the backup long.
As long as your bootloader is unlocked, Nexus devices tend to be hard to brick (barring any N7 2012 specific issues.)
Consider upgrading to N7 2013 running stock Android 6.0. I have 2 for app testing and they are pretty darn nice, especially for the price. Can buy for less than $150 new now, and good bargains for used.
Thanks Mike, Question what guide did you follow to get yours rooted and the recovery stuff updated?
mikereidis said:
I'm about to go down the same route.
I have TWRP recovery installed and am using it to backup the more or less stock setup. (except for TWRP recovery, custom kernel and SuperSU.)
I'm seeing that my backup will take 2.6 gigs though, which almost runs me out of SDCard space.
But since 5.1 is pretty much unusable I probably won't keep the backup long.
As long as your bootloader is unlocked, Nexus devices tend to be hard to brick (barring any N7 2012 specific issues.)
Consider upgrading to N7 2013 running stock Android 6.0. I have 2 for app testing and they are pretty darn nice, especially for the price. Can buy for less than $150 new now, and good bargains for used.
Click to expand...
Click to collapse
Wait, I figured it out. So I've got it rooted, then pushed Cyanogenmod recovery and rebooted and got into recovery mode. First off I tried loading Cyanogenmod 12.1 which worked well. It was snappy however I could not figure how to get gapps reinstalled. Thinking maybe another rom might already have google apps I then pushed 6.0.1_r10_Grouper-MM. Booted fine but still not gapps..
So I find a website that says to push the zip to /sdcard/ then apply update from sdcard in recovery mode. However now, I'm getting errors complaining about F2FS.
E:can't open /cache/recovery/last_log
E:unknown fs_type "f2fs" for /cache
Couldn't mount /sdcard
Installation aborted
Googles not been much help yet.
7298 said:
Thanks Mike, Question what guide did you follow to get yours rooted and the recovery stuff updated?
Click to expand...
Click to collapse
7298 said:
Wait, I figured it out. So I've got it rooted, then pushed Cyanogenmod recovery and rebooted and got into recovery mode. First off I tried loading Cyanogenmod 12.1 which worked well. It was snappy however I could not figure how to get gapps reinstalled. Thinking maybe another rom might already have google apps I then pushed 6.0.1_r10_Grouper-MM. Booted fine but still not gapps..
So I find a website that says to push the zip to /sdcard/ then apply update from sdcard in recovery mode. However now, I'm getting errors complaining about F2FS.
E:can't open /cache/recovery/last_log
E:unknown fs_type "f2fs" for /cache
Couldn't mount /sdcard
Installation aborted
Googles not been much help yet.
Click to expand...
Click to collapse
I've been doing this stuff for 5 years, so I usually don't need guides, just a few hints sometimes. CM recovery these days is something I try to avoid as it mostly works only with CM. I use TWRP and flash it with adb commands like:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-grouper.img
I ended up flashing this Marshmallow ROM because it seems to be the most popular at this time: http://forum.xda-developers.com/nexus-7/development/android-6-aosp-grouper-t3268172
And I'm happy with it so far.
Strange thing though is that I had to flash it 3 times to get it to flash without any error.
Then I had to flash the Benzo Gapps 2 times to get that on with no error. Result is working OK so far.
Damn Mike, I shoulda waited another hour before settling on mine. I tried that 6.0.1 i linked earlier in the thread about 4 times. Three times it applied successfully with 1 seeming to lockup during the new user setup. But I tried at least 4 different gapps that all didnt work. The usual results was Google Play Services have stopped. So because the day was nearing an end and I needed it last night to read I dropped back to the Cyanogenmod 12.1, changed the theme and tossed in Open Gapps Nano http://opengapps.org/?api=5.1&variant=nano
Wound up having to load play books, play services, gmail, and chrome individually.
But it's snappier than ever (so far). I'll end up re-trying 6 very soon but this time I'm trying the one you found.
mikereidis said:
I've been doing this stuff for 5 years, so I usually don't need guides, just a few hints sometimes. CM recovery these days is something I try to avoid as it mostly works only with CM. I use TWRP and flash it with adb commands like:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-grouper.img
I ended up flashing this Marshmallow ROM because it seems to be the most popular at this time: http://forum.xda-developers.com/nexus-7/development/android-6-aosp-grouper-t3268172
And I'm happy with it so far.
Strange thing though is that I had to flash it 3 times to get it to flash without any error.
Then I had to flash the Benzo Gapps 2 times to get that on with no error. Result is working OK so far.
Click to expand...
Click to collapse
I tried that MM ROM it worked fine for first week, then it started to act the same as it was on 5.1.1. I used Nexus Root Toolkit to flash my nexus to stock and then flash the rom with just few clicks
Related
Hi Everyone,
Sorry my first ever post is a question, but I have looked around a lot and can't find an answer for my problem.
I have a 16gb nexus 7 that I have rooted and unlocked the bootloader. I have successfully flashed both CM10 and AOKP roms, but each time flashing the GAPPS afterwards results in absolutely nothing. The ROMs work fine, and I can still access the Play store, but none of the GAPPS show up in my Applications folder. I have tried this multiple times with multiple GAPPS zips.
I flashed ClockworkMod Recovery, but interestingly I can only get into it by rebooting via CM10 or AOKP reboot to recovery options, or through ROM Manager's reboot option. If I manually enter fastboot then try to go to recovery it hangs on the Google loading page.
I am okay with the CWM issue, but I would really like to be able to flash the GAPPS zips! I change ROMs a lot (I have a Galaxy Nexus, which I have never had any issues with), so manually installing the google apps each time would be a pain.
Any help would be appreciated!
Hello,
Are you flashing this right after flashing the rom or are you booting into the rom then restarting and flashing the gapps?
You should be doing this...
Be sure to back up your current ROM!
Update your radio to the above recommended version if you have not already done so.
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Install darkside-wipe-cache-only.zip (which fixes bootloop due to bad /cache format)
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
good luck!!
Yes I flash the gapps immediately after flashing the rom without actually booting in to the rom first.
I have been doing a full wipe, but I did not re-format so I will try that later when I have time.
Also, never heard of the darkside wipe cache zip so that is probably my issue with the bootloop!
As for the radio, I could be totally wrong, but does the nexus 7 even have a radio file..? I thought that was just for phones or tablets that can connect to network carriers.
Thanks for the help!
sloambbr said:
Yes I flash the gapps immediately after flashing the rom without actually booting in to the rom first.
I have been doing a full wipe, but I did not re-format so I will try that later when I have time.
Also, never heard of the darkside wipe cache zip so that is probably my issue with the bootloop!
As for the radio, I could be totally wrong, but does the nexus 7 even have a radio file..? I thought that was just for phones or tablets that can connect to network carriers.
Thanks for the help!
Click to expand...
Click to collapse
You are absolutely right about the radio. Your welcome.
no6969el said:
You are absolutely right about the radio. Your welcome.
Click to expand...
Click to collapse
hey i tried everything you said and still no gapps... I tried to do a titanium backup of the stock rom then use that to install the gapps on the aokp rom but that didnt work either. I did notice though that when I did not install the gapps package the play store wasnt installed, but if i install the gapps zip, the play store is there...just none of the other apps.
Just search apps by Google inc on play if you have the store
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
Just search apps by Google inc on play if you have the store
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It would nice to not need to do that every time as I frequently flash new roms but oh well I will do that for now. Maybe it will change with a new update
I have the same issue. Using CWM I've installed two different roms and two different gapps versions (using the recommended procedure) both times my Nexus 7 boots up & the only Google app installed is Play Store.
I'm having a related problem with GAPPS but it's much more severe.
I have installed the Kaos rom on a Nexus 7 (and that install would ONLY succeed if one de-selected the GAPPS option during the Kaos installer process, otherwise you'd be thrown into infinite boot animation land) and everything was looking perfect.
Then i attempted to install GAPPS from a zip that was linked in a Nexus 7 thread. the specific package i used was...
gapps-jb-20120726-signed.zip
... and ever since that point the tablet cannot boot into the Android environment. It will attempt to, then hang for longer than it should at the Google logo screen (tiny lock at the bottom) and when that fails it will boot into the recovery environment.
I'm running TeamWin Recovery 2.2.1.4 because ClockworkMod constantly failed to work properly for me (never could manually launch recovery from the bootloader, but TWRP will launch manually just fine)
The TeamWin Recovery can see everything and even give me a terminal, and fastboot still sees the device just fine at the bootloader... so there's a lot i could try, if i only knew where to start.
The REAL annoying thing, however, is that i performed a backup just prior to attempting the GAPPS install (because of all the trouble this gives people) and now TWRP cannot successfully restore that backup. it can see both of the backups that i have made (stock and Kaos initial successful boot) but whenever i attempt to swipe to the side to start the restore, the whole recovery environment just restarts on me.
help? suggestions?
well, i see that i wasn't running the latest TWRP for the Nexus 7. i just used fastboot to flash to ver 2.3.2.1 and that appeared much happier.
it was able to see the two recovery images made by the earlier version and it's now restoring...
... and now we're rebooting...
... and KAOS appears to be proper booting...
... and back in business to the way it was before i tried the GAPPS install!
(this single run-on post -- as opposed to a series of small update posts -- brought to you by the faster processor and nice system specs of the Nexus 7 which kept on ticking along as i was typing here in my browser!)
---------- Post added at 06:26 AM ---------- Previous post was at 06:03 AM ----------
and now i have successfully installed GAPPS using a 4.1.2 package... gapps-jb-20121011-signed.zip
it's amazing how things can go sideways so quickly if you're simply using the wrong version of one thing or another. and it's also amazing how quickly these threads become outdated given the very fast pace that Android keeps evolving and how fast the dev community pops up with new packages, roms, and mods of other roms.
speaking of which, the KAOS fork of CyanogenMod is excellent! i already love the Apex launcher more than the stock Trebuchet (little interface tweaks like a quick menu popup whenever you long press a home screen item, for example) and i think this is a wonderful rom package.
great work, and a wonderful installer... just remember to NOT include GAPPS during the initial rom install process! uncheck that box!
UPDATE: gapps install incomplete / market installs failing
So it seems that while my Nexus 7 now shows the Play Store (which i still find myself calling the Market because Play Store is a colossally dumb name) i don't see most other Google apps.
Background sync and all that is working, but maps and youtube and such are not there. I've read that these are removed from newer versions of the GAPPS pacakges because it takes up less space and said apps are in the Market anyway.
however, when i search for them and pull them up in the Google Market they fail to install. i do not know why this would be. it doesn't matter a WHOLE lot to me, because i don't use GMail, i run Brutal Maps instead of stock Google Maps, and NextVid is far better than the stock, bloated YouTube player.
still, it made me curious.
so, it appears that i am not the first person to experience the "Unknown error code during application install" error, naturally. the (very simple) fix is in this thread.. http://forum.xda-developers.com/showthread.php?t=1992241
I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk
Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"
omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on
another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/
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....
Hey folks. I recently revived my 2012 Nexus 7 wifi. I thought it was toast, but I guess it just needed a nap. It was having Gapps problems last time I tried to flash, and this time around, I'm having the same issues. I've attempted to flash a few versions as well as flashing a few different roms. The roms flash fine, and they run very smooth, but Gapps constantly either fails to flash due to space concerns or even though it claims success, it doesn't load the services and I end up with a ton of errors and can't really work with the tablet. The computer itself obviously runs great, but I'm missing something, or need to take it back a step or something.
I was hoping someone could explain to me how to purge everything and install the most appropriate Rom & Gapps pairing. I'm using CWM, btw.
JavaMac said:
Hey folks. I recently revived my 2012 Nexus 7 wifi. I thought it was toast, but I guess it just needed a nap. It was having Gapps problems last time I tried to flash, and this time around, I'm having the same issues. I've attempted to flash a few versions as well as flashing a few different roms. The roms flash fine, and they run very smooth, but Gapps constantly either fails to flash due to space concerns or even though it claims success, it doesn't load the services and I end up with a ton of errors and can't really work with the tablet. The computer itself obviously runs great, but I'm missing something, or need to take it back a step or something.
I was hoping someone could explain to me how to purge everything and install the most appropriate Rom & Gapps pairing. I'm using CWM, btw.
Click to expand...
Click to collapse
First of all CWM is ancient...
I do this when I feel like starting over.
(First flash TWRP, via fastboot if possible)
Format the partition /system, /data, /cache and Internal Storage (yes even that)
Then connect it to the computer, get on XDA and download CM13 or a ROM you like (I like CM13) and flash opengapps (pico, just google it)
I would suggest following the suggestions that the developer of the CM13 port to the Nexus 7 gave to fix the eMMC speed.
Installing Trimmer and setting it to daily is enough.
Good luck!