Facebook account issue? Try this.

Facebook account issue? Try this. - Droid X General

If your don't want to do a factory reset like I didn't to fix the facebook account snyc/un-removable issue, try this:
Warning I take no responsibility in any damage you inflict if you input any commands incorrectly.
First you must be rooted, have Bootstrap installed and uninstalled the facebook app from the market.
1. Connect your Droid X to your pc
2. Open Command and navigate to your adb folder but do not run adb yet.
3. On your Droid X use Bootstrap and reboot into Clockwork recovery
4. Once you are in Clockwork recovery run "adb pull /data/system/accounts.db"
This will make a backup up of your accounts installed.
5. run "adb shell" via command
6. run "su" to make sure your in Superuser mode.
7. run "cd /data/system"
8. run 'rm accounts.db"
9. run "exit"
10. run adb reboot
When your Droid X reboots go to settings> accounts and if you have no accounts you have successfully removed all accounts including the facebook that was un-removable. You will have to reset your G-mail accounts and voicemail or any others you use.
If you have any issues I will try to help, or this wonderful community will assist.

Related

Stable ROM w/Backup Assistant?

Are there any stable ROMs that have Backup Assistant? My son just bought a Droid X and I rooted it for him. I have an Incredible and it seems like I have so many more choices as far as ROMs go. I put a couple ROMs on his X but they both had Backup Assistant removed and he really needs to have it.

I'm not sure of any of the ROM's currently that have Backup Assistant still in it. I think most of the ROM's have taken out all/most of the Moto Blur features and a lot of the "bloatware" that verizon throws on their phones. MY guess would be that most devs are pulling this out of the phone. If you really want to add it back in, I would try this...I have never had to do this for Backup Assistant, but I have manually added Facebook back in like this...
NOTE: If you have the phone rooted, I would make sure that you have koush's bootstrap installed and make a backup of the phone in its current state in case something goes wrong. Then you have a backup you can restore.
The usual...I take no responsibility if your phone gets messed up from following this...
Open a command prompt with the phone attached using Charge only USB mode.
Type the following commands:
1) type: adb shell (press enter)
2) tyep: su (press enter)
3) type: mount -o rw,remount /dev/block/mtdblock4 /system
You will need the android sdk installed, and open up ANOTHER command prompt to the sdk/tools/ folder. Paste the attached .apk and .odex files for backup assistant in the tools folder. You will need to rename the .odex.zip file to just .odex
make sure that ithe phone recognized by adb (at command prompt, type adb devices)
From command prompt at C:\<sdk location\tools\
1)type: adb push BackupAssistanceClient.apk /system/app
2)type: adb push BackupAssistanceClient.odex /system/app
switch back to the first command prompt where you typed adb shell (MAKE SURE NONE OF THIS IS MISPELLED! the slightest error can brick a phone!
1) type: cd /system/app
2) type: chmod 644 BackupAssistanceClient.apk
3) type: chmod 644 BackupAssitanceClient.odex
4) Type: exit
you may need to type exit one more time, but make sure it returns you to a normal command prompt. Then type adb remount
This will remount the /system portion of the phone back to the normal read-only state.
Then you will need to reboot the phone. When it loads up, this should have the app reloaded for you to use.

lennie paz said:
Are there any stable ROMs that have Backup Assistant? My son just bought a Droid X and I rooted it for him. I have an Incredible and it seems like I have so many more choices as far as ROMs go. I put a couple ROMs on his X but they both had Backup Assistant removed and he really needs to have it.
Click to expand...
Click to collapse
Why not pull his contacts off of Verizon's website and import them into Gmail?

milan616 said:
Why not pull his contacts off of Verizon's website and import them into Gmail?
Click to expand...
Click to collapse
Either they do not know how to do this, or they don't want their contacts with Google
I would suggest syncing with Google over using the Backup Assistant
Log into the Backup Assistant web site
Somewhere you will find export contacts
Export as a csv file
Log into GMail
Go to Contacts
Click import
Find your downloaded csv file
Import
Run the merge and clean option
And you are done

