Database Users

[HOW TO] enable non market apps

I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.

That's not how it works. When you use the option in SuperOneClick, it enables that option for you, even if it doesn't show up in settings>applications.

Thanks. When using SuperOneClick I was able to root, but I wan't able to allow Unknown Sources through Settings->Applications.
Now it works!

thanks, sideloading didnt work for me using aroot.

i rooted using SOC a while ago, and DLed the official PSN apk yesterday since it's not on the US market, and installed it by clicking the apk in file manager with no problem.

Thank you so much! This finally worked! Using aRoot/GladEnable/SuperOneClick , all of them SAID it was enabled but it clearly wasn't ... when I navigated to the db field it was still at '1' .. thanks for this, finally it's working

i am on gingerblur, and when clicking the menu button i don't get a dialog to do anything. Maybe a bug of the theme?
So i can't use root explorer to do this, but anyway this is useful since now i know the database name and can do it by hand...

For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done

franciscojavierleon said:
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
Click to expand...
Click to collapse
I tried this and it did not work just said sqlite3 not found. Type exit and type exit then type sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" it just locked up terminal. If I type sqlite3 before adb shell it finds it.
Used root explorer and copied settings.db to sdcard. Once there used as a disk drive on computer. Edited it with navcat for sqlite and saved it. Then disconnected it for computer used root explorer and copied it back to data and overwrote existing file. Rebooted and all was fine.

I did everything, but I am not able to edit the field...
"Thanks

manpreet14 said:
I did everything, but I am not able to edit the field...
"Thanks
Click to expand...
Click to collapse
thanks much
i got it

BravoMotorola said:
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
Click to expand...
Click to collapse
Thanx. Very useful info.

Worked for me.
Thanks

Works Great. Thank you!

is there a way to enable side loading with out rooting the phone?

aszrael1266 said:
is there a way to enable side loading with out rooting the phone?
Click to expand...
Click to collapse
sideload wonder machine. look it up. pretty easy.

BravoMotorola said:
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
Click to expand...
Click to collapse
Thanks for this instruction...

