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).
Related
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.
Wondering if anyone in the know has heard of any development going on for this device? I recently bought one and it's not a bad phone for the price, but I've seen absolutely -nothing- on it anywhere online for the most part. It's barely root-able with what I've been able to find, and no custom recovery or really anything custom has popped up that I've seen.
Not sure if it's just that it's been only a few months since the phone came out, or if it's just not that great a phone. I upgraded from an HTC Desire 510 to this, and it was heavily customized/rooted/etc, and I want so badly to get back to where I was with it on this phone I cant stand it!
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
triiuzii said:
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
Click to expand...
Click to collapse
Right now rooting isn't the problem so much as keeping root. Because apparently the colonel has protection and will remove root whenever you reboot. That means things that require root on boot like backups, Xposed and a lot of other things won't work for us until someone complies a kernel with root protection removed. You can do some debloating and possibly the AdAway but that's about it right now.
*kernel. Damn voice to text.
That sucks. I upgraded from an LG Volt and I was able to do a whole bunch of stuff on it. The J3 is still very new, so hopefully development will happen soon.
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
mallamike said:
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
Click to expand...
Click to collapse
I guess that would depend on what you have experience with and what you can do. Thus-far root has been able to be achieved with Kingroot, though it wont stick through a power cycle (reboot/power off/etc), and using any of the methods available (at least that I'm aware of, only found two legitimate ones) to replace Kingroot with SuperSU (to facilitate having root stick past the reboot hopefully) causes a soft-brick every time forcing a re-flash of stock firmware through Odin.
At the very least make your voice heard, if nothing else hopefully more popularity will come this devices way and we'll see some development for it. My roommate is considering writing something for it, but it is a long process working solo, so anyone who has experience working with kernels or editing stock rom/writing custom roms feels up to helping out, shoot me a message and I'll get it over to him. He's a fairly experienced programmer and picks up what he doesn't already know pretty quickly.
Got one recently too. Would also appreciate any more information on rooting.
I have a J320A (AT&T) came stock with 6.0.1, can help test if needed
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Will this version of TWRP work on the Att variant running 6.0.1? Is there a way to root that device yet?
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
TechShui said:
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
Click to expand...
Click to collapse
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
what about the
SM-J320VPP = the verizon pre paid planversion. any working roots for me yet?
oh pretty pleeeeeez
Azhero said:
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
Click to expand...
Click to collapse
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
AnierinB said:
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
Click to expand...
Click to collapse
It doesn't work tried it 3 times. I even tried other ones no luck. They locked this thing down. Im surprise chainfire haven't tried this phone yet.
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Gotbootloopedtoomuch said:
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Click to expand...
Click to collapse
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
darknaio said:
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
Click to expand...
Click to collapse
Thank you so much! I tried using Odin to flash a software update and it worked perfectly. The phone is back up and running and all of the files are still there!
Right now i have TWRP 3.0.2 with supersu and i havent lost root yet also had no problem switching between backups, xposed working fine and also overclock too with setcpu, im currently running 5.1.1 using j320FN but TWRP was from j320F, i will put up links to the files if any of you are willing to try its up to you.
TWRP flash through odin : http://www.mediafire.com/download/blk7qa90vs6wik3/TWRP_3.0.2-0_SM-J320F.tar.tar
Supersu flash through recovery then update through playstore then install busybox after through playstore : http://www.mediafire.com/download/cpv2c71cp11x41f/UPDATE-SuperSU-v2.76-20160630161323.zip
Remember to turn on usb debugging and turn on oem unlock before flashing recovery, also if you manage to get recovery press they grey box on the right to change language to english. Hope this might help somebody on here because we really need full root for everyone.
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.
Has anyone successfully rooted A9 2018 (A920F)?
Is anyone working on it?
How to root
you can use rooting tool or a application to root your galaxy. But there are pros and cons. So you have to consider about them. You can use a single click rooting applications but i can not guarantee it is safe. So you have to do it at your own risk.
We can start with that. That's a good option. I hope it will work.
Mod edit: Link removed - Untrusted host
Has anyone successfully rooted this model?
varadinum said:
We can start with that. That's a good option. I hope it will work.
Mod edit: Link removed - Untrusted host
Click to expand...
Click to collapse
This is only the firmware, not for root.
TP427 said:
This is only firmware, not for root.
Click to expand...
Click to collapse
You should click further:
How to root Samsung Galaxy A9 2018 SM-A920F via PDA/AP odin ->*Read here
This site has instructions, however the TWRP version for the A920F is not listed on the site.
Yes, there is no twrp for A920F
I have tried KingRoot, KingoRoot, Dr.fone. But all failed
We need to get some traction on this. Has anyone submitted a request to get TWRP on this model?
I managed to get this rooted with EFT dongle. There was no other method that I could find.
Codename_Falcon said:
I managed to get this rooted with EFT dongle. There was no other method that I could find.
Click to expand...
Click to collapse
Excuse me but how are you? What is eft dongle? Can you help us?
This is my first Samsung phone. I do not know myself. Please be so nice and help me. Thanks!
I just send email to support TWRP. Maybe the more they get such messages, the sooner they will deal with it
varadinum said:
Excuse me but how are you? What is eft dongle? Can you help us?
This is my first Samsung phone. I do not know myself. Please be so nice and help me. Thanks!
Click to expand...
Click to collapse
I am doing okay, thank you! Please check out the following for info.
http://forum.gsmhosting.com/vbb/f10...t-dongle-new-exclusive-method-2018-a-2526388/
Codename_Falcon said:
I am doing okay, thank you! Please check out the following for info.
http://forum.gsmhosting.com/vbb/f10...t-dongle-new-exclusive-method-2018-a-2526388/
Click to expand...
Click to collapse
It works? Can step by step instructions, starting with unlocking the bootloader, TvRP and to the end? From the very beginning. Thank!!! Sorry, Google translation.
Codename_Falcon said:
We need to get some traction on this. Has anyone submitted a request to get TWRP on this model?
Click to expand...
Click to collapse
I submitted the request for TWRP on TWRP builder today.
Rooted Successfully
SM-A920F can be successfully rooted by OneClickRoot. If you pay them, they can help you root it manually. My device has been rooted successfully.
But now, the problem is TWRP. Technicians from OneClickRoot told me no TWRP is available for this device and they can't help. So I submitted the request on TWRP builder. But nearly 40 devices are ahead of me waiting for TWRP building.
Is there anyway to get the TWRP faster?
TP427 said:
SM-A920F can be successfully rooted by OneClickRoot. If you pay them, they can help you root it manually. My device has been rooted successfully.
But now, the problem is TWRP. Technicians from OneClickRoot told me no TWRP is available for this device and they can't help. So I submitted the request on TWRP builder. But nearly 40 devices are ahead of me waiting for TWRP building.
Is there anyway to get the TWRP faster?
Click to expand...
Click to collapse
Does it trip knox counter?
Edit: I said screw the knox counter, I'm going with it. Everything was all green until it asked me to register so I entered some name and email. Then it asked me 30$(or 40$ if you're doing it from the computer and not the app). Definitely not worth it to root.
Edit 2: I'm now trying the Magisk boot file patch method, which can work without root and custom recovery. Unlocked developer options, checked OEM unlock option(which needed a factory reset)
downloaded stock firmware, extracted boot.img from it, patched and repacked it using magisk manager and finally flashed it to phone using odin. Knox counter is already tripped. It required another factory reset when I booted it after flashing(It said device integrity was compromised and it needed a factory reset, so I did it) but no bootloops. Aaand after I waited long enough to be able to install magisk manager again, I found out that my attempt was a success! I can now enjoy systemless root on my phone, at the expense of tripping the knox counter of course.
And of course, no luck on twrp side, which could've made the whole process easier for me.
Edit 3: It may sound simple when I write it like this here but it actually is a lengthy process. In fact, I looked up multiple guides on the internet, at least one for each part I talked about above and sometimes more than one since this is my first samsung phone ever.
Edit 4: One last thing, I can pass SafetyNet as well now, which was failing right after I did the OEM Unlocking and factory reset but before I actually rooted it with magisk.
thesingular said:
Does it trip knox counter?
Edit: I said screw the knox counter, I'm going with it. Everything was all green until it asked me to register so I entered some name and email. Then it asked me 30$(or 40$ if you're doing it from the computer and not the app). Definitely not worth it to root.
Edit 2: I'm now trying the Magisk boot file patch method, which can work without root and custom recovery. Unlocked developer options, checked OEM unlock option(which needed a factory reset)
downloaded stock firmware, extracted boot.img from it, patched and repacked it using magisk manager and finally flashed it to phone using odin. Knox counter is already tripped. It required another factory reset when I booted it after flashing(It said device integrity was compromised and it needed a factory reset, so I did it) but no bootloops. Aaand after I waited long enough to be able to install magisk manager again, I found out that my attempt was a success! I can now enjoy systemless root on my phone, at the expense of tripping the knox counter of course.
And of course, no luck on twrp side, which could've made the whole process easier for me.
Edit 3: It may sound simple when I write it like this here but it actually is a lengthy process. In fact, I looked up multiple guides on the internet, at least one for each part I talked about above and sometimes more than one since this is my first samsung phone ever.
Edit 4: One last thing, I can pass SafetyNet as well now, which was failing right after I did the OEM Unlocking and factory reset but before I actually rooted it with magisk.
Click to expand...
Click to collapse
It did trip knox. I don't know if there is a rooting method without tripping knox?
I'm waiting for TWRP. Request has been sent to TWRP builder
Hi!
I want to hide su binary from my phone temporarily to trick apps into thinking that my phone is not rooted. I thought I could just rename su binary from TWRP but I could not find that. It's not inside /system/xbin/ or /system/bin/.
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Thanks!
V0latyle said:
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Click to expand...
Click to collapse
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
sysctl said:
Thanks!
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
Click to expand...
Click to collapse
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
V0latyle said:
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
Click to expand...
Click to collapse
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
sysctl said:
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
Click to expand...
Click to collapse
Unrooting won't wipe data. It doesn't matter how you do it.
V0latyle said:
Unrooting won't wipe data. It doesn't matter how you do it.
Click to expand...
Click to collapse
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
sysctl said:
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
Click to expand...
Click to collapse
I honestly don't know that much about Knox but having it disabled doesn't make your device any more vulnerable than being rooted. Be mindful of what you install, and don't grant root access to apps you don't trust.