Database Users

[HOLY CRAP][SPRINT P100] Stock to CM10 JellyBean - Complete Walkthrough

*********************************************
CM10 is now available.
Requirements: Root
From rooted stock or a custom rom, just download and install updated Rom Manager from the Play Store and download CM10 Nightly and GAPPS. Reboot into ClockWorkMod, factory wipe, disable signature check, flash CM10 twice. The first time partitions our tabs and reboots. Flashing a second time is for good measure. Then flash GAPPS. Done.
Note: I am not sure if Rom Manager can flash ClockworkMod directly. I personally updated from ICS > CM10 by downloading CM10 and GAPPS through GooManager and flashing manually in ClockWorkMod.
Its been reported that you can go directly from rooted stock to CM10. I've actually completed everything below to get to ICS first (Stock > ICS > CM10 JB).
CM10 is a much better experience. The tab works much better, doesn't freak out, lasts longer, plays better.
*********************************************
Wow. Lots of different, confusing, and scattered information about how to go from stock Gingerbread to the latest CM9 build. It is all very confusing and honestly most of the useful information isn't even on this site. So I figured I would help myself (and others) in creating a very detailed walkthrough of the process required to successfully get from GB to CM9 Build 7.
**This specifically outlines the methods to take a COMPLETELY STOCK Sprint Galaxy Tab 7" SPH-P100, unrooted, to a ICE CREAM SANDWICH rom. I "think" it might also work for the Verizon CDMA and a few others. I think the ROM itself is a general overall generic build for all 7" Gtabs. So heads up that if you have a different version, you might want to use this as a guide rather then a step-by-step.**
BACKUP EVERYTHING YOU MAY NEED BECAUSE OBVIOUSLY THIS PROCESS WILL FORMAT YOUR GALAXY TAB
GET CONNECTED!
We need to download Heimdall's App and his Drivers (Main URL). This is the first confusing steps as everyone suggests using an older version, but the included drivers don't work on newer Windows OS's. So you have to mix and match a few different versions to get it working. I've already compiled an archive with everything you need: Heimhall Mixture /w zImage & ClockWorkMod 5.0.2.7
1. Extract everything to a simple folder [ex. C:\GTABICS ]
2. Turn off Gtab. Hold VolDown+Power until you get to a downloading screen
3. C:\GTABICS\Drivers\zadiag.exe to load drivers [try running as Administrator]
4. C:\GTABICS\heimdall-frontend.exe to start the process
5. Kind of confusing. Focus on the "BROWSE" buttons. Look for "Kernel(zImage)" on the left and "Recovery" on the right. Hit browse for each one and select the appropriate file from C:\GTABICS. Obviously "Kernel(zImage)" = "zImage" and "Recovery" = "recovery.bin".
6. Make sure Kernel(zImage) and Recovery both have files selected and a checked box. While GTAB is at the black Downloading screen: Hit "START".
7. The process is pretty fast. Don't rush. At this point your tab will probably just bootloop anyway.
LET'S GET THIS SHOW ON THE ROAD
Now you have ClockWorkMod installed and a proper kernel, most flashers will feel really at ease right now. But there are a few little quirks that will cause this to go bad. You have to install 2 versions of ICS to get to the latest; One using the existing partition table, and a second that will update to a newer format. You obviously have to install GAPPS like always with a CM rom, but not so fast, you have to manually "MOUNT /SYSTEM" in CWM before it will even take. And there is the fact that you have to manually open and edit the CM9 Build7 update and remove code....[holy crap].
But it is pretty easy once you go through it once.
REQUIRED FILES
JT1136 CM9 V5
JT1136 CM9 V7 UPDATE
GAPPS
Prepare CM9 v7 Update
1. On your PC, open "update-cm-9.0.0-RC0-galaxytab7c-KANG-BUILD7.zip" and browse to META-INF\com\google\android
2. Copy "updater-script" to your desktop and open with Notepad and remove the first 3 lines or just Download it.
3. Drag and drop the update-script back into the META-INF\com\google\android folder, overwriting the existing one.
If all goes well, you are now done with the PC.
COPY FILES AND FLASH
1. Copy Build5, the new Build7, and GAPPS to your microSD card.
2. Boot into ClockWorkMod: Power off. Hold VOLUP + POWER
3. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
4. Flash zip from SDCard: locate Build5 and Flash
5. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
5.5 [OPTIONAL] You should be able to boot into ICS at this point if you want to make sure build5 flashed properly before upgrading to build7
6. Flash zip from SDCard: locate Build7 and Flash
At this step, my GTab rebooted in the middle of the process the first time. It freaked me out but I assume (now) that since it changed the partition tables, it needed to reset. So I did it a second time just to be safe:
7. Flash zip from SDCard: locate Build7 and Flash
8. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
Congrats. You should have a working bootable CM9 build. But lets flash GAPPS so we have our Google services. This is tricky.
9. Mounts and Storage > Mount /System
10. Flash zip from SDCard: locate GAPPS and Flash.
11. Finally [!] reset device and prepare for boot.
Now you are on the latest CM9 build [7] and have the latest GAPPS installed. Hopefully you are booting now and see the famous ICS Boot Animation. Have fun. In the future you should be able to simply download new roms as they are available and flash normally like you would any other device.
RECAP:
Drivers and Flash Tool
Pre-Edited updater-script
UPDATES
Convert to Sprint
The above procedure will set your Tab as a Verizon version. If you plan on using the Sprint cellular service or just want everything to match, then flash this via ClockWorkMod.
****************************************​
I didn't do any development work. All credit goes to Heimdall for his fantastic Recovery Flasher and jt1136 for his great stills porting this awesome rom over to our Galaxy Tabs. All I did was bump and grind my way through to see a successful working flash. I figured if I didn't post a walkthrough here, I would hate myself in 6 months when I boink something up and have to do this all over again. I would recommend you keeping all of the files safe somewhere to prevent this headache again.
DONATE TO JT1134
DONATE TO HEIMDALL
MAIN HEIMDALL URL
MAIN ROM URL