Even though this thread is a little old it did help me and therefore want to add my two cents worth to possible help others who may be having issues. I have a rooted Motorola Flipside.
I purchased SQL Lite Editor from the market and was able to change the value directly in it. Here's how:
1. Download and install SQL Lite Editor from the market.
2. Start SQL Lite Editor to display a list of the applications installed on your device.
3. Look for the application titled Settings Storage (and in smaller print underneath it will display "com.motorola.android.providers.settings".
4. Select Settings.db.
5. Select Settings.
6. In the list of columns scroll down to item #70, "force_only_market_apps" and select it.
7. Click the shortcut menu on your device and select Edit Record.
8. Change the value from 1 to 0 then save and exit SQL Lite Editor.
9. Go to Settings > Applications. Unknown Sources will be visible and you will be able to check it.
Hope this helps anyone else who has issues.
Regards,
Greg

franciscojavierleon said:
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
Click to expand...
Click to collapse
You are awesome buddy.. thanx

[Q] Rooted 1.2, can't install apps (and other issues)

Hi,
I rooted my Nook 1.2 with ManualNooter 4.5.6 and have it running at 1.1GHz. Have some issues and was wondering if I can get some help.
How do I install non-market apps? I went to the amazon page and was able to download the Amazon_Appstore-release.apk. When I click on it, I get a choice of App Installer and Package Installer, neither of which works. I've tried unchecking and checking "Allow Non-Market Apps" in Nook Tools, but it still didn't work. It notes that the apk must be copied to /system/app...how do I do that?
I've installed SetCPU (full version) from the market and set max to 1100. SetCPU seems like it can do so much more, but I'm hesitant to mess anything up. Anyone willing to share their settings?
When looking through the Battery Use stats, I noticed that Cell Standby is using up 49% battery, and Phone Idle another 2%. Is there some way to set airplane mode or something to disable those?
Thanks,
kftgr

Easy solutions (although they take some steps). I've done both of these.
Amazon App Store:
* Download to your PC
http://amzn.to/getamazonappstore
* Put the apk onto your sdcard.
* Use a File Manager that will give you Read/Write access. I use SUFBS, so I'll give instructions for that.
Open SUFBS, rotate your nook on it's side and click the S and the D in the upper left hand corner. For whatever reason, at least on my Nook, it must be in landscape to be able to click the S.
* Navigate to the Amazon App Store apk. In my case, it was /sdcard/Amazon_Appstore-release.apk
* Click on it, click "Install", click "Package installer".
It should install, and ask you to log in.
DONE!
For the Cell Standby issue, you need to rename two apk's, you can do this in ADB, but since we're in SUFBS anyway:
* Navigate to /system/app
* Long Press "Phone.apk" until a menu pops up
* Select "Rename", rename it to "Phone.OLD"
Next, still in /system/app
* Long Press "TelephonyProvider.apk" until the menu pops up
* Select "Rename", rename it to "TelephonyProvider.OLD"
REBOOT
DONE!
If you ever want to turn those two back on, just replace .OLD with .apk and reboot again. It will make a difference in your battery life. Let me know if you have any questions. Good luck.

I downloaded the Amazon App store apk and have tried to install it, but whenever I do I get a Parse Error, "There is a problem parsing the package"
Edit: This happens whenever I try to use the Application Installer first, then the Package Installer. I've rebooted the machine and tried just using the Package Installer and I get a error saying my phone has been set to only allow applications from the market to be installed. I've verified that in the Nook Tools the "allow non-market apps" checkbox is checked. I even unchecked it and rebooted and it was checked when I went back into the Tools.

KWKSLVR said:
Easy solutions (although they take some steps). I've done both of these.
Amazon App Store:
* Download to your PC
http://amzn.to/getamazonappstore
* Put the apk onto your sdcard.
* Use a File Manager that will give you Read/Write access. I use SUFBS, so I'll give instructions for that.
Open SUFBS, rotate your nook on it's side and click the S and the D in the upper left hand corner. For whatever reason, at least on my Nook, it must be in landscape to be able to click the S.
* Navigate to the Amazon App Store apk. In my case, it was /sdcard/Amazon_Appstore-release.apk
* Click on it, click "Install", click "Package installer".
It should install, and ask you to log in.
DONE!
Click to expand...
Click to collapse
I couldn't find SUFBS in the market, so used Ghost Commander and was able to install the apks with your instructions. Thanks!
KWKSLVR said:
For the Cell Standby issue, you need to rename two apk's, you can do this in ADB, but since we're in SUFBS anyway:
* Navigate to /system/app
* Long Press "Phone.apk" until a menu pops up
* Select "Rename", rename it to "Phone.OLD"
Next, still in /system/app
* Long Press "TelephonyProvider.apk" until the menu pops up
* Select "Rename", rename it to "TelephonyProvider.OLD"
REBOOT
DONE!
If you ever want to turn those two back on, just replace .OLD with .apk and reboot again. It will make a difference in your battery life. Let me know if you have any questions. Good luck.
Click to expand...
Click to collapse
Could you provide the adb instructions? I already have the sdk installed.
I tried the renaming steps in Ghost Commander, but the new name doesn't stick, even though it's been given root.

@r0n1n69:
Just use the steps that KWKSLVR provided. Basically: get a file manager that provides read/write access, navigate to the apk, then install with "package installer."

kftgr said:
Could you provide the adb instructions? I already have the sdk installed. I tried the renaming steps in Ghost Commander, but the new name doesn't stick, even though it's been given root.
Click to expand...
Click to collapse
Try:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot

I've installed FileExpert and given it root permission, but I still get the "can only install from market" error whenever I try to install a package from my sdcard. In this case I'm trying to install mobo player, if that makes a difference.

KWKSLVR said:
Try:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
Click to expand...
Click to collapse
Thanks much. Pretty much doubled my battery life

kftgr said:
Thanks much. Pretty much doubled my battery life
Click to expand...
Click to collapse
So what? I enter in that string of text in where? and it doubles battery?

[ROOT] With working PlayStore Google Apps + Custom Launcher + superSU

###YOUTUBE VIDEO WILL BE UP SHORTLY###
###ALSO THE GUIDE WILL GET MORE DETAILS AND INFORMATION IN A SHORT PERIOD OF TIME###
###Before you ask, i use Quote instead of Code to NOT cut of the Code###
Requirement:
- Fire Tab 6" or 7" 4th Generation
- be patient
- be Aware - things can go wrong, if ANYthing is unclear, please ask first!
- Around 30~ to 60~ Minutes
depending how fast you get ADB and everything else required to get to the initial Root.
IF you already using ADB with your Fire, Check Step 3, THEN go to Step 7
Hi there,
In this Tutorial you will learn how you can root your Amazon Fire HD 6" or 7" Tablet.
First we are going to root it using Kingroot, after thet we Sideload SuperSU Root.
Please note this Tutorial requires the 4th(!) Generation of Fire Tabs.
Error-Solutions are at the BOTTOM of this Document!
NOTE: This Tutorial includes:
-Install ADB using Android Studio (also Windows 8, 10)
-Disable Fire Tab Ads
-Connect to Google
-Install Google GAPPS
-Install Custom Launcher
-Replace Default FireLauncher with Custom Launcher
-Root Device
-Sideload superSU, replace Root
-Install Google Store
-Implement Google Service as System-Apps
-Block Google-Phone-Home, AutoUpdates
Step 1:
Download the required Files (~180 MB)
Link: https://drive.google.com/file/d/0B5zOo5KIf0WdSVZKUllhQm85alk/view
Step 2:
Get Android Studio (FULL Install ~800MB)
Check the Android Studio Dir this ZIP contains and execute "Get AndroidStudio.lnk"
Step 2.1:
- After installing Android Studio launch it, click "Configuration" and Select the SDK (first Option)
- Select "Tools" at the Top and click "Manage Add-on Sites"
- Click the "User Defined Sites" Tab and click on "New..."
- Paste this URL:
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
- confirm with "OK"
- Close this Window after and go back to the Mainwindow "Android SDK Manager"
Step 2.2:
- Scroll down until you see the "Extras" Folder, select "Kindle Fire USB Driver"
TIP: Click "Deselect All" first and reselect "Kindle USB Driver" so you don't have to install the Whole Package.
- Click "Install x packages..." after and wait until it's installed. After it's done you can close the SDK Manager Process.
Step 3:
- Open the Android SDK Main Dir wich is located for ex:
C:\Users\<USERNAME>\AppData\Local\Android\
Click to expand...
Click to collapse
- Enter "android-sdk\platform-tools"
- Copy the Content from "APT" Dir to this Folder, for ex:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- Go back to the Mainfolder and enter "sdk\extras\amazon\kindle_fire_usb_driver"
Step 4:
- Open your Devicemanager (Controlpanel > Devices > Devicemanager) and connect your Fire Tab to the Computer
- Open the Internal Storage of your Fire Tab and go to "Download" Dir at, copy & paste the whole Content from APK Dir to Fire Tab's Download folder.
Step 5:
- Open "Settings" at your Fire Tab Device and select "Applications"-Tab, enable Third Party Application.
- Go back to Settings and go to your Device Propertys, now tap the "Serialnumber" Field until you enable the Dev-Mode.
- Enter Developersettings and enable "ADB" at the "Debugging"-Tab.
Step 6:
- Now (you are still at the Devicemanager) select the "Fire", it should be displayed as a protable device.
- Rightclick it and select "Uninstall".
If there is any other Kind of "Fire" you should install them, too.
Do NOT close the Devicemanager now.
###
---If you use Windows 8 or 10 - go to the Bottom now to see what you have to do instead of the following---
###
- Unplug your Device now and Run (As Admin) the "KindleDriver.exe" at your Amazon Folder located at AndroidSDK
- Install it (should give you a green tick if everything was correct)
- After you installed it - connect the Fire Tab again.
- If your Fire Tab Fire is not marked as "ADB Device" repeat
Step 7:
- Now ADB and your Fire Tab are ready to get tested.
- Your Fire should already be connected to your device, if not, do so.
- Run a Command Prompt (Win+R and type "cmd" without ")
- now first go to your Android AD Location wich should be by default:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- After you found the correct dir, copy the Path, go to your Command Prompt, paste it with "cd " in Front of it.
cd C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
###NOTE: All ADB-Commands are single-lined Commands.
Even if there are empty lines between them, it's just for better orientation.
Each command has to be added, one by one!
Step 8:
- Now you should be at the correct Dir, write
adb kill-server
Click to expand...
Click to collapse
Then
adb start-server
Click to expand...
Click to collapse
- The Server should start now, after it's online write
adb devices
Click to expand...
Click to collapse
- Your Device should now be displayed at the Prompt, if it says "Unauthorized", check your Tab, accept the Message and type again
adb devices
Click to expand...
Click to collapse
- It should now be displayed as "device"
Step 9:
- Enter
adb shell
Click to expand...
Click to collapse
at your Command Prompt
- Now let's make connection with Google.
- Enter the following command and accept with Enter of course
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
Click to expand...
Click to collapse
---Optional: to Block Ads from the Lockscreen menu type this:
pm block com.amazon.kindle.kso
Click to expand...
Click to collapse
Step 10:
- Go to your device and run Amazon Appstore look for "ES File Explorer" and install it.
- After that, we are starting to Install GAPPS.
NOTE: After each App, REBOOT your device and install the next one!
- Open ES File Explorer and go your "Download" Folder.
- Install the Apk's in this Order, don't forget to reboot:
Google Account Manager
Google Service Framework
Google Play Services
Google Play Store
Click to expand...
Click to collapse
- Now you can Create your Account and Log-In if you like
- After this Step, you do not need to reboot after the next APKs.
Google Play Games (also Create Acc/Login if you like)
Aptoide
VireLauncherPro
RootChecker
KindleReader (The default one may not work anymore)
Click to expand...
Click to collapse
Step 11:
- Back to adb Shell Prompt, we are going to Block our Amazon Default Launcher, type
pm block com.amazon.kindle.otter
Click to expand...
Click to collapse
- Now just Launch VireLauncher and mark it as default if it asks for.
- Now we got what we need to proceed for our root.
-----------IMPORTANT: In order to make sure all Amazonapps are Still working after the initial Root
-----------It is recommend to run all Amazon Apps you are going to use even once (MOST important after factory Reset)
Step 12:
- UNPLUG your Fire Tab (IMPORTANT)
- Open your ES File Explorer at the Download Tab and install
KingRoot-4.0.0.233-release-201505071219_105001
Click to expand...
Click to collapse
- Run KingRoot and tab the blue button at the bottom
- Now KingRoot is going to root your device, the device restarts during this Process.
- After the Device restarted.
- Click the Check Button (Top right Corner) and scroll up, it should say rooted, if NOT - restart KingRoot again and Root again.
Step 13:
- Go back to our Commandprompt (if you are still in ADB Shell, type "exit" first) and now excecute those Commands
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
Click to expand...
Click to collapse
- Now simply type
su
Click to expand...
Click to collapse
- now the following commands one after another, remember each command is a single line!
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Click to expand...
Click to collapse
Leave the ADB Terminal for now and go back to your Device, open the KingUser App
Click at the Top Right Corner on the Screen, click the Root authorization Settings and Remove Root Permission.
go to Settings > Application > All Applications/Third Party and uninstall the other King Applications (KingRoot and a Chinese one)
Go back to ADB now and enter the following commands one after another:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Click to expand...
Click to collapse
Step 14:
- leave the ADB Terminal again and open your ES File Explorer
- Install superSU now, then run it and let it update after that reboot your Device
- Leave the Device for around 5 Minutes after Reboot.
- Now run your RootChecker and click the Checkbutton at the Top right, and scroll up again, it should say "rooted".
Step 15:
- Go back to ES File Explorer but leave ADB open as always, Install
SysAppConverter
Click to expand...
Click to collapse
- Open the SysAppConverter after and add the following things to your "System-Apps"
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Click to expand...
Click to collapse
Step 16:
- After you have done this, go back to ADB Shell and stop them from Phoneing home
pm block com.amazon.otaverifier
pm block com.amazon.dcp
Click to expand...
Click to collapse
Also enter the Playstore, top right corner -> uncheck autoupdate
Swipe to the right, click Settings and also disable autoupdates.
Finally, you are ready and your Device is rooted including Access to Google Playstore
IMPORTANT: If Apps or Playstore should not work because of reasons, there is a simple trick just reset your Google Frame Services.
Open SystemAppConverter
Browser for "Google Play-Services" (The Puzzle Piece) and hit the "System" button to the right.
Now select "Remove Updates". Now wait around a minute. Try if it works, if not - restart the Device.
Sometimes the Screen can Flash or the Tab will just shut down.
-------------------------------------------------------------------------
WINDOWS 8
Go to the Windows 8 folder, There is a tutorial how to install ADB on Win 8, then back to Step 7
WINDOWS 10
Click this Link: http://pdanet.co/a/
Download PdaNet+ "Version 4.18 installer for Windows" for ex.
If you haven't done yet, unplug your Fire Tab and install PdaNet.
After you installed it completly ADB should be ready now.
Go to Step 7
-------------------------------------------------------------------------
###VIRE SETTINGS###
#Launcher Settings#
Enable reflections - y
Lock Home screen - n
Themes - Stock
Home transition style - Crystal
Advanced Features - include Wallpaper - y
" - Full Screen Transitions - y
" - Enable Frame
" - Enable HD Shaders - y
" - Enable infinite Scroll - y
" - Homescreen - iconlabelsize - large
Icon
Show icon Shadow - y
Icon Style - none
Icon pack Settings - None
Homescreen - Add App - Vire App - Clock
Click to expand...
Click to collapse

thanks for this- tried to download the link in Step 1 but the google drive link is protected. I requested access- email has "ben" in it, just hoping to try this out on my hd7.

I'd REALLY like to be able to follow your guide here, but...
Unfortunately I can't advance past the first couple steps because the google drive link posted in STEP ONE containing all the necessary files requires permission from you before I can download it.
Once you fix this, this guide will really help everyone.

Hell i'm sorry i updated the Link! Going to edit soon, there are a lot of parts pretty undetailed.

thank you, it's downloading for me now

Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.

Step 7 CMD window - suggestion for noobs
vismxownz said:
Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.
Click to expand...
Click to collapse
Wow! Thank you SO much. Step 7 might be a little unclear. Not sure "first copy the Android ADB Location" -- copy from where?-- and then "write to your Commandprompt" cd (ADB location)" -- do you mean write "cd" (no ") and paste what you copied? Just a thought . . .
Think it would be simpler to just open CMD window from adb.exe folder::
1. Open the folder containing adb.exe. (Should be C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools)
2. Hold down the shift key and right-click a white space in the folder. Choose "open command window here."

also for step 2.1 i wasn't able to get the fire SDK listed in the android SDK manager until i added the following URL
https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml

I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...

bibikalka said:
I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...
Click to expand...
Click to collapse
First I want to say thank you for the instructions this is a more detailed version of the steps I was taking. I had full intention to clean up my guide once we solved the problems we are currently having. I'm pretty sure these steps above are the basic steps of getting the Playstore but we are still not without issues. I'd be interested to see how many people this is working.

After all that, i still dunno why People got still issues - in first place with PlayStore.
It's the 6th (and 5th Day) for both HD 7" - still everything is working - PlayStore, also downloads and Cache Cleaning like a charm.
Also the Tablet seems to work faster now, cause of disabled Amazon Startup-Apps.
Also bibikalka is right, there are less big downloads, also you can evade downloading the whole SDK if you do not like, to. But you safed it for Future uses and instructions.
Also my first DL is above 100MB because it also includes the GAPPS, they are working as said and still working after nearly a week of usage on 2 Fire Tabs.
Just wanted to help, not that pro in writing instructions as you may already know.

But after all this, is Play Store application working?

devicer said:
But after all this, is Play Store application working?
Click to expand...
Click to collapse
As said before, nearly a week without any problems. Applications updating fine (for sure execluding Google Apps, don't updating anymore) - they should work until there is a update wich REQUIRES a newer Version of any GAPPS. But as said they work.

Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.

droidnext said:
Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.
Click to expand...
Click to collapse
Yes the GoogleCode got Patchday and 034 got patched. BUT to evade you also can go to your SysCustomizer and Reset the Google Play-Service to "Systemdefault" so it resets back to the first installed version. Until this gets a problem you can do it over and over again, so it would take just like 1 minute to fix the issue. Also there is no error or fail in using an "outdated" Version. Thanks for your Sharing i updated my uploadings

Everything is working now, and does not self update, see here :
http://forum.xda-developers.com/fire-hd/general/root-play-store-short-disabled-self-t3113975

Anyone else have problems setting up supersu?
Sent from my LG-V480 using Tapatalk

I'm waiting for the tuto video
thanks for the work btw !!!

Wich Problems?
greetings

So if we want the Google play store, we won't be able to use the default launcher anymore ? damn it ...
is it an obligation ?

[ROOT] VZW Note 7

First thanks to freeza and goonygugle
this is freezas method with a few adjustments from goonygugle and a little extra steps to get data on vzw
Files needed
You also need adb for this process if you dont already have it
Leaked Sprint Rom: https://www.androidfilehost.com/?fid=24651430732236681
Odin and verizon firmware, courtesy of Misterxtc
Sun7 Files: https://www.androidfilehost.com/?fid=24651430732236679 unzip this zip into a normal sun7 folder. Put the new sun7 folder into the folder that holds your adb file!
1) After downloading all the files unlock developer mode and enable usb debugging
2) Put the phone into download mode (vol-, Power, Home)
3) Connect the phone to the computer and open oden
4) Click AP and select the sprint file, wait for it to load and flash
5) The phone will reboot and go through a update process. when you get to a black screen force the phone into download mode again (for new settings menu allow first boot ~30mins then put into download mode)
6) Flash BL, CP and CSC in odin from the verizon firmware
7) After the flash it will be a long wait for first boot ~30mins (Can disconnect from computer)
8) You can skip setup. Go to settings and unlock developer options again and enable usb debugging
9) Plug the phone back in and don't forget to change from charging mode to file transfer
From freeza's post
10): Open a command prompt where your ADB executable and sun7 folder are.
11): Verify standard root access by typing "adb shell" then "su" If successful, type "exit" twice to get back to the command prompt.
12): Push the sun7 folder to your phone by typing "adb push sun7 /data/local/tmp/su"
13): Change permissions of contents in su to 777 by typing "adb shell chmod 0777 /data/local/tmp/su/*"
14): Launch adb shell by typing "adb shell"
15): Change directory to su by typing "cd data" "cd local" "cd tmp" "cd su"
16): Gain standard root privileges by typing "su"
17): Execute the SU script by typing "./root.sh"
Phone will reboot and you will have root but this leaves verizon without access to data
18) You will need a root explorer
19) Download stock verizon apn settings https://www.dropbox.com/s/x7m9v49a2eytmid/apns-conf.xml?dl=0
if you want to use different carriers download nexus 6p apn settings(includes verizon apn) https://www.dropbox.com/s/jqz3ps8xq492k8l/apns-conf.xml?dl=0
20) Copy the apns-conf to the phone
21) In a root explorer locate the apns-conf file you just transferred. Copy/Move it and navigate to system/etc
22) Delete that original apns-conf file in system/etc (contains sprint data info) and past the one you copied
23) Change the permissions to rw-r-r
24) Navigate to /data/data/com.android.providers.telephony/databases/ and delete telephony.db
25) Reboot your phone and everything should be up and running
Now you have a Samsung stock Note 7 with the only thing from Verizon being the network!

