yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 7" Android Development] CodyF86:
Here is 20130812 for p3110 / p3113 w/IR: http://d-h.st/qlG

Something must have been changed with SystemUI because it crashes systemUI now with the TabletUI patch. I'm going to take it down and tomorrow I'll put up separate links to 0811 that tabletUI still works with.

Building p3100
[Galaxy Tab 2 7" Android Development] CodyF86:
Here is 20130812 for p3100: http://d-h.st/O2p
[Galaxy Tab 2 7" Android Development] DrockaDroid:
Awesome to see IR supported on CM!

I have installed 8/12 but IR won't pair with my TV using Peel.

Is this latest IR build & patch considered fully functional?
[Galaxy Tab 2 7" Android Development] kenundrem:
Try IR Universal remote for GS4 on the Play Store...it seems something is up with Peel on an older version.
[Galaxy Tab 2 7" Android Development] Android-Andi:
will only work on a P3113 and not on a P3110 (your signature)
[Galaxy Tab 2 7" Android Development] CodyF86:
Peel is broken, it works when you set it up but once it stores the codes and goes to the main app it won't work. Use the IR Remote for GS4 it works amazing.
[Galaxy Tab 2 7" Android Development] DrockaDroid:
Alright I'll try that app instead. Thank you

I have the p3113 version confirmed

Edit: It may just be my Westinghouse TV, but it used to work when I was on stock 4.1.2.

Did you guys have to input codes for your TV?
[Galaxy Tab 2 7" Android Development] CodyF86:
Use this app: https://play.google.com/store/apps/details?id=com.freeirtv

It works great and you don't have to mess with codes.
[Galaxy Tab 2 7" Android Development] davebyone:
the tabletUI Patch 20130811 crashes my tablet with this ROM. gmail stops..
[Galaxy Tab 2 7" Android Development] CodyF86:
You can't patch 0812 with the 0811 patch, and please reread my post and the OP. I posted that TabletUI patching crashes system UI in 20130812. Something changed in SystemUI and ApG/autopatcher will need to be updated by their developers.

If you want TabletUI you can use the 0811 rom and TabletUI patch, Look at my first post. IF you want the latest rom, use 0812. :)

Edit: I'll try and patch TabletUI again tonight when I build and see if it was just a one time thing. Sometimes something gets derped on accident and it could have just been something like that. If not then like I said the patching programs will have to get updated. :)
[Galaxy Tab 2 7" Android Development] davebyone:
thank you so much!
[Galaxy Tab 2 7" Android Development] Dirtylarry11:
cant install the rom (Status 7)

Im trying to install but keep getting an error status 7 installation aborted message, ive even tried the Superuser sideload, and then the rom sideload...same error as if flashing from the tablet...Ive downloaded it 2 times as well...Are there any other roms that I can try that have the infra red?...Thanks in advance, Just not sure where to go from here...Dirty
[Galaxy Tab 2 7" Android Development] nakbaliNe:
Ir not working on p3100
[Galaxy Tab 2 7" Android Development] CodyF86:
Did you do any of the things I told you in my post before this? There is something wrong with your permissions or something. The roms flash fine, you should just be able to goto install from zip file and flash it. Like I said earlier did you try to fix your permissions and what recovery are you using?

If you have adb installed you should be able to boot into recovery and issue 'adb remount' and that should remount file system with write, and then try to flash doing that first.
[Galaxy Tab 2 7" Android Development] CodyF86:
p3100 doesn't have IR. :)

The p3113 has IR and its working. :)
[Galaxy Tab 2 7" Android Development] trmitche2:
Yes, I did enable dev options, and root access was already set to both ADP and apps when I checked.

Thanks given in a sec to to both you and the poster who answered right after your post. First I'd like to ask an open question to all, to make sure I understand that its safe to uninstall and re-install SuperSU from the Play store, if I understood you correctly. More importantly though, I'm just insanely curious what the binary update actually does for me as part of this overall process, and what the downside could be if I leave things the way they are now.... As in, what's the worst case scenario if I don't re-install SuperSU and let it reboot into CWM and let it "automagically" update (which I assume will occur without me having to go through the CWM menu and do something manually). I'm just really wanting to learn more about this particular scenario and why this step is important. I've read every page in this thread and several others, but that only goes so far, and has not truly allowed me to understand what this step is actually doing, and what are the hypothetical worst-case problems I could have due to an outdated SuperSU binary.

Thanks again to everyone here, and especially to the OP, for making my 3113 what it was born to be!

T
[Galaxy Tab 2 7" Android Development] Dirtylarry11:
I did try the fix permissions but same thing...I will try the remount and post back...tyvm!

---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------

I am using Philz recovery BTW
[Galaxy Tab 2 7" Android Development] CodyF86:
If you have root access right now then technically you don't have to let SU update, though I think it just closes out unless you update, so you can't actually change any settings. If you were to ever uninstall your super user program you would lose root access to your device and at that point you would have to sideload Superuser like I mentioned in my post above to get root back.

The reason you let recovery update superuser is because if you choose to let it update right then and there, it won't; It will just fail in 4.3.

When you choose update via recovery all that happens is your tablet reboots into recovery and it flashes the update for you just like when you flash a new rom.

In 4.3 you can't install superuser from the play store and have it gain root access, you have to side load it like in my post and the OP for superuser to have root access.
[Galaxy Tab 2 7" Android Development] CodyF86:
your flashing the right rom on the right device, right? p3110 to p3110 or p3113 / p3100 to p3100. If nothing works try clock work recovery. It flashes it fine for everyone else. That hasn't happened to anyone else it seems, but most people were using clockwork recovery I think.
[Galaxy Tab 2 7" Android Development] Dirtylarry11:
OK, thanks all, I got it...had to reinstall CWM recovery...doesn't like Philz apparently...ty for the Rom, and the Help!!!!!!!!
[Galaxy Tab 2 7" Android Development] CodyF86:
np, weird tho..I'll try and see what's going on with that. :)

I mean you should be able to flash Philz back also if you like it better, unless you plan on reflashing this rom everynight. Like I said weird tho.

Heck now that you flashed it...reflash Philz back and tomorrow flash 0813 when I post it and see if you get the same message.
[Galaxy Tab 2 7" Android Development] trmitche2:
OK, cool - thanks Cody. So, again, open question to anyone: What do I need to do from here to get my SuperSU binary updated without losing root? Or d I need to lose rot and do the whole Odin thing again like I did to get root in the first place when I was on 4.1.1? In other words, do I need to uninstall SuperSU to purposely lose root, and then follow (whatever process) to re-gain root in 4.3, in order to be able to take full advantage of all apps requiring root? I'm *REALLY* glad you replied so quickly Cody, because I was just about (finger on the button) to uninstall SuperSU and try to re-install it from the Play store. Now though, I'm not making any moves at all, until someone can give me a step-by-step, which I'm happy to follow, even if it includes losing root on purpose in order to re-gain it in 4.3. Sorry to ask for the hand-holding, but this is first tablet, although my XDA history as a lurker goes back to having a Windows 7 phone (LOL), before having and rooting a long line of Android phones going back to Android release day.

Still love this community just as much now as then, for whatever it's worth (not much, I know)
[Galaxy Tab 2 7" Android Development] CodyF86:
Just flash 4.3 and once it boots see if SU is in your app drawer. If it is open it up and let it flash its update via recovery if it asks you to, if it doesnt ask, then your done, you have root. If it isn't in your app drawer, then you'll need to do the sideload procedure I posted on the first page. Flashing update via recovery, if it asks you, has 0 chance of messing anything up, and like I said if you have no SU app once you flash, sideload it.

The reason I don't just say download it off the play store and then choose flash update via recovery is because when you download it from the play store, for some reason it won't actually reboot to flash the update.

Once you sideload, if you have to, you'll still have to let it update once via recovery anyway.
[Galaxy Tab 2 7" Android Development] trmitche2:
Thanks again Cody, but please see my original post, which said:

"The OP mentions "You will also need to open up your SU app and let recovery flash the update for it." When I open SuperSU (yellow diamond icon in app drawer), I get the update prompt as expected: "The SU binary needs to be updated, Continue?". I touch "Continue", and then I get the prompt asking whether I want to update via "Normal" recovery or "TWRP/CWM".

Normal fails outright with a failure error message, as expected I guess. When I choose the TWRP/CWM option instead, it says: "SuperSU will attempt to reboot your device into TWRP or CWM. This does not work on all devices. If this app just closes, please reboot into recovery manually.". When I click "OK", *nothing* happens. The tablet does not reboot. *The app does not even close* as referred to in the pop-up message. It just sits there in the SU app. I close it manually, power off, and reboot into CWM recovery, but nothing happens when I get into CWM, and I can't find any option in the CWM menus referring to manually performing a binary update."

See what I mean? I dunno, maybe I'm the one not getting what you're telling me, although I understand all the terminology that you're referencing (side-loading, etc.)

Sorry guys. Anyone else care to share a thought on this, even if it's to back Cody up, and maybe state the same thing in a different way, that might make it click for me? I feel like an idiot...
[Galaxy Tab 2 7" Android Development] CodyF86:
Yeah sorry that's what I meant. If it does nothing when you click ok (to reboot and flash with recovery), then you'll need to sideload it, and after you side load it, it will ask you the same thing when you start it, but this time it will reboot and flash when you click ok.

It's not hard to side load I promise. Make sure you have the samsung usb drivers installed (google it if you have to), then download the Android SDK: http://dl.google.com/android/installer_r22.0.5-windows.exe

Install it and make sure you open it up and update it.

(Make for sure if nothing else you have the package that has adb in it selected and updated.)

Then go into the root/base directory of where the sdk installed and there should be a folder in there called platform-tools. Copy your entire directory name (platform-tools) and path to your clip board...the entire thing c:\ and all.

Now click on start menu and right click on computer and click properties. Now click advanced system settings, and at the bottom it should say environmental variables. Click on that. Now on the bottom frame of that window is a variable called 'path', you need to edit it and add the entire directory you copied to your clipboard. Keep in mind entries are seperated by an ; Save your settings.

Now you can run adb from any directory. You can now plug your device into your computer, boot into recovery, select install from sideload, and issue the adb sideload command that is in my OP from the directory the SU file is in with the command prompt.

Make sure you have ADB turned on and also root access is set to apps and ADB both under Developer Settings.

Tada, you have root. :)
[Galaxy Tab 2 7" Android Development] trmitche2:
Side note:

I Installed another Chainfire app that looked cool: "NoMoarPowah", which is supposed to replace your battery charging screen with a better one, but it didnt work. Same old battery charging screen. Just now, I noticed the app had placed a shortcut on one of my desktops. I ran it, and it errored out, saying: "Could not acquire SuperUser access. Is your device rooted? If you are rooted but this message persists, reboot your device." I have rebooted a dozen times since installing that app yesterday, so that can't be good.... Argh. Now I'm really getting flustered, since it appears I may not actually even be rooted at all. SuperSU has no apps listed on the main screen. I feel like Charlie Brown... Can't do anything right.
[Galaxy Tab 2 7" Android Development] CodyF86:
You aren't rooted. If you follow the steps word for word in my previous post, you will have root access. :)
[Galaxy Tab 2 7" Android Development] kenundrem:
[MENTION=5337314]CodyF86[/MENTION] if you leave cm as is you will not have a superuser or su app in your drawer it is in settings...I have never flashed or updated anything related to root and I have full root access as I have restored/backup from titanium backup and use greenify and lagfix to name a few root required apps.
[Galaxy Tab 2 7" Android Development] CodyF86:
trmitche2 doesn't have root access right now, and with Android 4.3 you definitely do not have root access depending on what SU app and what version when you flash. You may have root access, but that isn't the case for everyone, like I said. There were changes to Android 4.3 that make your statement not necessarily true, and my builds are compiled from the CyanogenMod Github repository, so it's cm-10.2 as new as it can get. :)
[Galaxy Tab 2 7" Android Development] trmitche2:
Will do, and will report back tonight. So I guess I lost root (that I used Odin to acquire in the 1st place) when I upgraded to this thread's ROM. Agreed?

Thanks for all your patience with me Cody. You must feel like you're potty training a puppy....
[Galaxy Tab 2 7" Android Development] CodyF86:
Your fine, :) but you should have never flashed anything with odin when you upgraded to 4.3, so I don't know what you did, but follow the steps in my post and you will be fine and have root. I just did that entire procedure myself because I nuked su on my device on accident like a derp. lol :)

Unless you mean you had to install clockwork recovery to get it to flash, if that's what you mean.
[Galaxy Tab 2 7" Android Development] trmitche2:
Yes, that's what I meant, I used Odin to replace stock recovery with CWM6 and gained root in the process, and then apparently lost it when I installed this ROM, per your comments about changes in 4.3 that apparently change the game. I don't understand why more people who installed this ROM haven't mentioned losing root as well. Maybe its because of the method I used, which now seems like an outdated way to get root Using Odin, and even installing Kies (just for the required drivers if I remember correctly). I can't seem to find Tue thread that directed me to root that way.... Anyone else have a finger on that link, just for context, to help Cody better understand my predicament?
[Galaxy Tab 2 7" Android Development] CodyF86:
Yeah, the good news is that regardless, once you do the steps I posted you will have root access, and like I said i've done that procedure as recently as yesterday, so it does work. :)

Just ask if you run into any problems when you do it.

Also, here is the most up to date super user update: http://download.chainfire.eu/345/ I updated the OP also.
[Galaxy Tab 2 7" Android Development] trmitche2:
In the interest of laziness, (sorry man, now I've started drinking wine, not much though), can I use the download in this link to regain root *instead of* the (relatively) complex process you provided, requiring me to download the SDK to my laptop, etc.?
[Galaxy Tab 2 7" Android Development] CodyF86:
That's just version 1.51, I had 1.45 or something like that posted otherwise they are the same file. At this point you'll have to sideload to get root access back. It really isn't that bad. The SDK installs itself with the installer, and download the version without eclipse, there is a link farther down that says use with existing IDE.

You run the updater once it installs and your done you have adb, but you'll have to run the command from inside the adb folder (platform-tools) with full directory path names, or you can put the platform-tools directory in the sdk folder in your global path so you can issue the adb command from any directory. Either way, then you just issue the sideload command in recovery and the command line.
[Galaxy Tab 2 7" Android Development] shinobisoft:
Sorry for the OT but...

Just had to say Thanks :D Already gave thanks in the OP too ;)
[Galaxy Tab 2 7" Android Development] trmitche2:
OK, so per your change to the OP, this is exactly what I need to do, right? (I know I have the Samsung drivers installed already, since I installed Kies as part of the process to root 4.1.1): I'm not yelling with the bolded-caps, just trying to draw attention to my comments on each step.

How to gain root access on Android 4.3.

--------------------------------------------------

1. Download this SuperSU 1.51 update: http://download.chainfire.eu/345/ (OK, SAME LINK YOU GAVE ME A SECOND AGO, EASY ENOUGH)

2. Install the USB Drivers for Samsung Devices. (Google it.) (MAYBE LINK IT HERE ANYWAY?)

3. Install the Android SDK, so you have access to adb. (Make sure adb is in your global path. Google it.) (SUGGESTION: YOU MIGHT WANNA ADD THE LINK HERE THAT YOU GAVE ME ONE PAGE AGO, TO AVOID MORE QUESTIONS - A LOT OF FOLKS HERE HAVE NO IDEA WHERE TO FIND AN SDK OR HOW TO USE IT, EVEN WITH GOOGLE AT THEIR FINGERTIPS. THE TERM SDK IS INTMIDATING TO A LOT OF LURKERS, MYSELF INCLUDED)

4. Boot into recovery mode with your device attached via USB to your computer. (CWM6 REVOVERY RIGHT?)

5. Select install zip from sideload.(DOES CWM6 ACTUALLY HAVE A MENU OPTION THAT SAYS "Install Zip From Sideload"? I'VE ONLY NOTICED "Install Zip from SD card" OR "....External SD Card").

(Make sure ADB access is turned on in developer settings on your device!) (ALREADY DONE IN MY CASE)

6. Open up a command prompt on your computer and issue this command:

'adb sideload UPDATE-SuperSU-v1.51.zip' (Make sure your in the files working directory.) (WHAT IS THAT DIRECTORY? MY DEFAULT DOWNLOAD DIRECTORY? CAN I JUST MOVE IT TO C:\ AFTER DOWNLOADING IT?)

7. Reboot device, open up SU, and let it update via recovery if it asks.

(You have root access before updating, if it asks, but you should update if it asks!) (UNDERSTOOD THIS STEP NO PROBLEM)

8. Pat yourself on the back, your rooted. Enjoy! (YOU F*CKING ROCK WITH YOUR PATIENCE LEVEL HERE DUDE....)
[Galaxy Tab 2 7" Android Development] CodyF86:
Here is Samsung Kies, it has the samsung drivers included just install it, then once it's done uninstall it and it will give you the option to keep the USB drivers: http://downloadcenter.samsung.com/content/SW/201306/20130612104232657/KiesSetup.exe

Here is the SDK: http://dl.google.com/android/installer_r22.0.5-windows.exe (Run the SDK updater once it installs and update everything)

What I mean by working directory is you have to open up the command prompt and cd to the directory ADB is installed to if you don't add adb to your global path, which I tell you exactly how to do in my post a bit ago, go back and follow every direction step by step, your making it harder than it is. :)

Once you get adb in your global path you can open a command prompt and go to the directory the SU file is in and issue adb sideload filename. IF you don't put it in your global path youll have to change directory in the command prompt to the platform-tools directory adb is located in in the sdk directory and issue the same command but with the full path to the supersu file c:\blah\blah\blah\superuserfile.zip.

Make sure ADB is turned on under developer options on your device.

clockwork recovery 6.0.2.3 has the option to sideload at least here it is as a flashable zip you can flash from clockwork recovery, lol convenient. :)

http://d-h.st/XUq <== This is for p3113, if you have a different model, you'll have to search XDA for 6.0.2.3 for your device, if you don't have install from sideload, but you should.
[Galaxy Tab 2 7" Android Development] trmitche2:
Thanks, yes I have all these things already thanks to you - I was just suggesting that you update the OP again. I think I've asked as much of you as anyone could ever expect - thanks so much bro.
[Galaxy Tab 2 7" Android Development] CodyF86:
I'm putting it on the OP, the sdk and kies. :)
[Galaxy Tab 2 7" Android Development] CodyF86:
Oh hey one more thing,

If you have another device that runs android 4+ preferably 4.2.2+, as long as you have both devices are connected to the same network, you could use the second device to issue the adb sideload command instead of a normal computer.

Make sure adb over wireless is turned on in developer settings of the device you want to connect to. Get the IP address of the android device you want to connect to along with the port number. Both are listed under that option in developer settings.

You can issue from a terminal emulator on the second device 'adb root' to make sure adb is in root mode, then 'adb connect (ip: port)' to connect to the other android device on the network.

Type into the terminal 'adb devices', if there is only one device listed then you can issue adb sideload /path/to/file/filename.zip (You click install from side load in recovery first, then this command.)

If there are two devices listed you'll have to add the device name of the device you want to send the sideload command to as listed by 'adb devices' first. so: adb device-xxx sideload /path/to/file/filename.zip.
[Galaxy Tab 2 7" Android Development] CodyF86:
Here is 20130813 for p3110 / p3113 w/IR: http://d-h.st/sXy

NOTE!!!: Great news starting with this Build. The newest Samsung Ducati firmware blobs have been merged.

This means that even on the stock kernel you have the updated firmware blobs and if you use

BlackHawk-NEXT Kernel 1.8.2, you no longer have to flash the vendor-blobs-new-ducati-blackhawk.zip

file after installing his kernel like you normally would have to! You already have the newest firmware

blobs installed!

I'll add this to the OP.

TabletUI patching is still broken; Got another looped systemUI FC with it, so like I said, will just have to wait for an update for

ApG / Auto-Patcher.
[Galaxy Tab 2 7" Android Development] CodyF86:
Here is 20130813 for p3100: http://d-h.st/vVr
[Galaxy Tab 2 7" Android Development] trmitche2:
I plan to test your new root instructions today from work. Thanks again.

Has anyone using these builds been able to apply any themes that worked for CM10/10.1? Or, as with rooting, has something major changed in that department as well, requiring us to wait for the rest of the Android world to catch up to 4.3? I find myself afraid to even download, let alone apply, any of the themes for theme builder from the Play store, even though I imagine that the worst case scenario would be reverting back to stock theme, or throwing an error that stops me from applying a custom theme in the first place. Cost of being on the bleeding edge I guess - no complaints here, just curiosity. I have been using BetterBean's red/blue CM10/10.1 themes on my good ole' Sprint SGS II (A.K.A. "Epic 4G Touch") phone, and would love to gain consistency between both devices. I believe I *may* have tried to apply one of the BB CM10.1 themes the night I first installed this ROM (on 08/09, when I grabbed the most recent stable release), and I seem to remember it failing. Any feed-back from anyone who's has tried (successfully or not) to apply any themes through theme builder (or any other inverted apps, etc.)

Thanks.
[Galaxy Tab 2 7" Android Development] Zelmo88:
Running the 8/13 build on my 3113....working great! Very fast and smooth and nice to have IR back again! Great work Cody! My try to flash Blackhawk kernel this evening and see how that works. It will be nice not to have to flash the blobs!