Related
Hey all, finally got my N1 today and I've been trying to unlock the bootloader for a bit following the instructions at redmondpie
You can follow the step by step guide posted below (on your own risk) to unlock the bootloader on the Google Nexus One phone. We are not to be held responsible if you ended up bricking your phone. The steps are as follows.
Step 1: Download and extract fastboot from here (Windows, Linux and Mac included).
Step 2: Run a command prompt / terminal at the directory you just extracted.
Step 3: Type ‘fastboot-windows oem unlock’ or ‘./fastboot-mac oem unlock’ or ‘./fastboot-linux oem unlock’ (as appropriate).
Step 4: Proceed on your merry bootloader unlocked way.
Our complete coverage on the Google Nexus One phone can be found here.
Click to expand...
Click to collapse
Problem is I get a "fastboot-windows is not recognized as an external or internal command.
I've tried the command while in fastboot mode and while in the bootloader.
Any help is appreciated.
Carlos
Fastboot devices does recognize my N1
you need to start your phone in fastboot mode. turn off your phone, hold trackball button down, power on your phone while still holding trackball down.
also when you open a command prompt type cd followed by the path to the folder where your fastboot file is at (example: cd C:/myfolder/) and press enter. then type the command
I don't have my N1 yet so I haven't tried.
You're sure you are in the proper directory in the command prompt?
also maybe run the command prompt as admin? (right click on the icon run as administrator)
I'm an idiot.
I was supposed to download the zip attached in that thread and run the command prompt from the extracted folder. FYI: you can hold ctl+shift and left click on the folder to open a command prompt.
Well, might as well sticky this so other people don't have the same problem.
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
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
scotty7910 said:
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
Click to expand...
Click to collapse
are you in the same folder that the FASTBOOT.EXE is in when you run the command???
Make sure your running CMD as administrator. You can tell by the path that shows when cmd is launched. If its a regular user account it will path to something like: c:\users\"your username"\
If your running as admin it will path to something like: c:\windows\system32
Sent from my MB860 using XDA Premium App
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
beatphreek said:
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
Click to expand...
Click to collapse
Another handy thing is to open the folder then hold the shift key and then right click. You'll have an "Open command window here" option.
Yep I use that all the time...
used both the suggestions in here and still having trouble,can do the root of c folder,use the dir command see it is all there but the cd C:\fastbootpackage brings the same response again.Can anyone see where I am going wrong?Once the command line changes to fastboot what do I need to command?Phone is still attached (as per the guide I am following?)showing 100% phone needs manually rebooted.
I have all latest drivers on win 7 64bit and I am definetely running cmd as an administrator
Also as the third suggestion suggests if I open the cmd box from the folder what is the exact command to use from there?Is there an alternative to doing this as I am beginning to struggle?
Unlock your Bootloader
1. You need to download and install RDS lite on your PC:http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
2. Download and extract IHOP_Bell.rarhttp://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1136261&v=1&libid=1311795928774&out=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997&title=%5BPUDDING%5D%20International%20House%20of%20Pudding!%20(Unlock%2Froot%20thread)%20Updated%20July%2023%202011%20-%20xda-developers&txt=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar
3. Download and extract Fastboot tools http://gititbit.ch/FAST
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM*card*for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone*reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a.On Windows, press Start and type “cmd” then press the enter button
17.Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example:* cd C:\Users\Kenneth\Desktop\fastboot-package)
a.cd*your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a.Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a.fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a.fastboot oem unlock ####
b.fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
This is the guide I have been using, thanks again
scotty7910 said:
"this is not an internal or external command"
Click to expand...
Click to collapse
This msg will only show if you are in different folder than your fastboot. You don't need to run cmd as administrator. The best thing to do is:
copy those 3 files (AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe) to your main c:\ (do not put to the folder)
Run cmd and type "cd \" this will move you to c:\
Now type fastboot and press enter - you should see various commands that can be used. (your mobile doesn't need to be connect to your pc to see this)
Now you can continue with unlocking. If you applied ihop.sbf already then startt from step 18.
I'm 99% sure that you were in the wrong folder.
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Don't use the Rom Manager app. It sucks and doesn't work properly. Do things properly.
With XDA forum members there's no reason to do things half assed. Use your hole ass, dammit.
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Well if you came that far then try to install tenfar's recovery, download this file :recovery-en-goapk-0630-1029.zip Unzip and move recovery-en-goapk-0630-1029.img to your c:\....Now reboot your phone and enter to fastboot mode. In cmd go to c:\ and type "fastboot flash recovery recovery-en-goapk-0630-1029.img" and then "fastboot reboot" DONE
If you have any problems try to download moto-fastboot (http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440). It's kind of the same thing as fastboot and to be honest I don't know what's the different between both (I think moto-fastboot is designed for 2.3.4 firmware). Extract zip and move moto-fastboot to c:\ and type the same command but instead of fastboot type moto-fastboot. I hope this make sense.
Also it's recommended to delete "install_recovery.sh" which apparently is in /system/etc/ BUT I never managed to find this file and I just ignored this step.
thanks foka, but I have already tried and tried again unsuccessfully to use tenfars cwm.I can install the recovery and delete the sh file all as normal using fastboot and astro.However for some reason there seems to be no way I can get into cwm having flashed it.when I attempt it I dont see the same menu I could scroll through as before.Then I tried a cwm of tenfars that was supposed to flash through rom manager.Again the flash went fine but could not seem to enter recovery mode.I see you installed aura 1.1 didi you flash a radio afterwards?My signal is comnstantly 1 bar.Could you reccomend a uk radio?
Well Ive flashed at&t radio N_01.77.30p which solved battery draining and 1 bar issue. I'm not sure why you can't use cwm recovery...
Sent from Motorola Atrix
What do you mean you don't see the same menu as before? When you hold volume down, power up phone, fastboot, scroll through the list and none of them say Android Recovery?
After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows *see end of post*). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers *see end of post*) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android platform tools from the SDK installed on your Mac:
http://developer.android.com/sdk/index.html
Note: the only platform tool you need to sideload is adb.
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and tap the volume up button (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. Open a terminal window on your Mac and type "adb devices". Terminal will identify your nexus 7.
b. Type "adb sideload ". Don't forget the space.
c. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
* Windows 8.1 x64 drivers, thanks to sahilcc7: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Command not found
xdhall said:
After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for ANY developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android SDK installed on your Mac:
Follow instructions here: http://developer.android.com/sdk/index.html
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/packages/data/ota/google_razor/3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and volume up button down (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. In the terminal window on your Mac, type "adb sideload "
b. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
Click to expand...
Click to collapse
I downloaded the SDK file for Mac and set up the Eclipse app. However I get a "Command Not Found" when I try to type into Terminal? I appreciate seeing instructions for a Mac; thank you.
Make sure you're connected with a microUSB. Type "adb devices" in terminal to verify that you're hooked up.
Sent from my Nexus 7 using Tapatalk 4
Also, be sure there's a space between the word sideload and the file name that shows up after you've dropped the zip onto the terminal window.
Sent from my Nexus 7 using Tapatalk 4
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
---------- Post added at 02:24 AM ---------- Previous post was at 02:21 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
You can use Mini ADB and Fastboot Installer from xda too, just 2mb. I used it.
Sent from my Nexus 7 (2013)
bobng said:
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
Click to expand...
Click to collapse
In theory the first time you execute an adb command during a session in terminal you'll get the following echo:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then it will execute your initial command.
I've added an adb devices command to the guide so if anyone reports a problem, they'll already know if they've been able to communicate across the microUSB cord.
Sent from my Nexus 7 using Tapatalk 4
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
bobng said:
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
Click to expand...
Click to collapse
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
xdhall said:
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks, I rarely use Terminal so will have to read up some more to get this working.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
I should be able to walk you through it tomorrow.
Sent from my Nexus 7 using Tapatalk 4
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
Basically you need to tell terminal where to find the bits of the various SDK programs by editing your bash profile. This is how terminal knows what you mean when you ask it to execute an adb or fastboot command. Let me simplify from the androidauthority guide. It takes three lines of code.
Open up a terminal window and execute the following:
Step 1: This step lets you edit the profile that tells terminal where to find executable binary files
Type and press enter:
Code:
vi ~/.bash_profile
Step 2: The step actually edits said profile
Type but don't press enter:
Code:
export PATH=$PATH:
Open a Finder window and find the folder "platform-tools" in the sdk folder (make sure you've put your sdk folder wherever you want it to live--if you move it later, terminal won't be able to find it). Drag and drop the folder on the terminal window. This time you DON'T want a space between the typed code and the file path.
Now press enter.
Step 3: This step saves your changes
Type and press enter:
Code:
source $HOME/.bash_profile
From now on, whenever you open a terminal window, you'll be able to use your sdk tools.
sahilcc7 said:
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
Click to expand...
Click to collapse
Updated OP with the recommended tweak to the language and the link to the drivers. Thanks!
Sent from my Nexus 7 using Tapatalk 4
This worked for me without issue. I only had to install the proper drivers and after that it went smooth.
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
usage: vim [arguments] [file ..] edit specified file(s)
or: vim [arguments] - read text from stdin
or: vim [arguments] -t tag edit file where tag is defined
or: vim [arguments] -q [errorfile] edit file with first error
Arguments:
-- Only file names after this
-v Vi mode (like "vi")
-e Ex mode (like "ex")
-s Silent (batch) mode (only for "ex")
-d Diff mode (like "vimdiff")
-y Easy mode (like "evim", modeless)
-R Readonly mode (like "view")
-Z Restricted mode (like "rvim")
-m Modifications (writing files) not allowed
-M Modifications in text not allowed
-b Binary mode
-l Lisp mode
-C Compatible with Vi: 'compatible'
-N Not fully Vi compatible: 'nocompatible'
-V[N][fname] Be verbose [level N] [log messages to fname]
-D Debugging mode
-n No swap file, use memory only
-r List swap files and exit
-r (with file name) Recover crashed session
-L Same as -r
-T <terminal> Set terminal type to <terminal>
-u <vimrc> Use <vimrc> instead of any .vimrc
--noplugin Don't load plugin scripts
-p[N] Open N tab pages (default: one for each file)
-o[N] Open N windows (default: one for each file)
-O[N] Like -o but split vertically
+ Start at end of file
+<lnum> Start at line <lnum>
--cmd <command> Execute <command> before loading any vimrc file
-c <command> Execute <command> after loading the first file
-S <session> Source file <session> after loading the first file
-s <scriptin> Read Normal mode commands from file <scriptin>
-w <scriptout> Append all typed commands to file <scriptout>
-W <scriptout> Write all typed commands to file <scriptout>
-x Edit encrypted files
--startuptime <file> Write startup timing messages to <file>
-i <viminfo> Use <viminfo> instead of .viminfo
-h or --help Print Help (this message) and exit
--version Print version information and exit
Bobs-Retina:~ bobng$ -v -/.bash_profile
-bash: -v: command not found
Bobs-Retina:~ bobng$ export PATH=$PATH:/Users/bobng/Downloads/adt-bundle-mac-x86_64-20131030/sdk/platform-tools
Bobs-Retina:~ bobng$ source $HOME/.bash_profile
-bash: /Users/bobng/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$
I just upgraded to Mavericks, not sure if that makes a difference?
bobng said:
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
I just upgraded to Mavericks, not sure if that makes a difference?
Click to expand...
Click to collapse
You're using a hyphen where you need a tilda.
You typed: vi -/.bash_profile
It should be: vi ~/.bash_profile
vi space tilda forward slash period bash underscore profile
It might help to copy and paste the code from my post directly into terminal.
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
bobng said:
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
Click to expand...
Click to collapse
Delete the swap file by executing the following:
Code:
rm -r ~/.bash_profile.swp
Don't forget the ".swp" at the end
Then start again
Here's what I did, I downloaded the the full image, some 400mb to
File i found in the forums here, I then rebooted into twrp, and installed from zip.
Boom.
All my apps were ok apart from the browser. I'm on 4.4, have new kit Kat features etc. Other than that, how do I know if I did it right?
Sent from my Nexus 7 using xda app-developers app
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.