As of now stock messenger doesn't work for MMS, just use another messenger instead
Reboot requires any bluetooth devices to be paired again
Samsung cloud fix from jeffbob48
jeffbob48 said:
Here is the fix for samsung cloud https://mega.nz/#!v5JTFBwT!FAXwgY6VTGceerWJmt2pQ0xQEh07yiNw4AxNCPnAv10
1. Download zip and unzip it to storage of phone ( Do Not Flash... this zip cannot be flashed in any way)
2. copy file from zip to /system/omc/VZW
3. make sure it overwrites the old files
4.check to make sure that the permissions of all the files are rw- r-- r--
5. etc folder does not need to be changed, do not touch anything in etc folder
6. after you set the permissions reboot the phone
7. go check settings for samsung cloud now
Any donations would be much appreciated lol i worked really hard on fixing this for you guys and i have more fixes to come
Click to expand...
Click to collapse

Thanks for the Guide. I will give this a shot this weekend and see what happens.
~SG

Pit file
Is there an advantage to using the pit file? Under what circumstances would we need this?

coton said:
Is there an advantage to using the pit file? Under what circumstances would we need this?
Click to expand...
Click to collapse
I don't think so, I've dont it both ways. didn't notice a difference

Does this affect or trip Knox? Can you still use Samsung Pay and other Knox reliant apps when Rooted? The last Samsung I had was a Galaxy S3 and it was rooted long before Verizon enabled the Knox 'feature'.