I BELIEVE Apex still has Backup Assistant, not 100% sure though as I've been running GummyJAR for a while now:
http://androidforums.com/droid-x-al...id-x-running-running-fast-can-12-16-10-a.html
Honestly if you just want to be able to keep track of your contacts, I would just back them up to the SD card, load up a different ROM (my personal favorite after having tried them all is GummyJAR at the moment), load the saved contact list then make sure your Google account is backing them up. It's what I do and I prefer it over relying on Verizon's software.

Yeah gmail.contact sync is super easy... but apex has backup assistant on it still, fyi
Sent from my DROIDX using XDA App

My favorite would be chevyno1's SSX 1.1 at the moment.
Sent from my DROIDX using Tapatalk

Yeah ApeX is definitely the way to go !! and it indeed does have Backup assist.

milan616 said:
Why not pull his contacts off of Verizon's website and import them into Gmail?
Click to expand...
Click to collapse
To the OP, this is what I would suggest. Gmail backup is much easier. Once you log in to the phone with your Gmail account, your contacts will automatically come up.

Yes I would suggest Gmail contacts as well. I ROM all the time and my contacts always get sync'd to my phone as soon as I add my Gmail. Once I add my FB it also syncs with their profiles and adds/updates pictures.

Droid starts in recovery mode all the time

When I turn it on in the morning it goes into recovery mode I then select the reboot and it boots up and I'm good. I turn it off at night and charge it then when I turn it on again its in recovery mode. I was rooted and had bootstrapper but I do not have bootstrapper any more but still rooted. I deleted every file and everything that was related with bootstrapper. Please help me and I'm a noob at some of this stuff.
Sent from my DROIDX using XDA App

Most will tell u this is a blessing z better to always boot into recovery than to ppotentially not boot at all one day. If you TRULY want to remove bootstrap completely, google "completely remove droid X bootstrap"
The process involves renaming a logwrapper file that bootstrap had renamed, and deleting the one created by bootstrap
Sent from my DROIDX using XDA App

I agree that its not a problem but still don't want it. Can you please tell me how to do what you said. I have no clue in how to do that. As simlp as possible please and thank you
Sent from my DROIDX using XDA App

Ok... Here goes:
1) connect your phone to ur pc in charge only mode. Makr sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no reaponsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following thesr directions, you do so at your own risk.
Sent from my DROIDX using XDA App

One question about adb you said it will recognize it. Is it on my phone or is it something that I need to installed. That's the only thing I'm a little confused on everything else I'm good on.
Sent from my DROIDX using XDA App

Adb is the driver interface between your computer and your phone. You will need the latest motorola drivers installed on ur computer. Adb is on your computer
Sent from my DROIDX using XDA App

Sorry for the stupid questions but is adb going to pop up on my computer when I plug my phone in or is it something im going to need to find. Again thank you.
Sent from my DROIDX using XDA App

spacecasespiff said:
Sorry for the stupid questions but is adb going to pop up on my computer when I plug my phone in or is it something im going to need to find. Again thank you.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Here is a way to tell if you have adb drivers installed.
1) plug in your phone via usb to your computer.
2) open a command prompt. Type "adb devices" and press enter. (you don't need the quotes)
If it returns text that looks like " device 05842688788" adb is working correctly. The random numbers will be unique to your phone.
Sent from my DROIDX using XDA App

actually if this continues and you have koush's droid x bootstrapper open it and click the first option and give it superuser permission and it should stop

ok i pluged in my phone and put it on charge mode now I clicked on the start botton on my computer brought up the search bar and typed in command prompt. Is that correct. I then entered adb devices and i said it was not reconized as and external device. now im not sure if that is what i was sopposed to do. I think i was expecting something to just pop up. This is the only thing that i dont know how to find. You say its on my computer but where do i find it.

some people who dont know what theyre doing in the first place shouldn't start....smh just saying

Funnyface19 said:
some people who dont know what theyre doing in the first place shouldn't start....smh just saying
Click to expand...
Click to collapse
Eh... Yes and no. he wants to learb, and we all had to start somewhere.
Spacecase:
You need to download and install the android sdk. Google this and post back when you have it installed =)
Sent from my DROIDX using XDA App

So how am I going to learn how to do something if I don't start some where I just don't wake up and go " I know how to do it" no one told me about the sdk and now I know thank you. It will be tomorrow before I do any more.
Sent from my DROIDX using XDA App

