[Galaxy Note 3 General] dabgoo:
Installing Google Apps on a N9002

Below is a quote from a post that was in the old Dual SIM N-9002 thread.

============

Installing Google Apps

This was the tricker part, since to maintain Knox 0x0 after using URDLV to root, CWM and other custom recovery systems cannot be added to allow for flashing the the Google Apps .zip file. For most of the other Note 3 versions this isn't a huge issue, since Goggle Apps is already installed, but for the N9002, we know that Google Apps is specifically excluded, which presents us with an issue of how to get Google apps onto phone without being able to use CWM to flash the .zip file. Here are the steps:

1. Unzip the Google Apps .zip file on your computer and copy the folder "/system/app" onto your device (either internal or external SD card), you will use shortly

2. Now that your phone is rooted, you need to install the a file explore that will allow you root editing access to your file system so you can install the Google Apps files. I recommend ES File Explorer. You will need to get the ES File Explorer .apk file to put onto your device (e.g., via SD card or USB). I found a link somewhere on xda for the .apk file, but this version must have been an older one that isn't compatible with 4.3. So I downloaded the app Apk Extractor from Play onto my Note 2 and extracted the .apk from the latest version of ES File Explorer that is on my Note 2, then moved that .apk to my Note 3 and installed...it worked fine. If you don't have another device to do this, I'm sure you can find the .apk somewhere out there on the web, you'll just need to hunt around. The current ES File Explorer version is 3.0.6.0.

3. Now you will want to move the necessary Google Apps files onto your device, but before doing this, you will need to permission ES File Explorer root explorer access. Within the app, hit the left device button and turn "Root Explorer" on. Then click on "Root Explorer" and hit "Mount R/W" and ensure "/system" falls under the category "RW".

4. Within ES File Explorer, copy the following files from the Google Apps folder you copied over earlier onto the root system of your device at "/system/app":

OneTime Initializer.apk

GoogleLoginService.apk

GoogleServicesFramework.apk

SetupWizard.apk

Gmail.apk

5. Now, within ES File Explorer, long press on each of these files that have been copied over and hit the soft key "More" then "Properties" then hit "Change" related to the "Permissions" category. Make sure that only the following are checked:

Owner: Read and Write

Group: Read

Other: Read

When you hit "Okay" and it exits that screen, the permissions should look as follows: rw- r-- r--

Repeat for each file copied over earlier.

6. Reboot device and login to Gmail

7. Copy the following file to the same location in Steps 4 and repeat the process in Step 5 for the file:

Phonesky.apk

This is your Google Play file. Once this is loaded reboot.

8. Now you should be able to start loading up all your files from Play; however, we still need to copy some files over to allow for syncing of contacts, calendar, etc. Copy and repeat the some process above (Steps 4 and 5) on the following files:

GoogleContactSyncAdaptor.apk

GoogleCalendarSyncAdaptor.apk

Reboot

9. You should have complete functionality of your system now with Google Apps. There are a number of other files from the original Google Apps .zip file, but I cannot tell you which are actually critical or not--I haven't loaded them and my device seems to work fine. I believe once Play is installed, some of these files may actually be installed as updates anyway and/or be loaded as apps from Play (e.g., Google Search, etc.). Also, you will want to load any other desired Google applications, such as Maps, through Play.

10. Enjoy Google Apps! Let me know if you have any issues and I will try to back-step through what I did to help you or see if I overlooked a step. Just be patient and know if you haven't gotten there yet, there is always a way!

Removing Chinese Bloatware

I would just follow the same instructions as outlined by Marrk Daviid under Part 3 of his page: http://marrkdaviid.com/2013/10/insta.../#.UoxXtNNp7WV

Follow Up

Let's provide necessary feedback to each other here. Those of us with these locked down systems need to support each other! This took a while for me to figure out, but I hope it can help others. Please his "thanks" if this posting is helpful!

A few more things to hopefully provide some clarity/help:

1. Once again, as stated originally, when using odin to flash the patched URDLV file on the device, use the AP slot only (this assumes a "full" file was created using the "URDLV full c:\" command)

2. When installing ES File Explorer, this is done by clicking on the .apk file you have copied over and selecting "install"; HOWEVER, when I refer to all the Google Apps files, these are copied over and the permissions are changed, but do NOT install by clicking on the .apk files. Simply by following the method of: a) copying the files directly to the "/system/app" folder; b) changing the permissions; and c) rebooting the device, these apps will be installed. For the user interface apps like Gmail and Play, you should see their icons in the Apps section after reboot.

3. For those of you outside the US market (in countries where Google Play doesn't show all apps) one additional thing you may want to do is install Market Unlocker after copying/fixing the Google Play ("Phonesky.apk") file and rebooting, but prior to actually launching Google Play for the first time. Here's a link below to one source for the .apk, although I can't attest to the veracity of the source (e.g., potential for malware, etc.). There are links all over out there for different versions since Google removed it from the Play store a while back. (I personally had an old copy that I had used to install on my Note 2 and I just used it to install on my Note 3, which worked fine.) Once installed, you can select and activate AT&T or T-Mobile as your market carrier and you will be good to go.

=================

ADB

When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.

This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.

This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.

If you haven't this pop-up mesage in your device, there is the solution :

1) Install SDK in your PC

It may asks you to install JAVA, if so, do it.

2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window

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

After that you every thing will be OK

First, make sure adbd is running as root:

adb root

If you get an error that says something like "unable to run as root on production builds" it means that you must always issue su command in the adb shell to gain superuser privileges. You will need to enter the shell before any mount commands will work. You will need to push the file to the SD Card, then mount /system partition as read-write, and then copy the file to the /xbin directory like so:

adb push [path-to-iwconfig] /sdcard/

adb shell

su

mount -o remount,rw /system

cp /sdcard/iwconfig /system/xbin/

mount -o remount,ro /system

exit

exit