Data fix didn't work for me. I'll have to run back through to see if I did something wrong.

azradiohead said:
Does this affect or trip Knox? Can you still use Samsung Pay and other Knox reliant apps when Rooted? The last Samsung I had was a Galaxy S3 and it was rooted long before Verizon enabled the Knox 'feature'.
Click to expand...
Click to collapse
Does not trip knox. NO you cannot use Android Pay or Samsung Pay if rooted. Same with other apps such as Playstation Vue, Snapchat, etc.

Has anyone noticed any signal issues or anything? I haven't gotten a chance to run it yet.

jal3223 said:
Has anyone noticed any signal issues or anything? I haven't gotten a chance to run it yet.
Click to expand...
Click to collapse
I don't have any

Verizon SM-N930V Root Verified
LRiley said:
First thanks to freeza and goonygugle
this is freezas method with a few adjustments from goonygugle and a little extra steps to get data on vzw
Files needed
You also need adb for this process if you dont already have it
Leaked Sprint Rom: https://www.androidfilehost.com/?fid=24651430732236681
Odin and verizon firmware, courtesy of Misterxtc
Sun7 Files: https://www.androidfilehost.com/?fid=24651430732236679 unzip this zip into a normal sun7 folder. Put the new sun7 folder into the folder that holds your adb file!
1) After downloading all the files unlock developer mode and enable usb debugging
2) Put the phone into download mode (vol-, Power, Home)
3) Connect the phone to the computer and open oden
4) Click AP and select the sprint file, wait for it to load and flash
5) The phone will reboot and go through a update process. when you get to a black screen force the phone into download mode again
6) Flash BL, CP and CSC (I've dont it with and without the pit file) in odin from the verizon firmware
7) After the flash it will be a long wait for first boot ~30mins (Can disconnect from computer)
8) You can skip setup. Go to settings and unlock developer options again and enable usb debugging
9) Plug the phone back in and don't forget to change from charging mode to file transfer
From freeza's post
10): Open a command prompt where your ADB executable and sun7 folder are.
11): Verify standard root access by typing "adb shell" then "su" If successful, type "exit" twice to get back to the command prompt.
12): Push the sun7 folder to your phone by typing "adb push sun7 /data/local/tmp/su"
13): Change permissions of contents in su to 777 by typing "adb shell chmod 0777 /data/local/tmp/su/*"
14): Launch adb shell by typing "adb shell"
15): Change directory to su by typing "cd data" "cd local" "cd tmp" "cd su"
16): Gain standard root privileges by typing "su"
17): Execute the SU script by typing "./root.sh"
Phone will reboot and you will have root but this leaves verizon without access to data
18) You will need a root explorer
19) Download verizon apn settings https://www.androidfilehost.com/?fid=95916177934521717
20) Extract that file and go to vzw-APNfix>system>etc and copy the apns-conf to the phone
21) In a root explorer locate the apns-conf file you just transferred. Copy/Move it and navigate to system/etc
22) Delete that original apns-conf file in system/etc (contains sprint data info) and past the one you copied
23) Change the permissions to rw-r-r
24) Navigate to /data/data/com.android.providers.telephony/databases/ and delete telephony.db
25) Reboot your phone and everything should be up and running
Now you have a Samsung stock Note 7 with the only thing from Verizon being the network!
Click to expand...
Click to collapse
I can verify this works.