I downloaded the ask and have no clue inn how to use it. I click on the ask within the file it then brings up a black menu then wants me to download all sorts of stuff. The black box is where I type in the stuff but it wont let me type anything. Is this the only way to fix my problem
Sent from my DROIDX using XDA App

spacecasespiff said:
I downloaded the ask and have no clue inn how to use it. I click on the ask within the file it then brings up a black menu then wants me to download all sorts of stuff. The black box is where I type in the stuff but it wont let me type anything. Is this the only way to fix my problem
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Space,
I will need some time to try and put together some steps for you.
My suggestion would be to be careful with modding your phone. I feel like you may be in a little over your head. I do not say this to belittle you, but merely out of concern. I don't want to see ur phone break on you, and you not have the means to fix it yourself, that is all.
I am glad you have a desire to learn what you want to, but be careful, as these tools can also cause more harm than good. I will try and get you some info to set you straight!
Sent from my DROIDX using XDA App

Can't you just use root explorer to delete the hijack file and modified logwrapper, then rename logwrapper.bin to logwrapper? Instead of using all the sdk stuff?
Sent from my DROID2 using XDA App

spaceman4 said:
Can't you just use root explorer to delete the hijack file and modified logwrapper, then rename logwrapper.bin to logwrapper? Instead of using all the sdk stuff?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes! If you've purchased root explorer.... So kinda has a caveat there! But definitely a recommended program if you know what you are doing with root privileges...

Just posting a few files for a tutorial I am typing up to come later...

GUIDE PART I:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r08-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following:
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ; at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers <your operating system> you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Removing BOOTSTRAP COMPLETELY
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.
There will be more to come...but it's late, and I have already type 4 pages worth of text into Word already... Add 8 hours of server management to this... equals one fried brain...gonna get some sleep.

I know I was over my head a little and did my home work about how to fix any problems that I may encountered but didn't think that I would need to use adb. I know how far I can go and be ok now. I greatly appreciate what you are doing for me. I will get back on my computer when im done at work. I seem to have the right file downloaded so im good there. I will let you know how it goes. Again thank you. Im done messing with my phone and I find out that it runs great and is quick even with no roms or tweeks. Best phone I've owned.
Sent from my DROIDX using XDA App

DX noob here. Anybody wanna help me out?

I ordered my DX earlier today and should have it tomorrow afternoon. (yay!)
I'm coming from the LG Ally, which I played around with quite a bit as far as root/roms go. I ended up bricking it when the Froyo update came out trying to get from 2.1 to one of the new 2.2.1 roms.
I've seen a lot of stuff about the DX and it looks like a lot of progress has been made (yay, again!). I love the look of Gingerbread, so I'd probably look into flashing one of the roms that supports a GB theme (Liberty looks cool!), but I don't want to run into trouble when the official GB release comes out.
So, how hard is this on the DX? What are the general steps? What in the world is a SBF?
Any sort of basic noob-friendly introduction would be greatly appreciated!
Thanks!