player911
i have been thinking about moving up to ICS with my sprint sph-p100
just not sure if i should jump now or wait till more things are working ?
do the things working out number those not , is it ready to be a daily driver yet?

Camera fully works but is flaky sometimes. Video out isn't working yet but he's working on it.
Other then that, its golden. Very fast and works well. Really worth it. Feels much better... like an actual tablet vs a large phone.
Iffy Camera and video out aren't worth holding back. One of the benefits is now Wiimotes and PS3 controllers will pair up using their respective apps now.
Sent from my Galaxy Nexus using xda premium

Thanks for the input ill be movin up to ICS soon
Sent from my SPH-P100 using Tapatalk

flashed sprint Tab
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!

Great Thanks! The first complete step-to-step instruction for installing ICS on Sprint p100.
One note- if you have Error 12 - delete all SAMSUNG USB drivers on PC, rebut and instal drivers from first archive.
At least!!! Thanks a lot!

I don't use the cellular network (sprint) but it does come up and show signal. I don't use it as a phone or anything like some people (supposedly you can install phone.apk and make calls over a voice plan).
I just use the tab as a tab. I just wanted to confirm that it appears to see the cellular network fine.
Sent from my Galaxy Nexus using xda premium

just made the plunge had some issues with the drivers for heimdall and after that i got a fail when flashing hit start again and it flashed
followed all the steps and im on cloud 9 now wow
gonna take a few to get used to ICS

Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2

LivnDream said:
Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2
Click to expand...
Click to collapse
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium

scabrerautexas said:
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!
Click to expand...
Click to collapse
you have nothing to worry about, 3g will still work.. i have flashed many roms on mine including ics ones and 3g still worked.
well i shouldn't say many roms...i've flashed it many times to ics and back to gb.

player911 said:
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its a sprint patch on the rootzwiki fourm for this rom ill get you a link
i got a post there with a link to the patch someone there posted
it changes the wireless from showing veirson to sprint and the tab to sph-p100
wasnt tryin to cause any confusion
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build7-0304/page__st__1040#entry613901

Do I need to be on stock gb or could I do this while rooted? Sorry I'm noob with hiemdall.
Sent from my SPH-P100 using xda premium

As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?

dog44 said:
As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?
Click to expand...
Click to collapse
Try re-downloading the version 5 zip again. Make sure you don't edit anything within the zip before you put it on your SD card. This happened to me when I edited the version 7 zip as instructed above.

Ok. Got it working. What is the newest ver.? I'm on 4.03
Sent from my SPH-D700 using XDA

I think 4.0.3 is the latest ported over. I have a Galaxy Nexus and 4.0.4 was just released... so I would expect delays in porting that over to unofficial devices.
The patch, I've found, is just cosmetic. Once you upgrade to ICS using this method, the build.prop has everything setup as a Verizon Device (name, settings, etc). They can all be manually changed but there is a patch that you can flash via ClockWorkMod that does everything for you.
The link was posted a few posts up.

What is DTI? I may just leave it as verizon since I get more signal. LOL

Hey what's up guys I just threw this on my sprint tab... I had a few quirks with it early... when I first flashed the clockwork mod on it, the screen was discombobulated... the capacitive touch orientation was in landscape mode while the actual screen was in portrait.
So when I had to put the files back on the tab after modifying build 7 zip. I had to figure how to unlock the screen and then and also to choose "connect USB to storage"
Then I got a little nervous while doing the wipe because it took long. I thought it froze..
Just a heads up of what could happen to other guys .
Also now after full install, I find that my ram is usually pretty low and my CPU usage is almost always @ 100 percent .
Taking away from the fluidity... any suggestions ?
I restored my email from titanium back up and also my browser bookmarks, now they don't open up or close immediately. This happens with a lot with system data restored things....
Sent from my SPH-P100 using Tapatalk