AstonsAndroid said:
I came to the same place by flashing Verizon CSC immediately after the Sprint AP. I did not allow startup in between. Everything booted up on Verizon without activation or additional work. I can verify this works.
Click to expand...
Click to collapse
Just the CSC file after the AP, or did you do all three?

nu2droid said:
Just the CSC file after the AP, or did you do all three?
Click to expand...
Click to collapse
I only had to flash the VZW CSC immediately after the Sprint AP by holding "volume down+Home" during the Sprint Odin reboot, then add VZW CSC.
After which you will boot up on Verizon network with a Vanilla Note 7. No Verizon bloat! Follow the ADB Root instructions in this thread and be happy!

Cool. Thank you sir.... trying now
Sent from my SM-N930V using Tapatalk

AstonsAndroid said:
I came to the same place by flashing Verizon CSC immediately after the Sprint AP. I did not allow startup in between. Everything booted up on Verizon without activation or additional work. I can verify this works.
Click to expand...
Click to collapse
can you edit apn settings?
can you activate wi-fi calling?
can you go into Privacy and emergency>emergency alerts?

MrBaltazar said:
Does not trip knox. NO you cannot use Android Pay or Samsung Pay if rooted. Same with other apps such as Playstation Vue, Snapchat, etc.
Click to expand...
Click to collapse
Will the 2 ever co-exist? Will there ever be root and Android/Samsung Pay that work together?