Here is a bunch of stuff I have put together for various people that should get you started:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r08-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following:
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ( at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers <your operating system> you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Removing BOOTSTRAP COMPLETELY
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.

Thanks for the reply, but it's actually pretty confusing...
To install z4root, do I NEED to do any of those adb steps or can I just sideload it? I'm not sure if you're telling me to do both of those steps or just either/or. Sideloading is much easier, if it's an option.
And as far as the bootstrap goes - am I removing the original bootstrap and then installing the apk you attached to replace it with a custom bootstrap? Is this different than a custom recovery?
Also, what are SBFs and how do they fit into all of this?
Thanks!

lextex said:
Thanks for the reply, but it's actually pretty confusing...
To install z4root, do I NEED to do any of those adb steps or can I just sideload it? I'm not sure if you're telling me to do both of those steps or just either/or. Sideloading is much easier, if it's an option.
And as far as the bootstrap goes - am I removing the original bootstrap and then installing the apk you attached to replace it with a custom bootstrap? Is this different than a custom recovery?
Also, what are SBFs and how do they fit into all of this?
Thanks!
Click to expand...
Click to collapse
No, you do not have to do it this way. I just used this as an example for something I was doing for someone else, especially since they needed the sdk anyways... Just was practice.
(PS, not sure what you mean by sideloading... sorry just not familiar with the term...) Nonetheless...
You can just download the file, and then use file manager to install the file or any app installer you may normally use. Just make sure that under Settings-->Applications-->Unknown sources, that the check box is marked. Then you should be good to go.
As for bootstrap... You are basically replacing a logwrapper file that tells the phone to boot to Motorola's built in recovery. Koush's bootstrap hijacks this and writes its own logwrapper and allows for the recovery process to be interrupted so backing up/restorying, etc. You can load that apk the same way you do Z4root.
As for SBF files, I'm can't recall what it actually stands for, but it is basically a file from Motorola that allowed their employees to flash a phone back to "out of the box" state in the event that a customer ruined their phone or had issues with it... this goes way back to even the Motorola Razor days I believe... In any event, it is used alongside a program called RSDlite. This program allows you to connect your phone to your computer and flash the sbf files that have been released, and as a result allows you to restore your phone back to a "clean" state in the event that you mess up the /system partition and for other uses as well.
I will be adding more to a basic guide for all things Droid X later this weekend. If you have more questions, feel free to post back. And check out my other post here:
http://forum.xda-developers.com/showthread.php?t=940986
This includes the same info as I posted here already, but should have some more updates this weekend.
Good luck!

new here also.
i thought droid x could not be rooted.
i bought mine in october 2010; it's running 2.2.1
thanks in advance

The Complete Noob-iots Guide To Rooting, Recovery, and Troubleshooting

The purpose of this tutorial is not to teach you everything. It's just to give the less-than-average user (noob) an idea of why certain steps are taken and how to prevent and or troubleshoot problems that most people have when rooting or flashing ROMs on their device. I am also assuming that if you do decide to root your device you have at least a basic working knowledge of a computer. If you don't know what a desktop is or how to find the "any" key, you have no business being anywhere near a computer much less an android device…continue no further. Read my tutorial…If you like it, let me know. If I missed anything or got something wrong, let me know…I'll try to fix it. If you're impartial to it, I couldn't care less. If you hate it, PM me…I have some important information for you about anger management.
ROOTING
While there are different rooting "methods" they all rely on the same basic concept. Get temporary root access to your system in order to use the adb (Android Debug Bridge) to transfer necessary files and change permissions to permanently root (take ownership of) the device.
Before programs like KindleFireUtility and KindleWater, rooting the Kindle Fire was done manually through a command line interface (command prompt). Although those programs still use the same methods, you never see it. But why use command prompt? What do those commands mean anyway? Anyone can point and click but if you don't know what is going on behind the scenes then you are big trouble when things go wrong…and they inevitably will. So, let's get started.
From here on out we will consider this the beginning of the tutorial. Read everything first before doing anything. Pay close attention to what's being said and follow instructions carefully. Now...
Before anything your device needs to be fully charged and have the Android SDK and the Kindle adb drivers installed onto your computer. I'm not going to go into how to install SDK or Kindle adb drivers here because there are millions of pages on the internet that will teach you, and quite frankly that's not the purpose of this tutorial. That being said, lets get down to business and talk about the older (manual) methods of rooting the Kindle Fire.
First, lets start with the device turned on. Now go to your Kindle Fire settings and scroll down and select "Devices". Make sure "Allow Installation of Applications" is set to ON. This allows you to install apps not downloaded from the Amazon App Store. Next we open the App Store and search for and install a file management utility (ES File Explorer is a good one to start with). This will be necessary to temporarily root your device. Exit the App Store.
Now plug your device into the computer. For the purposes of this exercise there are two USB modes you will need to know, USB debugging and USB file transfer. On stock devices when you plug into your computer you will see a black screen that says "You can now transfer files from your computer to Kindle". This we will call USB file transfer mode. You will use this to transfer a program to your device that will give you temporary root permissions. The old program for this was ZergRush, nowadays its BurritoRoot and tomorrow it will probably be something else. Whatever it is, find whichever one works for your device's software version and transfer it to your device using Explorer (Windows) or Finder (Mac). Since you don't have root access yet, everything you put on your device for now will go directly to the SDcard partition, far away from system folders (for all intents and purposes).
Press "disconnect" on your Kindle Fire. Now, and by default, your Kindle is in USB debugging mode. What that means is that when you are not in USB file transfer mode your device is constantly listening for debugging commands coming from the USB port. We will be using this to send adb commands to the device which are necessary for rooting and setting up recovery. Now open the file management app you installed from the App Store, navigate to the temporary root program you transferred from your computer and open it. Install and follow the instructions, if any. Next go to your computer and navigate to your Android SDK folder and look for a folder called "platform-tools" if you don't see it, open the tools folder and double-click the file named "Android". Select "platform-tools" and install.
To make things simple, lets to take the platform-tools folder and place it on your desktop (just be sure to put it back when this is all over).
At this point we need to get Superuser. This is what we will use to give your apps root access. Go to http://www.androidsu.com/superuser and download the one for Gingerbread. Extract the superuser.zip file, open the folder and navigate to the system folder inside. There, inside the "app" and "bin" folders you will see two files called "superuser.apk" and "SU". Place them in the platform-tools folder that is now on your desktop. And now the fun part, it's time to start rooting.
Open your command prompt (or terminal for mac users) and type and enter:
cd Desktop/platform-tools
Here, you are telling the computer to cd (change directory) to the platform-tools folder located inside the Desktop folder. This is going to be your workspace. Everything you do from here on will be done from this folder. If you don't get any errors then you are in good shape. Otherwise you messed up somewhere and probably skipped a step...go back and read from the beginning. Make sure your Kindle Fire is turned on and NOT in USB file transfer mode. If you are not sure what mode you're in, go back to the beginning. If this is your second time around, stop. You need to learn more about how to change directories using command line interface.
When you are in the platform-tools folder, type and enter this command:
adb devices
Mac and Linux users will put ./ before all adb and fastboot commands from here on out. It will look like: ./adb devices
Here you are using the adb program to print a list of connected devices. You should see a bunch of numbers that mean nothing to you at this skill level. Move on. If you don't see any numbers then you either don't have your drivers installed properly or you skipped a step; go back to the beginning.
If you do get a bunch of numbers your device is connected. Now type and enter:
adb root
...gives root permissions to the adb
adb remount
...mounts the system partition to a "read/write" state allowing you to make changes to system files and folders. Consequentially, if you enter adb remount a second time, you will change it back to "read only". Don't do that.
adb push su /system/xbin/su
...will push (transfer) the file named "SU" that is in your workspace (platform-tools folder) to the su folder inside the xbin folder of your device's system folder. The SU binary file is what other apps call to when they need superuser rights.
adb shell chown 0.0 /system/xbin/su
...this is where it gets a little funky. It opens a shell interface within the adb in order to chown (give ownership permissions) to user 0.0 for the su folder. A shell is a piece of software with a particular set of commands built in to act as sort of a go-between between the user, operating system and hardware kernel services. But who is user 0.0? [Edit:] User 0.0 is the root user. Thanks to b63 for that piece of knowledge
adb shell chmod 06755 /system/xbin/su
...opens a shell within the adb to chmod (change mode) of the su folder to 06755. What that basically means is you are changing the folder permissions to rwxr-xr-x or read/write/execute for the owner, and read/execute for the group and others.
adb install superuser.apk
...installs the program superuser.apk located in the platform-tools folder. Superuser.apk maintains a database of what apps you allow to access SU binary file.
That's how the rooting process works. Again if you get any errors, you did something wrong. Go back to the beginning and read it all over again. Attention is key.
Also, I suggest you skip the one-click methods for rooting and get used to using the command line interface so you understand how the process works in order to quickly troubleshoot problems should they arise. Oh and congratulations, you are rooted.
RECOVERY
Now lets install a custom recovery utility and a new boot-loader. For this you will be using the fastboot command. Before we go on, one thing you absolutely must get your head around is the difference between how fastboot interacts with your device versus how adb interacts with your device. fastboot deals with the boot portion of the device whereas adb only deals with the system portion. What that means is adb will only work when the device is completely booted. If for some reason your device doesn't boot properly then you should not be issuing adb commands. It's like trying to light a match in a vacuum. Fastboot works in the same way in that you must be in the fastboot bootmode in order to issue fastboot commands. Unless you have custom recovery installed or a factory programming cable there is only one way to get into fastboot mode. We'll talk about that later.
Installing recovery is a simple process but it is where people tend to have the most problems. Part of the reason is the misunderstanding of the different bootmodes. For now, you only need to be concerned with two of them; normal bootmode (4000) and fastboot bootmode (4002). The main reason people run into trouble is that once you are in a particular bootmode, it doesn't change until you tell it to (with the exception of temporary fastboot which we will get into later).
In normal bootmode your device will boot...normally (imagine that). With the fastboot bootmode the boot-loader will hang at the Kindle Fire splash screen (or yellow triangle if you have recovery installed) to wait for further commands. If this happens to you, chances are your only problem is you are in the wrong bootmode, which is easy to fix. Knowing that, installing a custom recovery should be a breeze.
First find whatever recovery you want to use (unzip it if you have to) and place the .img file into your platform-tools folder that you were using earlier. We're going to use adb to change the bootmode to fastboot in order to install custom recovery. Remember, anything that pertains to the boot-loader, (Kindle Fire logo/yellow triangle) will be done in the fastboot bootmode; that includes custom recovery installation. For more information on Kindle Fire bootmodes, boot-loaders, fastboot and just about everything else, see this post:
http://forum.xda-developers.com/showthread.php?t=1552547
From your command prompt type and enter:
adb shell su
idme bootmode 4002
reboot
What that does is tells adb to open a shell and su (substitute user) for the root user, change the bootmode from normal (4000) to fastboot (4002) and reboot. The root user has the necessary permissions to change the bootmode from the adb. Your device will reboot then hang at the splash screen because it is in the fastboot bootmode.
Now install your custom recovery (we'll call it customrecovery.img for now)
fastboot -i 0x1949 boot customrecovery.img
again, for Mac and Linux you would type: ./fastboot -i 0x1949 boot customrecovery.img
That tells your computer to, using the fastboot program that is in your platform-tools folder, boot the device with the ID of 0x1949 (your Kindle) with the file named "customrecovery.img"
After installation, reboot, but you will still be in the fastboot bootmode. So type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
…tells the device to reset the partition where the recovery(?) is located, change the bootmode to normal (4000) and reboot.
TROUBLESHOOTING
Flashing custom ROMS are another source of frustrations as they add too many variables to the equation. Some ROMS can be very unstable and cause weird things to happen to your device. But just knowing how this stuff works will help you fix 90% of the problems that may come up. If you are having trouble with your device, troubleshoot the problem:
Does the device turn on?
No
Is it fully charged?
No--> Charge it
Is it fully charged? Yes--> Hold the power button for 30 seconds and restart
Does the device turn on?
No--> Hold the power button for 3 minutes and restart
Does the device turn on?
No--> Google search "Motorola USB factory programming cable"
Does it boot normally? No
Do you have custom recovery installed No--> You need to get into fastboot mode to issue fastboot commands. Google search "Motorola USB factory programming cable"
Do you have custom recovery installed? Yes--> During the first 5 seconds of seeing the boot splash screen (this is temporary fastboot mode that comes with custom recovery) issue fastboot command to change bootmode to 4000. Reboot
Does it boot normally?
No
Can you get into recovery? No--> During the first 5 seconds of seeing the boot splash screen (temporary fastboot mode) issue fastboot command to install a new customrecovery.img. Reboot.
Can you get into recovery?
Yes--> Re-flash your ROM. Reboot.
Does it boot normally?
No--> Enter recovery, factory reset, wipe cache, wipe dalvik cache, re-flash your ROM. Reboot
Does it boot normally? No--> Enter recovery, factory reset, wipe cache, wipe dalvik cache, flash a different ROM. Reboot
Does it boot normally? No--> Post your problem on the XDA forum. Include all pertinent information such as what rom you are using, what the exact problem is, what you were doing before the problem occurred and all the steps you have taken to try and fix the problem.
Does it boot normally?
Yes--> Give yourself a pat on the back, because you rock!
Do you Rock?
No--> Start over from the beginning

nice
--sent from my glacier.

[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1)

Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/

It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk

Thank you for posting this so clearly! Would Samsung "smart switch" be a viable tool to use for backing up all my apps/app data, home screen setup, etc. before rooting, and still work to import the data after rooting?

EdrickMG said:
It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse
That kernel flash is optional from what I've seen. That's just what people have been wanting on their phones
Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Torrent File
Torrent Magnet Link
Torrent is hosted on 10gbit/s seedbox.
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
Click to expand...
Click to collapse
Sent from my SM-N910V using XDA-Developers mobile app

KingVekxin said:
That kernel flash is optional from what I've seen. That's just what people have been wanting on their phones
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's optional but have to make like 3 more steps with kernel you just flash it and that's it... 3 less steps

EdrickMG said:
It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse
It's included in Step 10. I think you may have missed it. It's the very last step. It's also included in the Google Drive folder and torrent.

You shouldn't need to do SuperSuMe. You can use Kingroot for the whole shebang. Also, you will need a kernel for 5.1.x roms otherwise it will bootloop at the Verizon logo.

Robots_Never_Die said:
It's included in Step 10. I think you may have missed it. It's the very last step. It's also included in the Google Drive folder and torrent.
Click to expand...
Click to collapse
Yes you are right I thought u missed it and it's very important... Disregard my previous comment
Enviado desde mi SM-N910V mediante Tapatalk

EdrickMG said:
It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse
Hyperdimensionalist said:
Thank you for posting this so clearly! Would Samsung "smart switch" be a viable tool to use for backing up all my apps/app data, home screen setup, etc. before rooting, and still work to import the data after rooting?
Click to expand...
Click to collapse
I have not used it. What I did was find every export settings/backup option in apps like nova launcher. I wrote down one time passwords for eligible accounts or disabled 2 factor Auth temporarily. I copied my SD card to my computer, along with all the files in the folders Downloads, Media, DCIM, etc. I exported my contacts and copied the file to my pc. I didn't care about any saved games so I can't help you there. Some people have success with Helium for back ups. Using the pc backup option.

Sizzlechest said:
You shouldn't need to do SuperSuMe. You can use Kingroot for the whole shebang. Also, you will need a kernel for 5.1.x roms otherwise it will bootloop at the Verizon logo.
Click to expand...
Click to collapse
The kernel is included. See comment below from the guy who said I didn't include it.
I heard kingroot sends data to China. So I don't want it on my phone longer than needed.
EdrickMG said:
Yes you are right I thought u missed it and it's very important... Disregard my previous comment
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse

isnt kingroot deleted once you do a full wipe before installing a custom rom via twrp?

mta1981 said:
isnt kingroot deleted once you do a full wipe before installing a custom rom via twrp?
Click to expand...
Click to collapse
Correct. Though this is a guide for staying on stock rom with root and the option to change roms at a later point easily.

Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Torrent File
Torrent Magnet Link
Torrent is hosted on 10gbit/s seedbox.
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
Click to expand...
Click to collapse
Just wanted to say thank you for compiling everything you rock

Thanks to the OP for the effort!
This should be stickied!
Sent from my SM-N910V using Tapatalk

Hey thanks to all devs for all that is being done to make our n4 more lovable. I have everything set up per op. ADB sees my phone and I am able to get root. I enter all the lines of the code and get positive response on all till I get to chmod 777 samsung_unlock_n4-fix. It is in my minimal adb and fastboot folder. It is also unzipped. It all works up to there. Also have drivers installed. Thanks
Sent from my SM-N910V using Tapatalk

having an issue after the command lines, saying this is for some samsung devices only?.....anyone know the fix for this ?

MrMeek said:
having an issue after the command lines, saying this is for some samsung devices only?.....anyone know the fix for this ?
Click to expand...
Click to collapse
What android version are you on? If you are on 4.4.4, update to lollipop and try! Also verify that your emmc starts with 15!

Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Torrent File
Torrent Magnet Link
Torrent is hosted on 10gbit/s seedbox.
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
Click to expand...
Click to collapse
Good one mate...
You can also flash MultiSystem-Kernel_LP-5.1.1 by @hsbadr instead of emotion kernel!
Its SE Permissive and wont show, "Seandroid is not selinux enforcing" error during boot and very snappy!
https://www.androidfilehost.com/?fid=24415232478676428

Yes this is a very good write-up of instructions. But I too, think the flashing the kernel is worth mentioning, considering I went through all this and ended up boot looping because I did not have the kernel, ended up doing it all over again, but a lot smarter the second time around.
?If someone helps you, plz thank them?
Sent from my Tab S SM-T700

Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Click to expand...
Click to collapse
My Super-Sume Pro is stuck on the beginning of Step 2. Is this necessary to run or can I skip out on it.

Database Users

welcome