Whenever my tab starts it says encryption unsucessful, how can I get past this screen?

[Q] Can't Install GAPPS on my Nexus 7

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

[Q] Clockwork Mod Rom update problems?

So I finally got arround to getting my Nook up-to-date from 7.1 to the 7.2 encore CM7 rom. Thought that Rom Manager would take care of everything for me, and it looked like it was well on its way.
So it finally downloads and I'm all excited to install it, maybe it'll help the random hanging errors when I'm on wifi. (dummy me) Selected just to wipe dlavick (sp?) cache and not backup current rom, and durring the install, it reports a critical error and fails out. Okay, fine, sounds good, i'll just hop online and figure out how to manually install it. I reboot, and it just hangs. Wierd, but I reboot again. And again. And I finally come to the conclusion that it must have screwed over my old rom as well.
If anyone can give me an idea of how to proceede, do i reflash a new rom? And how do I go about it without damaging the current files that I have installed, I've got a few hundred ebooks and comics that i'd hate to lose.

breakneat said:
So I finally got arround to getting my Nook up-to-date from 7.1 to the 7.2 encore CM7 rom. Thought that Rom Manager would take care of everything for me, and it looked like it was well on its way.
So it finally downloads and I'm all excited to install it, maybe it'll help the random hanging errors when I'm on wifi. (dummy me) Selected just to wipe dlavick (sp?) cache and not backup current rom, and durring the install, it reports a critical error and fails out. Okay, fine, sounds good, i'll just hop online and figure out how to manually install it. I reboot, and it just hangs. Wierd, but I reboot again. And again. And I finally come to the conclusion that it must have screwed over my old rom as well.
If anyone can give me an idea of how to proceede, do i reflash a new rom? And how do I go about it without damaging the current files that I have installed, I've got a few hundred ebooks and comics that i'd hate to lose.
Click to expand...
Click to collapse
Go to my tips thread linked in my signature and make a bootable CWM SD per my item A10. If your books and comics are on SD do not use that SD for CWM, use a different one. Then you can flash the new CM7.2 ROM with that. It should boot fine for you. If it still balks on you, go back to CWM and do a wipe data/factory reset. That will wipe out the installed apps and settings, but will not effect the books and comics you have on your media partitions (emmc and sdcard). But you will have to reinstall all of your apps.

[Q] After installing CM, internal storage gone...?

Alright... I have been running CM7 on my Defy (MB525 red lens) for years without any issues, but recently I decided it was about time to wipe the thing and start from scratch, and I figured, if I was going to do that, why not install the latest (CM11) and see how it works for a bit before (if necessary) downgrading to a more stable version.
So, after reading up I figured what I should do is:
1. Flash SBF with RSD Lite.
2. Root phone (easy with Framaroot 1.7)
3. Install custom recovery/bootloader (easy with SndInitDefy 2.0)
4. Flash to CM10.0 latest (android 4.1)
5. Reboot, check if it runs, then reboot into recovery
6. Flash to CM10.1 latest (android 4.2)
7. Reboot, check if it runs, then reboot into recovery
8. Flash to CM10.2 latest (android 4.3)
9. Reboot, check if it runs, then reboot into recovery, follow Quarks instructions for 4.4/CM11
I thought that would be easy enough, but I have attempted this about 20 times by now and am running into the same problem time and time again... after flashing to CM10.0, 10.1, or 10.2 and booting up, my phone turns out to have lost access to its internal storage. As a consequence, bootloader/cwm/twrp becomes inaccessible, installing anything becomes impossible, and any settings changes you make are lost again whenever you reboot the phone. I would expect it to be a corrupt ROM I am installing, except for the fact that this seems to be happening randomly on one of the 3 flashes, not consistently on the same flash. Whenever it happens though, the only thing I seem to be able to do is flash the SBF again and start from scratch... and where I do occasionally get as far as having CM10.1 running and functioning, I have not yet had a single run through where I ended up with a functioning version of CM10.2.
Am I missing some important step I should be taking inbetween my steps somewhere? I read some stuff about custom kernels, but if I understood things right, they are included in the CM zip installs, so I shouldn't need to do that manually... or am I mistaken about that? Or am I not missing a step in my process, but is there an easy fix for this issue that I have overlooked? I imagine that this is either a problem that everyone runs into but is very easy to fix (and therefore not allover these forums) or it is a problem I am bringing upon myself by doing something wrong in my upgrading steps.
Help would very much be appreciated.
P.S.: I have no difficulties using adb or anything like that, I originally rooted my phone using ADB too, so any solutions involving ADB or anything like that shouldn't be an issue. I am fairly confident in my use of computers and programming where it concerns computers, but I am somewhat new to the whole android modding scene, hence my need for some assistance.

Try a full wiper (either defy full wiper or aroma wiper or even TJKVs safe wipe) to wipe to ext4.
Sent from my Nexus 7 using Tapatalk

18 year IT vet/Total newb to rooting/rom'ing tablets

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