nu2droid said:
Cool. Thank you sir.... trying now
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
Lmk if this works. If so I'll add it into the guide

LRiley said:
can you edit apn settings?
can you activate wi-fi calling?
can you go into Privacy and emergency>emergency alerts?
Click to expand...
Click to collapse
No to all three questions!

AstonsAndroid said:
No to all three questions!
Click to expand...
Click to collapse
Cool same across the board then. That's the reason for the extra part, couldn't change apn. If your method works for another person then I'll add it into the guide. Always good to have more than one way

Hdhntr23 said:
Will the 2 ever co-exist? Will there ever be root and Android/Samsung Pay that work together?
Click to expand...
Click to collapse
I highly doubt it. I honestly wouldn't want it to work with root for security reasons. When you root your device it's open to all kinds of unsecured flaws. I don't know about you but I'm not putting my bank card information on a rooted device. ?
Sent from my SM-N930P using Tapatalk
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@LRiley thanks man. Got everything working! Thanks for the help with adb earlier ?
Sent from my SM-N930P using Tapatalk

[GUIDE] [NO ROOT REQUIRED] Hide The Status Bar Or Nav Bar With ADB

Hide The Status Bar Or Nav Bar With ADB​
To permanently hide Nav Bar for root users only see post 2
Note this only hides the Nav bar - swipe up gesture will show Nav bar and not all apps will honour the hidden status
Requirements
ADB setup on pc - see Here if you need to set it up
Moto USB phone driver installed
How To
Connect phone to laptop/pc via usb cable and make sure usb debugging is enabled
Open a command prompt or terminal window at your adb location (If you have adb in your environmental values then you can run this from anywhere)
The commands you’ll need are:
To only hide the status bar:
Code:
adb shell settings put global policy_control immersive.status=*
To only hide the navigation bar:
Code:
adb shell settings put global policy_control immersive.navigation=*
To hide both status and nav bar:
Code:
adb shell settings put global policy_control immersive.full=*
Return things to normal:
Code:
adb shell settings put global policy_control null*

