Hey guys,I have noticed a few problems after rooting my Galaxy S3(this tutorial).
- My SuperSU crashes often (usually soon after booting up the phone)
- I can't access the "user info" part of the menu (that part of the Settings where you can
enter your own message and it displays on the lock screen),after I click on it I get an error message saying "settings has closed"
And now for a stupid question: could I have rooted an already rooted phone?
(I'm asking this because I had my phone SIM unlocked right after I bought it,and it might have been rooted then,I'm not sure.
Although,before I rooted I downloaded 2 different root-checker apps and checked whether or not I'm rooted,and they both said NO.)
U used cf-root,best choose.open supersu app,if it ask u to update binaries press yes.
If u already did this then swipe to the last page scroll down to "reinstall from market" when done restall from play store,open supersu update binaries.done
zodiaxe66 said:
U used cf-root,best choose.open supersu app,if it ask u to update binaries press yes.
If u already did this then swipe to the last page scroll down to "reinstall from market" when done restall from play store,open supersu update binaries.done
Click to expand...
Click to collapse
I tried reinstalling from Market,but the binary update still doesn't go through,I get a message saying "Instalation failed"
gnjuss said:
I tried reinstalling from Market,but the binary update still doesn't go through,I get a message saying "Instalation failed"
Click to expand...
Click to collapse
Reboot and try again,if it doesn't update,Then u are not rooted.
Reflash cf-root using Odin.it rarely happens that root isn't applied properly,but it does happen.
Reboot and update binaries
Thank You very much,I will root again using the same method.
Should I first wipe anything,or unroot...? Or should I just go through the same process again.
OK,I have just finished reflashing the Odin root,and everything is the same.
Now when I try to open the CWM app,I get the error message: "SuperSU has stopped",
and then the CWM app opens.
I gave Superuser permission for CWM,now it doesnt work properly.
It seems every app breaks down after I give it permission.
gnjuss said:
OK,I have just finished reflashing the Odin root,and everything is the same.
Now when I try to open the CWM app,I get the error message: "SuperSU has stopped",
and then the CWM app opens.
I gave Superuser permission for CWM,now it doesnt work properly.
It seems every app breaks down after I give it permission.
Click to expand...
Click to collapse
CWM app is a bit useless on SGS3 until its updated .
Go to Play uninstall Super User and reinstall can clear a misbehaving SU.
jje
Related
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
Ive been using ViperDNA which comes with what seems like a custom SuperUser type of all in it.
But when I origionally rooted my phone, i seem to remember having an issue with SuperSU, and the first time i rooted i said screw it and just installed Superuser without any problems. The second time i rooted, i Installed SuperSU, then had to download Superuser form the Android Market, to update the binary, which updated it for SuperSU, and that solved my problem.
When you try to open an app that needs to use root access, do you get the notification asking for permission?
perhaps the "other" superSU/busybox package that you used didn't properly do what it needed to do?
I see the link on that tutorial is broken, fortunately i have the file that i originally downloaded form that very same tutorial saved to my hard drive, and now uploaded to DropBox if you would like to download it and try flashing this zip while in recovery to see if it gives you a proper root.
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
BigRed35m said:
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
Click to expand...
Click to collapse
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
BigRed35m said:
When you try to open an app that needs to use root access, do you get the notification asking for permission?
Click to expand...
Click to collapse
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
xDexter said:
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
Click to expand...
Click to collapse
It's difficult for me to troubleshoot when i haven't had to fix this problem since december haha.
The tampered, and unlocked is standard that is what it shows for everyone who unlocked the boot-loader.
So let me get this straight,
Do me a favor, un-install Superuser, download RootChecker from the market by JoeyKrim, And run it, what does it say?
->When you run it, did it ask for permission from SuperSU?
With just the SuperSU installed, if you run a program that requires root permission (For example, RootChecker), Nothing shows up asking if you want to Allow/Deny?
->When you open SuperSU to update the binary, it fails to update and restarts the APP?
With the SuperSU/BusyBox package flashed, when you install Superuser from the android market and try to update the binary, it *appears* to revert back to an older version of the binary?
-> After updating the binary through Superuser (despite the appparent reversion), if you un-install Superuser, and try to run RootChecker, does it work?
Sorry, i know it is a lot and i'm not much help, i'm troubleshooting blindly and from a distance haha.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Bigandrewgold said:
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Click to expand...
Click to collapse
Yeah this is what I figured out too.
Sent from my HTC6435LVW using XDA Premium HD app
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
orangechoochoo said:
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
Click to expand...
Click to collapse
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Quite a few of us running a version of Supercharged Hatka had problems when they switched to SuperSu,but now they switched back to SuperUser and the problem hasn't reared its head.
First time im success rooting use framaroot 1.4.2 but after factory reset root error and when i try to use frama again.happen is half success:-/ your system partition...bla bla bla
Im confused and looking on internet no one know to root with spec my mobile
Model:andromax u a.k.a innos 6cp
build number :smartfren_4.1.2_i6cp_v1.0.g
I already try some apl z4root/universalandroot/exinos abuse/binary
And nothing happen
When im use binary report on stock recovery is root success but after reboot check and not root
Help me please,thank you
and please explain in detail what steps should I do
agustien said:
First time im success rooting use framaroot 1.4.2 but after factory reset root error and when i try to use frama again.happen is half success:-/ your system partition...bla bla bla
Im confused and looking on internet no one know to root with spec my mobile
Model:andromax u a.k.a innos 6cp
build number :smartfren_4.1.2_i6cp_v1.0.g
I already try some apl z4root/universalandroot/exinos abuse/binary
And nothing happen
When im use binary report on stock recovery is root success but after reboot check and not root
Help me please,thank you
and please explain in detail what steps should I do
Click to expand...
Click to collapse
I would be happy to help. First lets try this, go to Play Store and install SRT Appscanner please, then open the app and tell me if it says either of the bugs say vulnerable. Also, what version of Android does your device have on it currently?
Im using android 4.1.2 version
Sent from my Andromax U using xda premium
Bug 8219321: vulnerable
Bug 9695860:vulnerable
The security vulnerability has not been fixed on your device. Contact your device vendor to check when an update for your device will be released
Sent from my Andromax U using xda premium
agustien said:
Bug 8219321: vulnerable
Bug 9695860:vulnerable
The security vulnerability has not been fixed on your device. Contact your device vendor to check when an update for your device will be released
Sent from my Andromax U using xda premium
Click to expand...
Click to collapse
Ok, that is good actually. Now go to this link and download Impactor please, unzip the file onto your PC then double click the Impactor application, then on box that pops up leave it on # drop Supersu su to /system/xbin/su and hit start. IF it says successful the go to Play Store and download Supersu, when it opens it will ask to update binary, choose continue then normal and you should have root! Use root checker to verify afterwards if you like. Good luck!
http://www.cydiaimpactor.com/
You might need to install drivers for your device so the root program can communicate with your device, Impactor has a button to help install drivers but if it fails let me know and I can give you some generic android drivers if nothing else
Hope this helps!
I've managed to install all the drivers, but in time will always fail to install the adb drivers
it say
cannot start this hardware
there was a problem installing this hardware
android composite adb interface (Qualcomm usb ID)
windows cannot load the device driver for this hardware
the driver may be corrupted or missing (code 39)
agustien said:
I've managed to install all the drivers, but in time will always fail to install the adb drivers
it say
cannot start this hardware
there was a problem installing this hardware
android composite adb interface (Qualcomm usb ID)
windows cannot load the device driver for this hardware
the driver may be corrupted or missing (code 39)
Click to expand...
Click to collapse
Try installing this on your PC, it will help find drivers for your device. If that don't work we will use the generic drivers:
http://www.snappea.com/
Also - Do you have USB debugging enabled? Go to Settings > Developer Options > and make sure USB debugging is checked otherwise the PC cant use ADB drivers even if correct ones are installed.
ntactsai difhes
I finally managed to install the driver
I've tried to use cydia impactor but it's always like this
error
/ data/local/tmp/impactor-8 [11]: mkdir: not found
agustien said:
I finally managed to install the driver
I've tried to use cydia impactor but it's always like this
error
/ data/local/tmp/impactor-8 [11]: mkdir: not found
Click to expand...
Click to collapse
Ok, if no luck with Impactor, try this:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7
try srsroot
I think something wrong with my phone
Some root checker said you are root but the other said no.
I already use vroot and eroot on process they said success in rooting but where???
I still cant use titanium backup and when i write su on terminal emulator said su is excited permission denied
Im very cunfused
Sent from my Andromax U using xda premium
agustien said:
I think something wrong with my phone
Some root checker said you are root but the other said no.
I already use vroot and eroot on process they said success in rooting but where???
I still cant use titanium backup and when i write su on terminal emulator said su is excited permission denied
Im very cunfused
Sent from my Andromax U using xda premium
Click to expand...
Click to collapse
Ok, do you have SuperSU or Superuser on your device? First we will have to sort that out. Both apps do the same thing, but it is not good to have more than one installed at same time or you get conflicts on whether you are rooted because the apps cant decide who controls root access between them all. How many superuser apps do you have counting the chinese one Vroot installed/ Usually when I use Vroot, it installs the chinese superuser app then I instal SuperSU from play store, when you go to update binary in SuperSU the first time you open the app, make sure you hit the right button in the chinese pop up that should pop up. If you have alot of trouble figuring out this part, feel free to install Teamviewer on your PC and I can connect to you and help you get this sorted, I have tools that will let me see your phone on your PC's screen so it wont take long to fix I dont think.
No i dont have supersu apl in my phone.
What you need about my mobile?
I will send you everything you need.
I check in google and i think my mobile same with innos i6c.
But all site about this product on chinesse language and i cant understand at all
I need install teamviewer only on pc? Or mobile to?
agustien said:
No i dont have supersu apl in my phone.
What you need about my mobile?
I will send you everything you need.
I check in google and i think my mobile same with innos i6c.
But all site about this product on chinesse language and i cant understand at all
Click to expand...
Click to collapse
Ok, first go install SuperSU from Play Store. Once installed open the app and it should pop up a message saying it needs to update binary. Choose continue then choose normal. You should then get a pop up box that from the chinese root app, make sure you tap the right hand button to allow the english SuperSU to install binary. Let me know if it fails after this, if it completes with no errors reboot phone once. Upon rebooting look to see if the other chinese root app is still there. If it is still there then I will need you to go back into SuperSU app and then choose setttings, within settings please choose "Install SuperSU into /system" This may reboot phone but that is ok, if it does not reboot then reboot it yourself. (If it reboots phone itself, it had to do that to clean up files first and you will need to go back into SuperSU and install SuperSU to /system again and reboot once more) Upon reboot chinese root app should now be gone and you should have root.
I do not need any info about your mobile, I got everything I need to help already. I was suggesting Teamviewer meaning if you cant get root yourself, I was offering to connect to your PC and do it for you. If you would feel more comfortable just doing it yourself that is fine but I was just making the offer in case you were to the point you just wanted it done and over!
Let me know how it goes.
I just need flash my firmware and now my phone is rooted
Thanks for help me and sori for late reply
Sent from my Andromax U using xda premium
agustien said:
I just need flash my firmware and now my phone is rooted
Thanks for help me and sori for late reply
Sent from my Andromax U using xda premium
Click to expand...
Click to collapse
no worries! I am glad it worked!
Hi,
I have succesfully updated my razr xt910 to official JB using RSDLite and UK ROM but failed to restore the root from OTArootkeeper.
Went on many threads and found one "easy way" to root the device using virtual box and rootbionic.ova. It ended up success and I see the superuser icon in my phone.
Problem is everytime I open the superuser app, it asks me to update the superuser binary and it always failed.
What should I do next? Please help.
Thanks.
romeotango said:
Hi,
I have succesfully updated my razr xt910 to official JB using RSDLite and UK ROM but failed to restore the root from OTArootkeeper.
Went on many threads and found one "easy way" to root the device using virtual box and rootbionic.ova. It ended up success and I see the superuser icon in my phone.
Problem is everytime I open the superuser app, it asks me to update the superuser binary and it always failed.
What should I do next? Please help.
Thanks.
Click to expand...
Click to collapse
Have you tried to download it directly from playstore? That might help.
Sent from my XT910 using xda premium
u can try my way to root XT910
http://forum.xda-developers.com/showthread.php?t=2402943
will do! thanks for responding
AztekSoul said:
Have you tried to download it directly from playstore? That might help.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Hi, already did this. The result was the same. After installing the superuser, it will still ask me to update the su binary.
Thank you.
lanhoter said:
u can try my way to root XT910
http://forum.xda-developers.com/showthread.php?t=2402943
Click to expand...
Click to collapse
Hi, thank you very much! Now my RAZR is already ROOTED.
It just that all the confirmation dialog box from superuser now appear in Chinese. Do I still need to install the superuser from Cyanogen?
Because everytime I open the superuser app from Cyanogen, it is strangely always asking me to update the superuser binary, and although the status was success, when I open the superuser app again, the same thing happens again.
But yes, the superuser is working. I have tested it with DroidWall and Root Uninstaller.
Many thanks
romeotango said:
Hi, already did this. The result was the same. After installing the superuser, it will still ask me to update the su binary.
Thank you.
Hi, thank you very much! Now my RAZR is already ROOTED.
It just that all the confirmation dialog box from superuser now appear in Chinese. Do I still need to install the superuser from Cyanogen?
Because everytime I open the superuser app from Cyanogen, it is strangely always asking me to update the superuser binary, and although the status was success, when I open the superuser app again, the same thing happens again.
But yes, the superuser is working. I have tested it with DroidWall and Root Uninstaller.
Many thanks
Click to expand...
Click to collapse
after superuser(Cyanogen verison) update binary successfully, go to system/app delete superuser.apk(chinese verison) and reboot
superuser(Cyanogen verison) will take over as root tool
bcz cannot read chinese, so came out this way to delete superuser(chinese verison)
u can see Post #8 in my thread
http://forum.xda-developers.com/showthread.php?t=2402943
lanhoter said:
after superuser(Cyanogen verison) update binary successfully, go to system/app delete superuser.apk(chinese verison) and reboot
superuser(Cyanogen verison) will take over as root tool
bcz cannot read chinese, so came out this way to delete superuser(chinese verison)
u can see Post #8 in my thread
http://forum.xda-developers.com/showthread.php?t=2402943
Click to expand...
Click to collapse
Ah, sorry totally missed this part. Will try later.
Thank you once again.
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
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.