Related
N7105XXUEMK5 ROOT Tutorial – Galaxy Note 2 LTE GT-N7105 JELLY BEAN 4.3 FIRMWARE
Step by step instructions -
Download CF-Root package on your computer and extract the file.
http://download.chainfire.eu/255/CF...tn7105.zipRoot/CF-Auto-Root-t0lte-gtn7105.zip
Download Latest ODIN Software
Switch off your phone and enter into download mode.
To enter into download mode you need to press Volume down button and Home button simultaneously while turning the phone on.
Hope you have your device’s USB drivers installed on your computer if not install it.
Now open ODIN on your computer and connect your device to computer while your phone is on download mode.
When your device will be connected to your computer, one ID:COM boxes will turn yellow after some time.
Select the files that you have to flash or install on your device from the extracted files in first download.
Now in ODIN, check for Auto Reboot and F. Reset Time options.and for the Re-partition option, check only if you have selected .PIT file above.
Click start in ODIN and the flashing will begin.
This flashing might take some time.As soon as the installation ends your device will restart.
Unplug your device from computer.
Switch it off again after it turns on completely and boots to home screen.
Now you need to enter into recovery mode,to enter into recovery switch on the phone while pressing Volume up,Home and Power buttons together.
Navigate with volume buttons to and select wipe data/factory reset from the recovery menu.
Select reboot system now and wait for device to boot again.
You are done, you rooted your Samsung Galaxy Note 2 LTE GT-N7105 to 4.3 Jelly Bean N7105XXUEMK5 Firmware.
Click to expand...
Click to collapse
Method actually supplied by Chainfire.
https://twitter.com/ChainfireXDA
doesnt remove just puts it to the "uninstalled state". so u can choose to install it, from APP menu. KNOX.. then click install.
Don't seem worthwhile to flash. It doesn't have most of the note3/s4 functions
Sent from my GT-N7105 using Tapatalk 4
if your refering to "air command / snote3 etc" . those are n3 exclusive features. the skynote rom has them ported as addons but its touch and go atm some succeeded ( i myself got everything working, except a few syncing issues)
there will be ports though. no doubt
this wont work because of KNOX anyway. stupid feature.
I think knox can be gotten rid of using titanium backup
No need to post this in the dev section
If you didnt make it dont post it
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
can u please move it to general. sorry
UPDATE.
it does work. i just had to update SuperSU i got a few knox errors but it seems to be rooted. now some apps like readers hub etc. wont load (rooting detected)
addition to the tutorial above:
after you started your device again do the following:
1) update supersu through playstore
2) open supersu and update binary > reboot
and if you don't get popups to ask you for permission as soon as you use an app that needs root, open supersu and in settings set the default behavior from "ask" to "always allow".
this gets rid of the fc's and you can enjoy apps with root permission.
All i did was update SuperSU. it said binaries needed updating. i dont have twrp on this so i just selected normal. it rebooted to stock recovery , did nothing i could see. rebooted. updated gplay again. opened superSU didnt give FC. loaded greenify. WIN
all my apps ask "GRANT" permission.
wanam exposed works. got popup for KNOX again. just used it to bypass popup. still have root
4way reboot sticks
R0B3RTF1SH3R said:
All i did was update SuperSU. it said binaries needed updating. i dont have twrp on this so i just selected normal. it rebooted to stock recovery , did nothing i could see. rebooted. updated gplay again. opened superSU didnt give FC. loaded greenify. WIN
Click to expand...
Click to collapse
also used normal on my device, but it didn't reboot to recovery for me, it simply installed and told me that i needed to reboot.
i do however fail to get popup's asking me for permission.
yeah. i think everytime a new app asks it might trigger. but i have wanam exposed removing them. so all looks great. can customize away now. thats all i wanted. THANKS!
There is a nice rom for the 7100 ditto that could be updated for the 7105. It can be found in the 7100 development section. I think with some encouragement the development team would bring it to the 7105
Sent from my GT-N7105 using xda app-developers app
Yeah, 7105 isn't officially supported in neither Skynote nor Ditto. So i can't really get the N3 features on my phone without risking problems anyway. Thus going with the official 4.3 may be the best thing for the LTE people to do, which is why i'm now waiting for someone to release a stock rom modded to take away the knox bootloader. I still haven't decided what to do. There are some really good roms for 7105 in terms of performance and battery life, but those aren't the reasons for why i bought this phone. It feels like there are no good roms for the 7105 that don't also break the many unique features, like the advanced pen functions and the excellent stock camera app's steady-shot and slow-motion functionality. Those are more important to me than performance and battery life.
R0B3RTF1SH3R said:
All i did was update SuperSU. it said binaries needed updating. i dont have twrp on this so i just selected normal. it rebooted to stock recovery , did nothing i could see. rebooted. updated gplay again. opened superSU didnt give FC. loaded greenify. WIN
all my apps ask "GRANT" permission.
wanam exposed works. got popup for KNOX again. just used it to bypass popup. still have root
4way reboot sticks
Click to expand...
Click to collapse
May i know, with the step in post 1, do we have a stock recovery or CWM recovery?
saints5354 said:
May i know, with the step in post 1, do we have a stock recovery or CWM recovery?
Click to expand...
Click to collapse
i only have stock installed. sorry for delay. sleeping.
but when i updated superSU. i selected NORMAL recovery. then it said it would reboot. took about 10 seconds or more then rebooted into normal recovery. I didnt see it update or install anything automated so was like ?????? rebooted. then got messages from KNOX. then after updating my gapps APPS like. "google services" or the one that updates the gplay app. anyway. then it all seemed to work. noticed greenify asked for permission for root. i granted and it didnt get denied by knox. got a warning when trying to load "wanam exposed". then used wanam to get rid of warnings and stuff. even though i still have root.
after wipe/factory settings when I try to open SuperSU for update its blocked straight away with KNOX, any idea?
makes it 0x1
R0B3RTF1SH3R said:
makes it 0x1
Click to expand...
Click to collapse
Yeah... It does lol. But I cant open SuperSU now as its blocked straight away with KNOX, How can I open it to update and change settings for ALLOW?
Every couple of minutes I get message from knox that SuperSU has stopped.....
I am also facing the same problem... looks like the tutorial don't work...
Sent from my GT-N7105 using Tapatalk
kohmax said:
I am also facing the same problem... looks like the tutorial don't work...
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Well it must work somehow because other guys confirms that it actually works
Sent from my GT-N7105 using XDA Premium 4 mobile app
My supersu fc-ed followed by the warning attached
Sent from my GT-N7105 using Tapatalk
Hey there
I hadd my j5 500fn version for a month its on android lollipop 5.1.1
I tried to root it yesterday and it wasnt that nice
I tried rooting by removing google account and enable usb debugging mode and rooted using the odin method with cf root file
As soon as it finished it rebooted with a yellow "set warranty bit:kernel" message on left top of the device name and it all went fine and root checker said it was rooted and could use all root apps but then i tried adding the google account again and restarted my device and then got the custom binary blocked by frp error
I solved that error by flashing the official stock rom again and then i tried rooting again and got the same problem again
It seems like i cant root with a google account and without it i cant install any google play apps
Any suggestion???
Amir3022 said:
Hey there
I hadd my j5 500fn version for a month its on android lollipop 5.1.1
I tried to root it yesterday and it wasnt that nice
I tried rooting by removing google account and enable usb debugging mode and rooted using the odin method with cf root file
As soon as it finished it rebooted with a yellow "set warranty bit:kernel" message on left top of the device name and it all went fine and root checker said it was rooted and could use all root apps but then i tried adding the google account again and restarted my device and then got the custom binary blocked by frp error
I solved that error by flashing the official stock rom again and then i tried rooting again and got the same problem again
It seems like i cant root with a google account and without it i cant install any google play apps
Any suggestion???
Click to expand...
Click to collapse
Hey any help would be appreciated there many apps i use which require root
Hey there any help ??!
Have you enabled OEM Unlocking in Developer Options?
I didnt check that
Al i tried was removing my google account and enabling usb debugging
es0tericcha0s said:
Have you enabled OEM Unlocking in Developer Options?
Click to expand...
Click to collapse
I would try that but ate there any risks of unrepairable bricks or boot loops ??
Amir3022 said:
I would try that but ate there any risks of unrepairable bricks or boot loops ??
Click to expand...
Click to collapse
Not from enabling that option, no.
es0tericcha0s said:
Not from enabling that option, no.
Click to expand...
Click to collapse
So di you suggest teying to root with oem disabled??
?
The question was whether you have enabled OEM unlocking in the development options. If your phone has this option, it must be enabled for you to load a custom recovery that's used with auto root to root, and then it will flash back the original recovery.
es0tericcha0s said:
?
The question was whether you have enabled OEM unlocking in the development options. If your phone has this option, it must be enabled for you to load a custom recovery that's used with auto root to root, and then it will flash back the original recovery.
Click to expand...
Click to collapse
Ok i will try that and tell you the results
es0tericcha0s said:
?
The question was whether you have enabled OEM unlocking in the development options. If your phone has this option, it must be enabled for you to load a custom recovery that's used with auto root to root, and then it will flash back the original recovery.
Click to expand...
Click to collapse
I just tried rooting with oem enabled but its the same still getting the yellow set bit warranty:kernel message on startup
Amir3022 said:
I just tried rooting with oem enabled but its the same still getting the yellow set bit warranty:kernel message on startup
Click to expand...
Click to collapse
That part doesn't mean anything. Does root still work?
es0tericcha0s said:
That part doesn't mean anything. Does root still work?
Click to expand...
Click to collapse
It works but as soon as i enter my google account and restart i get the blocked by frp error
Odd. I've rooted dozens of Samsung phones and have not come across this. If you are already logged into Google and then enable OEM unlocking and then root, does it still get blocked?
es0tericcha0s said:
Odd. I've rooted dozens of Samsung phones and have not come across this. If you are already logged into Google and then enable OEM unlocking and then root, does it still get blocked?
Click to expand...
Click to collapse
If i try rooting without removing my google account i get ared failed message while rooting with odin
I also realised that knox flag is tripped at 0x1 could that be tbe problem
Please post a link to the guide you are using.
es0tericcha0s said:
Please post a link to the guide you are using.
Click to expand...
Click to collapse
I dont use a guide to do it i just tried this same method on my old j1 and it worked but ut doesnt seem to work here
Here it is:
Remove google account
Enable oem unlock
Turn off mobile and put it on download mode
Flash the cf auto root with odin
Mobile turns on and it root automatically then reboots
A yellow set bit warranty: kernel message in top of the screen
Until now all is fine root works fine and all but as soon as i enter my google account and reboot i get the custom binary blocked by frp error and have to reflash the official rom again to get it to work
Amir3022 said:
I dont use a guide to do it i just tried this same method on my old j1 and it worked but ut doesnt seem to work here
Here it is:
Remove google account
Enable oem unlock
Turn off mobile and put it on download mode
Flash the cf auto root with odin
Mobile turns on and it root automatically then reboots
A yellow set bit warranty: kernel message in top of the screen
Until now all is fine root works fine and all but as soon as i enter my google account and reboot i get the custom binary blocked by frp error and have to reflash the official rom again to get it to work
Click to expand...
Click to collapse
You might not be using the right CF package. Just try TWRP + SuperSU zip method instead.
es0tericcha0s said:
You might not be using the right CF package. Just try TWRP + SuperSU zip method instead.
Click to expand...
Click to collapse
I will tey to search for a guide to that method and tell you the results
http://forum.xda-developers.com/gal...overy-twrp-2-8-7-0-samsung-galaxy-j5-t3219901
http://download.chainfire.eu/supersu-stable
Make sure to boot into TWRP before it boots into the OS to flash SuperSU.
Below you will find instructions how to root this device.
The following procedure has been tested up to firmware MMB29K.J320AUSC2AQA1
KNOX should remain 0x0
However you undertake this at your own risk.
(NOTE: This procedure will also work for the SM-J320AZ (Cricket))
Issues:
Wifi passwords not remembered (fix below)
Stock Flashlight app not working.
Model number may be missing from build.prop (fix below)
Instructions
1.Download 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_J320A_PG1
2. Flash the 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_J320A_PG1.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
3. Install and run Kingroot:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
You may need to run Kingroot several times to gain successful root.
4. 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
Alternative (free) method to replace Kingroot:
Follow Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Don't flash the boot partition with Flashfire, uncheck.
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
5. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
6. Model number fix:
http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
7. To fix “Unauthorized actions have been detected”
disable 'Security log agent'
Enjoy your rooted device.
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN in the AP slot.
https://www.androidfilehost.com/?fid=745425885120713788
J3 forum link: https://forum.xda-developers.com/t/galaxy-j3-2016
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Thanks bud. Your post in the other thread convinced me to purchase this device... so far so good
To everyone else, I had to use the patched version of supersu me to remove kingroot
Bugs in the system
So i reflashed the stock rom, everything was great. when i reflashed the file you gave us, debugging has failed to work as well as the flashlight. other than that no issues so far
bobbyp1086 said:
So i reflashed the stock rom, everything was great. when i reflashed the file you gave us, debugging has failed to work as well as the flashlight. other than that no issues so far
Click to expand...
Click to collapse
What do you mean debugging does not work? Adb is enabled by default, it's an engineering boot image.
ashyx said:
What do you mean debugging does not work? Adb is enabled by default, it's an engineering boot image.
Click to expand...
Click to collapse
instead of it asking if i want the computer to read i get this
bobbyp1086 said:
instead of it asking if i want the computer to read i get this
Click to expand...
Click to collapse
What response do you get for
adb devices
In adb?
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
DamienMc said:
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
Click to expand...
Click to collapse
How is an older firmware going to be better when most people will already be running AQA1 firmware?
ashyx said:
What response do you get for
adb devices
In adb?
Click to expand...
Click to collapse
The generic. But then i set the directory to sdk/platformtools and it worked.
But flashlight gone. Keyboard,google services and cell gone. Cant uninstall kingroot with every method out there and my phone is glitching
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
DamienMc said:
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
Click to expand...
Click to collapse
Mine is stock duos, i love the stock rom, but my conputer died this morning,no hopes of odin
bobbyp1086 said:
The generic. But then i set the directory to sdk/platformtools and it worked.
But flashlight gone. Keyboard,google services and cell gone. Cant uninstall kingroot with every method out there and my phone is glitching
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
Mine is stock duos, i love the stock rom, but my conputer died this morning,no hopes of odin
Click to expand...
Click to collapse
King root can be replaced with supersu me or the script. It can also be easily uninstalled via its settings.
What did you actually install?
My system went haywire. I need a command thru terminal on android to factory reset, can't boot into recovery.
bobbyp1086 said:
My system went haywire. I need a command thru terminal on android to factory reset, can't boot into recovery.
Click to expand...
Click to collapse
Just hold POWER + HOME + VOL DOWN until the device reboots then immediately change to POWER + HOME + VOL UP to get in to recovery mode or in Terminal type
su
reboot recovery
.
Thats a no go, can't boot up. kingroot seems to have killed my phone i just get "unfortunatley System UI has Stopped" when i power up. I will reflash withwork comp and update in a few hours...
bobbyp1086 said:
Thats a no go, can't boot up. kingroot seems to have killed my phone i just get "unfortunatley System UI has Stopped" when i power up. I will reflash withwork comp and update in a few hours...
Click to expand...
Click to collapse
You can't possibly have lost the recovery, nothing has touched it. It does take a short while for stock recovery to boot.
ashyx said:
Just hold POWER + HOME + VOL DOWN until the device reboots then immediately change to POWER + HOME + VOL UP to get in to recovery mode or in Terminal type
su
reboot recovery
.
Click to expand...
Click to collapse
ashyx said:
You can't possibly have lost the recovery, nothing has touched it. It does take a short while for stock recovery to boot.
Click to expand...
Click to collapse
Iam lost as to how it happened as well lol but its ok, just a tester phone for fun 3rd time i have done something wrong :laugh:
---------- Post added at 04:33 PM ---------- Previous post was at 04:12 PM ----------
Reflashed Stock Firmware, regained access to recovery, factory reset and back up and running. i actually noticed some new features in recovery. i can actually apply update from sd now, whereas before i could not access files on sd, looks like dm-verity is also gone, or at least not showing up in recovery as before (maybe because it was a failed test) also the start up of the phone has skipped the initial set up (no add account or set up password) and the main screen is way more crisp and clear than what i had on before, even with the other 3 reflashes i have previously done. so far so good though
DamienMc said:
Thanks bud. Your post in the other thread convinced me to purchase this device... so far so good
To everyone else, I had to use the patched version of supersu me to remove kingroot
Click to expand...
Click to collapse
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
bobbyp1086 said:
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
Click to expand...
Click to collapse
The model number missing is a known issue. You just need to edit the build.prop and put it back.
See this link for more info: http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
bobbyp1086 said:
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
Click to expand...
Click to collapse
Used an old version, 9.7.4P
And I only got the script to work once :/
DamienMc said:
Used an old version, 9.7.4P
And I only got the script to work once :/
Click to expand...
Click to collapse
ok so the script is working but there is a different way
1. install kingroot 4.5 from apk mirror
2. Run script
3. update Su
4. update Binary
(i had to reinstall kingroot and deny kingroot root permission before binary would update and uninstall and keep root)
it seems denying kingroot root permission keeps the root on the device, letting su take over for root permission and uninstall of kingroot.
i know it seems weird but it works, the hang up was updating su, which you can do from google play
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
Anyone have a stock "Build.prop" for this model
bobbyp1086 said:
Anyone have a stock "Build.prop" for this model
Click to expand...
Click to collapse
I'll upload it later.
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
OP, is it okay if I don't have original factory sync cable in hands?
volibyro said:
OP, is it okay if I don't have original factory sync cable in hands?
Click to expand...
Click to collapse
Yeah its ok you just run into less issues with original cable.
**Working on updating links I have a slow upload speed though.
HideTheCookies said:
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
Click to expand...
Click to collapse
If u want to switch to SuperSu from KingoROOT, the best and easiest method would be backing up ur phone and performing a soft reset. Afterwards simply install SuperSu, the superuser binary is already installed from kingroot - no worries, just update it normally via SuperSU and disable KNOX after the update is complete.
That switch idea of yours might get you bricked
Confirmed it works now we need a recovery so we can just flash su
SuperSUme works really really well lol, this phone is 32bit only any1 wanna try 4 a recovery?
Thxx bro
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
gravyd316 said:
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
Click to expand...
Click to collapse
Agreed about flashing the recovery, but you need to be rooted with KingOroot to get SuperSUme to work, & it helps to just keep the screen timeout turned off thru this process , after it says "complete" I downloaded SuperSU & installed, updated, "disabled" knox, & I can also use flashfire although its pretty worthless for anything other than backups, as the little AROMA shell emulator thingy does run after the verizon logo is showing, which indicates to me yea its locked down pretty solid lol.
I tried Safestrap & it gave me a /SS folder in my /etc so I looked into that but I can't manage to figure out how I should go placing the files to make it work lol. But i do know this thing is 32bit ONLY, so compiling the j100H twrp for instance will NOT flash no matter what we do to the bootloader, it will bootloop since the architecture is for a 64bit SoC, we need someone to compile the j100H twrp in a 32bit only compatible architecture, & then you can easily flash it like cake, & TWRP should do the rest like all other Samsung phones O.O
its gotten to the point these are all the apps I have when i restore haha, if you wanna PM me about working together to get this thing a little more flexible I'm always open to ideas . I only use this thing as a hotspot but would totally like to see a recovery at least make it over & from there I could definitely start the ROM bringup
Will I get bricked by doing this with Verizon
Weegee1 said:
Will I get bricked by doing this with Verizon
Click to expand...
Click to collapse
you cant hard brick this device, restore with ODIN start over.
LilAnt530 said:
you cant hard brick this device, restore with ODIN start over.
Click to expand...
Click to collapse
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
LilAnt530 said:
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
Click to expand...
Click to collapse
THANKS! sorry last noob question, will I lose root if I turn my phone off
Weegee1 said:
THANKS! sorry last noob question, will I lose root if I turn my phone off
Click to expand...
Click to collapse
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
LilAnt530 said:
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
Click to expand...
Click to collapse
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Weegee1 said:
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Click to expand...
Click to collapse
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
LilAnt530 said:
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
Click to expand...
Click to collapse
And with SuperSU, is that one more stable
Below you will find my procedure to root the SM-J727P Galaxy J7 Perx / MSM8953
This procedure has only been tested on J727PVPU1AQB9 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
This took some doing and was a tough nut to crack. I don't own this device and much thanks goes to those that stuck with it in the testing phase, without whom it would not have even been possible. Credits below.
To see how we got here and before asking any questions click this link: https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
J727P-SuperSU-v2.79-SR3_rooted_boot_AQB9
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the J727P_SuperSU-v2.79-SR3_rooted_boot_AQB9.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: ME, @Borams @Project89Odin @Chainfire and special thanks to @RS.85243
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
scbcskin said:
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
Click to expand...
Click to collapse
Whoops glad you pointed that out, forgot to include that step!
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
scbcskin said:
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
Click to expand...
Click to collapse
When you open the SuperSU app does it complain about no binary installed?
ashyx said:
When you open the SuperSU app does it complain about no binary installed?
Click to expand...
Click to collapse
It sure does!!
scbcskin said:
It sure does!!
Click to expand...
Click to collapse
Strange, it works perfectly on Marshmallow. Looks like we're going back to the old method of manually pushing su.img to data!
Will update shortly.
Have you tried rebooting again to see if works after that?
Just did a reboot and same deal.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Project89Odin said:
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Click to expand...
Click to collapse
Say again. Can you explain in more details, not sure I understand?
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Project89Odin said:
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Click to expand...
Click to collapse
OK I see. Can you do me a favour and test the updated version?
First delete su.img from /data or just unroot from SuperSU settings then reboot to download mode and install the new version. Your device should auto re-root.
https://www.androidfilehost.com/?fid=961840155545567256
ashyx said:
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
Click to expand...
Click to collapse
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
After deleting su in /data andfull unroot, flashed newer build and supersu reports no binary, not even one to update, no root
scbcskin said:
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
Click to expand...
Click to collapse
Thanks for confirming. OP updated.
You can use Flashfire to install Xposed.
ashyx thank you for your efforts. Thanks to everyone else that helped as well. Guess what I just ordered. Can't wait to get my new phone and root, install viper4android. Both are a must for me and I never own a phone I can't have both on.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
When the reboot is repeated,
please flash the original firmware to odin
and try again from the beginning.
from CIAO7
after unrooting, repeating format is required to reroot. Works flawless. Thankyou again. Looking forward to a fully functional twrp now!!
Project89Odin said:
Thankyou again. Looking forward to a fully functional twrp now!!
Click to expand...
Click to collapse
It's next on my hit list. Just need to figure out why the source built kernel doesn't boot.
Now that root is achieved there's more chance of finding out what's going on, so I'll be calling on you guys again at some point for logs.