5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]
I have seen a few people having issues with the DOK2 update and were looking for a step by step process of how to upgrade to the new firmware and optimize it to get goo performance. this thread will guide you through that process as well as link to the appropriate threads to download and get the needed files/add ons.
*****This process will wipe your phones internal storage and give you a clean install of the new firmware.
Step 1: Download the DOK2 firmware to your PC
There are a few places you can get this from:
Sammobile: N910T Firmware
Or XDA thread: Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2 UNMODIFIED Mirror
(You will need the entire firmware not just the modem and baseband)
Step 2: Download ODIN to you computer
From ODIN DOWNLOAD: ODIN 3.10.7
Step 3: Odin Flash new firmware.
The download from Sammobile or Mega should be a .zip file. you will need to unzip that file to find the .tar file which is what you will use for ODIN flashing the firmware.
If you need help using Odin to flash the firmware check out this post on Android Central: Help Thread
After you have completed the Odin Flash the phone should reboot and come to the setup screen with your new firmware.
Step 4: Odin Flash TWRP
Download TWRP to your computer: TWRP Downloads
Specifically you want this file: twrp-2.8.7.0-trltetmo.img.tar
Use Odin to flash TWRP recovery onto your device.
If you get lost you can check this tutorial: ODIN Help
Step 5: Reboot your device and setup
Once you have rebooted go ahead and set up your device. we will worry abou debloating and getting root after your device is setup.
Step 6: make a backup in TWRP
Once your device is setup make a TWRP backup of your setting
Step 7: Getting Root
*****Update: New SuperSu 2.64 beta. Works even better with Samsung phones. *******
You will need the latest SuperSU beta from the below thread.
SuperSU Beta Systemless Root
Newest version is 2.64
You will then boot into TWRP and flash that zip in recovery. This will give you "Systemless Root"
Systemless root allows you to use the stock kernel with SE LINUX enforcing, but still be able to use root apps. However this is not complete root. Some root apps that need to modify the system will not work. this is just a BETA root and is not final yet. check back to that thread for updates as they come out.
Once you have flashed the SuperSU zip reboot your device and verify your root apps are working.
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater V3.90 DeBloater
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps
http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
This Option removes 222 applications. It is a simple download and flash in recovery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Step 9 Viper4Android on Systemless root.
Download the Viper4 Andriod/Beat installer
Viper4Android w/ Beat Audio
Flash the installer zip in TWRP and reboot your device
Download BusyBox Installer
BusyBox by Stephen (Stericson)
Install BusyBox
Reboot
install Viper$Android Drivers
Reboot
Download both the Viper4Android SU policy fixes
1.) ViPER4Android-supolicy.zip
2.) XM_V4A_Fix_by_androidexpert35.zip
Reboot into TWRP and flahs both of these. you can flash them at the same time just to them in the order above. [1 then 2]
Reboot the device and enjoy V4a.
******Also the Beat portion of the zip is a bit wonky sometimes. I have not yet been able to get it to opperate effectively, so you may want to disable it or freeze it with Titanium backup.
Disclaimer: NONE of these zips are mine. I am posting download links from my mega, because I pulled these files from 3 different threads and only one was from an OP. the main Viper4Android /beats install zip comes from here : [SUPER MOD][4.3+/6.0][ v6.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD!
*************************************************************************************************************************************************************************
With this setup I have easily gotten more than a days worth of usage. I average about 5.5 hours of SOT and 24 hrs between charges. Normally I plug in around 20 hours with about 40% battery left.
*****These are all items developed by other XDA USERS. Please provide the thanks on their respective threads as well.
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is any way of getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
James62370 said:
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is anyway off getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
Click to expand...
Click to collapse
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
The two main reasons to use this method are:
1.) It keeps the system intact, which allows you to use apps that check for root. (eg. Android Pay, Some Bank Apps etc)
2.) It allows you to use the stock kernel from 5.1.1. Currently the only way to get root on 5.1.1 and up is to install a custom kernel. Which is fine, and there are two really great option available with Emotion and Beast Mode, but I find the stock kernel gets me the best battery life and is the most stable.
ALSO this will be the way root is done going forward. 6.0.1 has a bunch of system file locks that prevent much of the system tinkering from happening. Chainfire (dev who built SuperSU) has a nice right up about the system partition on XDA right now explaining why some of the system tweaks we were used to will not be possible in the future. so at the very least this is good practice for getting ready for the Marshmallow update.
ShrekOpher said:
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater [http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294]
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps [http://forum.xda-developers.com/not...t-touchwiz-bloating-script-222-apps-t3258537]
This Option removes 222 applications. It is a simple download and flash in recoevery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Click to expand...
Click to collapse
Witch option is the easier? :silly:
Avide said:
Witch option is the easier? :silly:
Click to expand...
Click to collapse
Option #2 is WAY easier as long as you don't want to modify the script. You just download it to you phone boot into recovery and flash it. Then reboot. Takes 5 min.
ShrekOpher said:
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
Click to expand...
Click to collapse
Appreciate your reply. I was under the impression that the boatloader is already unlocked which is why we can flash a recovery without jumping through too many hoops. I know that a custom recovery trips Knox, but if there's a way to install the latest supersu through a utility such as flashfire or mobile odin, Knox won't be tripped.
I'm not really worried about warranty, just curious to see if it's possible to retain the integrity. Unfortunately both those options I mention requires the device to already be rooted which defeats what I'm trying to accomplish.
Hopefully someone will be able to figure something out in the near future.
Is it possible to use xposed with this?
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
chodaboy19 said:
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
Click to expand...
Click to collapse
Well i'm on 5.0.1 right now pop rocks, so yeah i probably will wait since there isn't a particular feature... i'm using the DOK2 modem on COD6 rom right now.
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
There is no dark theme option as of right now, really it's the only thing i miss.
Will Rickards said:
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
Click to expand...
Click to collapse
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
chodaboy19 said:
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
Click to expand...
Click to collapse
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
ShrekOpher said:
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
Click to expand...
Click to collapse
I think I found the culprit after 2 days of googling and countless wasted hours. My specific problem was that Media process was running all the time which in turn was causing Google Play Services to run at all times.
The Media process includes 2 packages: Media Storage and Download Manager. Together they perform scanning and indexing of media files on the internal SD and external SD.
I came across this page:
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
I did step #3 which states that having more than 1,000 files in a folder makes this process crap out. I reformatted my microSD card, then I copied back all the files to the microSD. Then finally I deleted most of the pictures so that no one folder had more than 400 images.
I rebooted my phone and it started to behave normally. The Media Process only ran for 5minutes and stopped. Google Play Services ran for 2min and stopped. I have been through 1 charge already and got 5hrs or so of screen time with heavy use, I was installing apps, configuring accounts, freezing apps with Titanium backup, etc.
Overall, it seems like I have a happy ending to my story, BUT I will post a followup if the phone craps out again.
EDIT:
How do you get it to show the time on battery?
Mine doesn't have that information:
Does anyone have any interest in me adding how to set up Viper4Android on Systemless root to this thread? Just curious if I should go through the trouble.
There is a new version of SuperSU 2.64:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog:
20.12.2015 - v2.64 - BETA
- (systemless) Detect more boot image partition names
- (systemless) Blank partitions before writing to them
- (systemless) Ask to restore boot and recovery images on full unroot
- (systemless) Implement "uninstall competing superuser apps"
- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning
- (systemless) Cleanup system install properly if present, fixes a number of possible bootloops
- ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")
- supolicy: Additional SELinux patches for M (reduced logging only)
- Update translations
ShrekOpher said:
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
Click to expand...
Click to collapse
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
AlexanderBlaQ said:
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Should be working now. Thanks for the heads up.
Related
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Stock Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
Stock ODIN for the P900 can be found here: http://forum.xda-developers.com/showthread.php?t=2724895
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Thank you for your help. Now I will be able to use my tablet more frequently
dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
Click to expand...
Click to collapse
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Click to expand...
Click to collapse
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
acaldrn2 said:
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2724895
I will add it to the main post also.
Hello everyone,
I've noticed that there hasn't been any threads about rooting the Xperia Z2 Tablet on lollipop. Most threads have discussed how to root the device on 4.4.4 and to create an update image to maintain your root whilst updating to 5.0+.
I've scoured the interwebs and found nothing so I'll make it easy for those whom don't know how to achieve root or don't want to do much work without creating images and such.
First off I'm not responsible for any inconvenience that may come with rooting your device and losing your warranty. I can and will be willing to help out in restoring or answering questions that you may have.
This method uses Kingroot... For those who have a problem with kingroot, it is only used to achieve root and this guide will also be showing you how to remove kingroot and install Supersu with ease. Using the link below download the necessary files: Kingroot V4, Supersume, XZDualRecovery 2.8.26. Place all these files on the root of your devices internal storage/SD card excluding Xdualrecovery as that needs a PC. (If you want to Xposed working I will also supply the files needed for that as well). https://www.mediafire.com/download/wrsajbgw2jr6czt
*Make sure you have unknown sources enabled under Settings>Security>Device administrators as well as Developer Options available and USB debugging enabled. (To enable Developer Options go to Settings>About Tablet>Build Number and click it 10 times).
1. Install NewKingroot.apk and run the application. It will notify you that a root method was found and to try it. It may take up to 2 minutes to achieve root. (If all you wanted was root and are content with kinguser then you're done! :good: if you want Supersu and/or a custom recovery then continue on to step 2!
2. Connect your Tablet to your PC via microUSB. On your PC open and extract the contents of TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip to your desktop. Now double click install.bat a screen will pop up providing you with options to install xdualrecovery. Choose option 2. Installation on ROM rooted with SuperUser by pressing 2 and enter. The script will run its course and tell you to grant permission on your tablet. Open up your tablet and a kinguser prompt will show asking you to grant or deny permission to ADB (Grant it!!!) afterwards your tablet will reboot on it's own to TWRP. (I advise you to either make a backup of the tablet now or after you install Supersu as insurance in case of any mishaps). Click reboot System.
3.Install Supersume, open the application and run it. It will of course ask to grant it permission (Grant it!!!) it will check the environment (making sure that there isn't any Pokemon nearby that you don't need... Sorry Pokemon Go reference) and it will begin removing kingroot and install Supersu. If you didn't have Supersu installed already great! It'll open up Supersu automatically. Supersu may ask you to update binaries (DO NOT click TWRP as it will reboot and you have to start the process over from step one!!! :crying: Just click Normal and once it says successful you're done! :victory: The next step is optional if you Want Xposed.
*Optional 4. Install XposedInstaller_3.0_alpha4.apk. Open your app drawer and open NDR Utils. It will ask for permission (Grant it!!!) now here you may choose your preferred recovery... Philz Touch Recovery,TWRP or Clockwork Mod Recovery. Click Reboot to Primary Recovery (fourth option) once it's rebooted you want to click install>SD>xposed-v85.1-sdk22-arm-by-romracer-20160620.zip and swipe to install. You should get a success when it's finished. Now simply reboot and your apps will be upgrading. Congratulations you now have root with SuperSU and xposed! :victory:
**if you wish to uninstall Xposed simply reboot to recovery and click install>SD>xposed-uninstaller-20151218-arm.zip uninstall the application once it's rebooted and you're good to go!
***if you have a problem with Supersume not working, reinstall Newkingroot.apk and run it again to get root. Then run supersume again (Grant permission!!!) and let it run its magic.
If anyone has issues, has questions or needs help PM and I will do my best to help and answer all your questions. Please don't be discouraged because I'm new here! I will be soon adding a link to a video tutorial on how all these steps can be done!
I have the Verizon 561, will this allow rom upgrade to marshmallow?
chin_bone said:
I have the Verizon 561, will this allow rom upgrade to marshmallow?
Click to expand...
Click to collapse
Hi there, I also have SGP561 as well for Verizon. Verizon didn't release Marshmallowfor the device yet unfortunately. ???? still waiting and more then willing to confirm when it does
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
creepingcreep said:
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
Click to expand...
Click to collapse
Glad it worked for you. Just wanted to help people out as I had invested time trying to figure out my own. I didn't like flashing files constantly so tried making easy.
Never had luck with kingoapp and today isnt any different
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Sent from my SM-G930V using XDA-Developers mobile app
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Sent from my SGP561 using XDA-Developers mobile app
ToneLa said:
Never had luck with kingoapp and today isnt any different
Click to expand...
Click to collapse
Sorry to hear what version are you using? Use the provided KingRoot in the download link provided
Daimonion1980 said:
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
Click to expand...
Click to collapse
No, in the link provided all necessary apps and folders/zips are included. Including KingRoot apk
Cammy253 said:
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Click to expand...
Click to collapse
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
JediDru said:
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Click to expand...
Click to collapse
That's great news to hear! I picked one up and wanted to root and I did on KitKat but when I upgraded to lollipop I lost root and rooted it the long way... Needed something simpler and couldn't find anything on here. So I wanted to make sure a guide was available to all. Enjoy and let me know how it went
reymund602 said:
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
Click to expand...
Click to collapse
Thank you working great
Sent from my SGP561 using XDA-Developers mobile app
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
ToneLa said:
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
Click to expand...
Click to collapse
Let me double check and if anything I'll post a link to the apk
Sorry that you're having issues though
bilestoad said:
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
Click to expand...
Click to collapse
Thanks for confirming! If you didn't see the KingRoot apk in drive I'll upload the current version!
ToneLa said:
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
Click to expand...
Click to collapse
What is the software version you are having problems with?
Hi,
i need to get this phone rooted please, no root apps works, @Chainfire maybe can help?
Any one be able to help if this can be rooted?
xxmcvapourxx said:
Any one be able to help if this can be rooted?
Click to expand...
Click to collapse
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
KNOX should remain 0x0
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
ashyx said:
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
Click to expand...
Click to collapse
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
xxmcvapourxx said:
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
Click to expand...
Click to collapse
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
when trying to root
By Kin9Root Won Chu chu in a few ROot failure 'not yet suitable ˉ a - condolence ˉ ˉ a ˉ a "` ` One by one - one 'one one '- one - the
i get i've tried the pc version and the apk a few tries i keep getting notifications in the settings it is set to permissive
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
figured it out -- it was the pin we just trying super me
xxmcvapourxx said:
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
ok I tried 3 different cords, various lengths, and now no matter what I get this screen only
Click to expand...
Click to collapse
You're using the desktop version, please download and use the android English apk:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
.
Is there an update on this, did anyone achieve root?
.
ashyx said:
Is there an update on this, did anyone achieve root?
.
Click to expand...
Click to collapse
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
xxmcvapourxx said:
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
Click to expand...
Click to collapse
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
Yes as soon as super su me installs ask to install binaries ans ask to reboot it will lose root.
I will try the script without flashing firmware
Thank you ill let you know how i get on
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
xxmcvapourxx said:
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
Click to expand...
Click to collapse
It's not related to the bootloader, the bootloader is still locked, it's simply an incomplete installation of SuperSU. Probably due to permissions.
Follow the guide posted above and you should be good. I'd also suggest using root package disabler to disable knox.
Hit search in the app and type knox. Disable all knox related files.
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootpackagedisablerfree
.
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
ashyx said:
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
Click to expand...
Click to collapse
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
xxmcvapourxx said:
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
Click to expand...
Click to collapse
So even when flashing root with Flashfire still losing root? Did you try using the script posted above?
Also could you post a screenshot of Root validator after losing root?
I would also suggest flashing the stock firmware with FLASHFIRE.
Ensure to Uncheck the boot partition and disable EverRoot.
Add the system supersu zip to the install.
It may be remnants of Kingroot causing the issue. Flashing this way will ensure a clean system with just supersu.
Having the same problem
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
stanfox said:
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
Click to expand...
Click to collapse
Why can't you enable OEM unlock? Remove any pin/password from the device first.
ashyx said:
Why can't you enable OEM unlock? Remove any pin/password from the device first.
Click to expand...
Click to collapse
I was surprised at first when you directed me to this thread ashyx, the first word I saw was Kingroot and I was sure a dev such as yourself wouldn't use that.
I write against Kingroot all the time. It is information stealing malware that doesn't even give true root, packs PUPs, and sends IMEI and other info to China upon install (check the logcat).
And it's nortoriously hard to get rid of and replace with a different SU. From what I read above, true root hasnt' been achieved yet. Ive used KR a few times in the past, but never again. It used to be easier to replace KingUser w SuperSU. Not so much anymore.
Please folks, Kingroot IS NOT actual root ; please quit posting about it in a true professional developer site.
Ahyx, PM me if you wish. I'd like to work on any methods other than this. I can get the bootloader unlocked from Net 10. But not until having it hooked up w/ lthem for a year. I've already chosen to disconnect this device anyhow because I can't stand using a non-rooted phone. Too bad, it's a good machine. I got a great buy on it. $50US brand new. Same store today $99. WalMart = $120
I just bought an LG G3 for $45. Verizon model, interesting root. I had to downgrade firmware to achieve root. It's TWRPd, and running Dirty Unicorns 10.6, a nice rom, better once I mod it.
Tried the latest RR rom for it. Nougat was cool, but too early, too many bugs.
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Great job keep us posted
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
I think you would need a boot.img that disables it. Or you can disable encryption manually and erase all data to keep it disabled.
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
@jcadduono can help you to have a perfect job about TWRP ...
Ask him on irc ...
Backup failed because /data cannot be mounted, which suggests a mismatch twixt TWRP and device. Decided to push on and try to root. This failed, so that stock firmware had to be installed. I've hacked a number of phones and tabs here, so I was itching to see what could be done with existing N7 mods. Now I know.
It looks as though we need recovery etc specific to FE. Not sure we will have the numbers for it, though. If anyone has any ideas...
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Well I'm traveling now and will give this a go when I return home. Question: does DM Verity and Magic's or SU root require a a Note FR boot image to work or can they simply patch the boot image?
force70 said:
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
Ah, I followed directions I found on the N7 forum, from which I assumed that SU would do the encryption. This is the first time I have come up against this barrier. I was resigned to possibly not having root, but from what you say I now think we might well manage it.
I've had a number of narrow shaves with various devices, so I felt that I could find my way out of any difficulty I encountered hacking the FE (maybe just fool's luck) . While cortez.i will try it at some stage, I am tempted to dive back in and see what happens.
Incidentally, sammobile didn't have the K variant firmware (may have now). I found it through google on a vietnamese site.
Just found this comprehensive guide to removing dm-verity:
http://www.theandroidsoul.com/disable-dm-verity-forced-encryption-galaxy-note-7/
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
You are THE MAN !!!!
WOOOOOOOOOO
wolfgart said:
You are THE MAN !!!!
WOOOOOOOOOO
Click to expand...
Click to collapse
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
force70 said:
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
Click to expand...
Click to collapse
I uninstalled the log agent with Titanium, ripped out all the Knox, still getting that message. I think I'll backup progress so far and restart FE from within the warning message and see what happens...**
Thank you both for the kudos. But some work still to be done. I'm finding some apps won't start - unfortunately some of them important. It's OK for now - I'm not using the FE yet - but need to get some real benefits from root, otherwise it's back to stock with Adhell (tho' I'd say sammy will spike that soon). Maybe folk with more tech xp than I have can work out what's wrong here.
**Restart from within Security boots into Recovery - in this case TWRP. Looks like a response to the decrypted state, and is set off by any root level action. Can we get rid of this?
zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
cortez.i said:
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
Click to expand...
Click to collapse
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
KOLIOSIS said:
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
Click to expand...
Click to collapse
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
force70 said:
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
KOLIOSIS said:
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
Click to expand...
Click to collapse
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
force70 said:
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
Click to expand...
Click to collapse
+1
LMFAO,let's hope for the former................... :highfive:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
cortez.i said:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
Click to expand...
Click to collapse
The Adaway update worked. Thanks for that. I followed the N7 forum guide, except that I formatted data using TWRP, and used SU as advised. I uninstalled the log agent with Titanium (and as much of Knox as I could find). I no longer get security notifications, but something is still being tripped by any root activity. The apps that won't start don't require root, for instance, Adobe Reader, and sms and call log restore apps. I cannot see any common cause here. SDfix (latest version) says it can't find any groups, so can't do its work.
I'll nose around the S7 & 8 forums and see if any of these problems are turning up there (dev on the N7 was seriously interrupted by the problems caused by sammy's battery restrictions).
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.