Root Only - Permanently Disable Nav Bar​
Requirements
Root
Root browser
Note - not all roms will support this change
First check to see if the rom supports expanded desktop which will do the job for you either globally or on a per app basis
Instructions
Set up all your gestures before continuing
Copy build.prop from /system to sd card and rename build.prop-backup using a root browser
Copy build.prop to any folder on internal stoeage
Open build.prop file you have placed in internal storage
Add the following line at the end of build.prop
Code:
qemu.hw.mainkeys = 1
Copy modified build.prop back to /system using a root browser
Make sure permissions are still set to 644
Restart phone

I wanted to contribute with my findings... This command: "adb shell settings put global policy_control immersive.status=*" hides the status bar in all apps, but some of them get bugged, for example in Instagram you can't see the text field when replying on a story, or Twitter doesn't display the bottom part where you can insert pictures to your post while typing.
I discovered that if you type "adb shell settings put global policy_control immersive.status=apps," then Instagram works fine without the status bar, and of course you could add twitter after that to exclude twitter.
But this is a bit random, I don't know exactly why Instagram gets fixed by this and I wonder if there is a way to fix other apps...

once nav bar is removed can u turn on and off in settings

mikedolo said:
once nav bar is removed can u turn on and off in settings
Click to expand...
Click to collapse
No - not unless you create your own mod and add it to the settings apk
Use the adb command to return things to normal

I tried it hides but whenever you swipe up it displays and you have to swipe up a second time to complete an action ! How to disable the drag ?

mchtt said:
I tried it hides but whenever you swipe up it displays and you have to swipe up a second time to complete an action ! How to disable the drag ?
Click to expand...
Click to collapse
It displaying when you swipe up is normal - that's just how it works and subsequently will effect the swipe up gesture
If you want to completely remove it see if your rom supports expanded desktop - will be in your phones settings somewhere if it does. Revert the adb changes and use that instead

Yes it does but on certain apps a bottom bar remains

Lineage OS

I just tried XDA navigation gesture, it hides the bar properly for the moment ?

mchtt said:
Yes it does but on certain apps a bottom bar remains
Click to expand...
Click to collapse
Again nothing I can do about that - it's how android works and how the app was built
If you want to remove it properly use a rom that supports expanded desktop and enable it in your phones settings

Like I said I did and I said it to the ROM developer, thanks for your replies anyway ?