Related
Hi i just update to 2.3.4 and try to root it and work fine with me
Download this file and move it to your NS
http://www.mediafire.com/?0a4abln7x3gjgrv
after your flash the recovery then ..
On your phone, use the volume key to highlight "recovery". Press power to boot into recovery.
in the recovery screen, select mounts and storage
mount /system
mount /data
go back, and choose install zip from sd card
choose "choose zip from sd card"
pick the su package zip file you copied over earlier
choose Yes
when done, reboot.
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
it is for the i9023??
So after I flash 2.3.4 update, all I have to do is reboot and flash SuperUser again, and then Nexus S is re-rooted again?? Thanks!
amjad_2020 said:
Hi i just update to 2.3.4 and try to root it and work fine with me
Click to expand...
Click to collapse
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
I have a custom kernel. How do I Install 2.3.4
Sent from my Nexus S using XDA App
italia0101 said:
I have a custom kernel. How do I Install 2.3.4
Click to expand...
Click to collapse
You have to go back to stock GRI40, i.e. with a Nandroid restore?! But this will be the correct thread for you: http://forum.xda-developers.com/showthread.php?t=1055591&page=12
kevin_ngckk said:
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
hehe how on earth can someone provide real feedback on battery life 2 seconds after installation?
Thanks for sharing, I'll wait for Team Douche to implement this on CM7.
Trouble
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
smlmn said:
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
Click to expand...
Click to collapse
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
jungbum said:
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
Click to expand...
Click to collapse
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
Yes, same here SuperUser ist still available, but without any function
on nexus s 9023 ??
what about it ?
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
jamallj said:
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
Click to expand...
Click to collapse
No sorry. It's not possible to install busybox without root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
That means you're not rooted.. you have to root again.
bolabola118 said:
That means you're not rooted.. you have to root again.
Click to expand...
Click to collapse
I've tried to reroot again and totally get result
But I also done that:
!Once you are in recovery mode, select the relevent mounts and storage by Mount / System and Mount / data.
(I can not post links)
Thx
Handymeister said:
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
Click to expand...
Click to collapse
Same situation/problem
For those stock rooted but bootloader locked 2.3.3 users that previously rooting using CWM recovery to update and superuser root method.
You can root the same way...but save the trouble of fastboot recovery step via PC which novice users could be stuck on getting fastboot usb driver to work properly.
0) Just installed ROM Manager (From Market) into your phone
1) Store both 2.3.4 update.zip and SuperUser.zip into SDCard
2) Run ROM Manager
3) Activate CWM Recovery
=> Make sure recovery is installed succesfully..check ROM Manager screen which tell whether the installation is successfully done.
4) Reboot recovery from ROM Manager App
5) Follow thread #1 on the rest
6) After applying update.zip..do not reboot...do a system mount from CWM Recovery then apply SuperUser.zip ..after completing all steps..do a reboot..
Voila your 2.3.4 is installed and rooted..
Thanks, but this way comes to late for me and some other users. We've flashed the update without rooting.
And now we need another way for root ...
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
reflash rom and flash otas in order 1,2,3,4 , THEN update su binary and AFTER THAT install kernel
Sent from my GT-S5360 using xda premium
Maybe your update.zip is corrupted hmm. Try download another update.zip and install it via cwm. Here
http://forum.xda-developers.com/showpost.php?p=26609075&postcount=3
Don't forget to mount system
Sent from my GT-S5360 using xda premium
MaestroCharan said:
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
Click to expand...
Click to collapse
flash stock rom....root again...then update su binary...then flash jbv3 by removing boot.img to not install kuro kernel and to stay with merruk....flash ota 1,2,3,4 one by one.....done....enjoy!!!!! :laugh:
Tried exactly the same!!
denysw0w said:
reflash rom and flash otas in order 1,2,3,4 , THEN update su binary and AFTER THAT install kernel
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
(First of all i thank(ed) all of u for your advises to help me out of this)
I did exactly the same!!
>flash stock>delete ext partition on sd>root>update subinary>flash JB without boot.img>flash all OTAs in order>update suBinary(though its already updated)>kernel MT2.0 pre-final !! :highfive:
But finally i got the same result.
actually i tried it multiple times in different ways..but in vain!
What i hope is that some1 make a cwm flashable zip of that su provided ... which perhaps might help!
Do this thing.....
Go to superuser>>>it will show update binary failed.....than go to settings>>>than disable superuser>>than again enable it.....now u hv root access..
Now go to link2sd & remove superuser.apk
Than install superuser from playstore....dont install supersu
Now their will b no problem...
Sent from my GT-S5360 using xda app-developers app
i will make you tomorrow a flashable zip with the su file provided in the first post to flash via cwm
Sent from my GT-S5360 using xda premium
'disable superuser' means??
anmolsharma1293 said:
Do this thing.....
Go to superuser>>>it will show update binary failed.....than go to settings>>>than disable superuser>>than again enable it.....now u hv root access..
Now go to link2sd & remove superuser.apk
Than install superuser from playstore....dont install supersu
Now their will b no problem...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Sir Anmol,
i cannot understand what exactly u mean by 'disable superuser' !!
and about removing superuser.apk : may i do that with root explorer or L2SD is explicitly required?
but i'm afraid i may not want to go with those 'removing' kind of steps because i already did the whole process of flashing frm start to end many times and now tired and want to settle with some less riskier ways!! :angel:
Anyway, thanks for your reply and support :highfive: :good:
try this bro maybe it will help.flash it with cwm,mount everything.
http://db.tt/3slPTkNX
MaestroCharan said:
Sir Anmol,
i cannot understand what exactly u mean by 'disable superuser' !!
and about removing superuser.apk : may i do that with root explorer or L2SD is explicitly required?
but i'm afraid i may not want to go with those 'removing' kind of steps because i already did the whole process of flashing frm start to end many times and now tired and want to settle with some less riskier ways!! :angel:
Anyway, thanks for your reply and support :highfive: :good:
Click to expand...
Click to collapse
First of all dont call me sir....
Its the working method which i use when i get superuser conflicts....
If u have no problem with root access than go to link2sd & just remove superuser.apk.....
And just download superuser from market.....
Sent from my GT-S5360 using xda app-developers app
thanks brother..i'll try them!!
anmolsharma1293 said:
Do this thing.....
Go to superuser>>>it will show update binary failed.....than go to settings>>>than disable superuser>>than again enable it.....now u hv root access..
Now go to link2sd & remove superuser.apk
Than install superuser from playstore....dont install supersu
Now their will b no problem...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
blackpanther2209 said:
try this bro maybe it will help.flash it with cwm,mount everything.
http://db.tt/3slPTkNX
Click to expand...
Click to collapse
Thanks bro :good:
anmolsharma1293 said:
First of all dont call me sir....
Its the working method which i use when i get superuser conflicts....
If u have no problem with root access than go to link2sd & just remove superuser.apk.....
And just download superuser from market.....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Ok bro i'll try that :highfive:
MaestroCharan said:
Thanks bro :good:
Ok bro i'll try that :highfive:
Click to expand...
Click to collapse
u may also flash other stable kernels like hells,savies etc to solve ur problem if still not solved
As you said...
anmolsharma1293 said:
First of all dont call me sir....
Its the working method which i use when i get superuser conflicts....
If u have no problem with root access than go to link2sd & just remove superuser.apk.....
And just download superuser from market.....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Did as u said : remove superuser apk and reinstall from market.
But still the same..
Finally, to me it looks like a problem associated with the kernel.
samir basnet said:
u may also flash other stable kernels like hells,savies etc to solve ur problem if still not solved
Click to expand...
Click to collapse
Yo bro..looks like its time for me to look for some other kernelsThanks for the suggestion anyway!!
MaestroCharan said:
Did as u said : remove superuser apk and reinstall from market.
But still the same..
Finally, to me it looks like a problem associated with the kernel.
Yo bro..looks like its time for me to look for some other kernelsThanks for the suggestion anyway!!
Click to expand...
Click to collapse
I dont know what has happened...
i never faced such problems....
now its better to flash stock and than any other rom.....
Sent from my GT-S5360 using xda app-developers app
problem solved (i think)
MaestroCharan said:
Did as u said : remove superuser apk and reinstall from market.
But still the same..
Finally, to me it looks like a problem associated with the kernel.
Yo bro..looks like its time for me to look for some other kernelsThanks for the suggestion anyway!!
Click to expand...
Click to collapse
i just had the very same problem like yours. then i installed superSU chainfire from app store, and it work fine.
hope it help you too
Can you help me?
MaestroCharan said:
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
Click to expand...
Click to collapse
Hi! i also have the same problem with you
it occur after i install merruk kernel 2.5
you said that you've just rooted again after following the steps that denysw0w said, does it mean that i have to flash JBV3 and ota 1,2,3,4 again, ill be back to 0 in upgrading my phone? help me pls...
Louie Jay said:
Hi! i also have the same problem with you
it occur after i install merruk kernel 2.5
you said that you've just rooted again after following the steps that denysw0w said, does it mean that i have to flash JBV3 and ota 1,2,3,4 again, ill be back to 0 in upgrading my phone? help me pls...
Click to expand...
Click to collapse
No come back to 0 broo...
Im use this methode everything work fine and good for me...
1. Flash stock rom (if you in custom rom)
2.install merruk kernel (for this case Im install the stable version 2.0 original dev.)
3. After finish, Im install superuser from chainfire in the market.
4. And Install custom rom and you can update the OTA
I hope this help you..
Sent from my GT-S5360 using Tapatalk 2
I have the problem with mising su binary after uninstall SuperSU, but fix it easily with this - http://forum.xda-developers.com/showthread.php?t=1538053&nocache=1
MaestroCharan said:
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
Click to expand...
Click to collapse
Try flashing other kernel! No offense to the maker of meruk but that kernel is way outdated! Try Percy or Savie!
IGI83 said:
I have the problem with mising su binary after uninstall SuperSU, but fix it easily with this - http://forum.xda-developers.com/showthread.php?t=1538053&nocache=1
Click to expand...
Click to collapse
And by the above link, I think he means, download Super SU from the Play store...install. Once you open that app, it will tell you that you need to update your binary. Click "Normal" and it should work.
I had a major root issue here but I didn't want to wipe my work phone and deal with 5 hours of setup haha. This is what finally worked for me.
(PS, the reason I needed root was for Good For Enterprise - Exposed Module) http://forum.xda-developers.com/showthread.php?t=2040163&page=76
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
shimp208 said:
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
Click to expand...
Click to collapse
how to boot a custom recovery? any link?
minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine did the same. Then I chose the other option not normal and it installed it automatically through recovery. Before that it might be needed to download twrp recovery from here
http://www.teamw.in/project/twrp2/128. Use Android App Install Method.
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
awyeahh1 said:
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
Click to expand...
Click to collapse
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
shimp208 said:
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
Click to expand...
Click to collapse
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
awyeahh1 said:
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
Click to expand...
Click to collapse
People have reported that CF-Auto Root works fine with Android 4.3 on the Nexus 10. You can also always update the SuperSU app and binary after successfully rooting with CF-Auto Root.
Thx my prob was solved by appying latest recovery and latest supersu 1.65
Beamed from my Htc kickass Sensation using tapatalk 4.
Same problem here
On starting SuperSU, here’s what I get:
>The SU binary needs to be updated. Continue?
[selected: Continue]
>If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary? (Normal / TWRP/CWN)
[selected: Normal]
>Installing, please wait
>Installation failed!
As far as I can tell, I can’t install TRWP/CWN because the SuperSU binary is not updated, and I can’t update the the SuperSU binary unless TRWP/CWN is installed. This looks like a vicious circle, can anyone recommend a way out of it please?
Further background:
Device: Evolveo Xtraphone 4.5 Q4, rooted by SRSroot which recognised it as an HTC device.
Also attempted: updating from SD card with UPDATE-SuperSU-v1.86.zip, by running Superuser.apk from the zip folder. This takes me back to square one: “The SU binary needs to be updated. Continue?” etc.
Any recommendations enormously appreciated, thanks!
..
..
I've never done a backup myself but that's bad practice I know.
If SuperSu does not ask you for root privileges, then there might be some issues with your root. Have you tried to install the latest update? I had the same issue right after root, the default SuperSu app did not work so what I did was flashing the latest SuperSu app via Recovery and it worked.
Get it here: http://forum.xda-developers.com/showthread.php?t=1538053
I just flash 4.4.2 INU, just backup yr msg & call logs, the installation process automatically backup & restore apps
Sent from my GT-I9500 using xda app-developers app
Always make a backup before doing anything to your system. You never know what might go wrong. You can backup using nandroid or your custom recovery.
Regarding you SuperSU issue, make sure you answer "No" when your custom recovery asks you fix root (unless specified by the rooting procedure - philz touch recovery when rooting Russian firmware i9500 4.4.2).
Moreover, you can download an app to check if you lost your root privileges. If you did lose it, root your system again.
..
Ap0rd said:
I already backed up my stock rom as an image, I'm talking about backing up apps, settings, etc to restore them. About superuser, I tried several times to re root but i won't work.
Click to expand...
Click to collapse
you can use titanium backup but that needs root. uninstall Super SU and install it from the play store. The app will detect if its activity is hindered by KNOX.
..
Ap0rd said:
By uninstalling , you mean unrooting?
Click to expand...
Click to collapse
First, make sure that your are, indeed, rooted. Uninstall Super SU in Applications Manager in your Settings. Install again from play store.
..
download a root checker app to check if you are rooted. try downloading Super SU from play store anyway. See what happens.
cheers ~
..
Ap0rd said:
How am i supposed to check for root if supersu isn't giving root access
Click to expand...
Click to collapse
ohhh right. reinstall your recovery and reroot your phone. When I was on 4.3, I used CWM 6.0.4.5.
..
Ap0rd said:
Why do I have to reinstall the recovery? And more importantly, I tried to re root before but it didn't work?
Click to expand...
Click to collapse
I read you first post again and you stated that you can grant root privileges to apps (always grant). Install Titanium Backup and backup your apps and flash 4.4.2. What's the problem here?
..
Ap0rd said:
Thanks for the help. Did you flash 4.4.2? And if you did, did you encounter any problems with it?
Click to expand...
Click to collapse
Yes. Flashed it with ODIN. No problems whatsoever. ALTHOUGH... some users are complaining about sd card permissions.
..
Ap0rd said:
Flashed 4.4.2 and rooted with philz recovery... No problems...
Thanks for the help everyone, especially @deandoi
Click to expand...
Click to collapse
Gladly.
cheers ~
Updated CF-autoroot with latest Supersu binaries and combined TWRP recovery for SM-T800/SM-T805/T700/T705 Exynos only, Lollipop and Kitkat
I've noticed that quite a number of people seeking to root their device also flash TWRP afterwards, seeing as it's unnecessary to do both steps I have made an all in one package to root and install TWRP recovery.
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version (ADB root shell and Download mode fixes).
UPDATE - I have updated all versions with new builds. TWRP is now v2.8.6.2 and now includes the fixes recently pushed to their repo for encrypted backups. I have also addressed the slow wipe issue, cache, system, etc., which some have experienced and should now be much quicker.
Each device now has it's own build, this is to ensure that TWRP recovery build properties reflect the device it's installed on. ROMs such as CM12 should now install without issue.
Feedback is welcome.
Simply flash with ODIN. Odin 10.6
cf-autoroot-twrp-t700
cf-autoroot-twrp-t705
cf-autoroot-twrp-t800
cf-autoroot-twrp-t805
Check root status with ROOT VALIDATOR
Guide how to flash, credit to Usama m.
http://techbeasts.com/2015/05/01/root-twrp-recovery-galaxy-tab-s-84-running-lollipop-502/
UPDATED TWRP:
http://forum.xda-developers.com/showthread.php?t=3074633
NOTE: It is important to boot to recovery after flashing or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Credits to chainfire for his great work.
FEEDBACK PLEASE
AND DONT FORGET THAT THANKS BUTTON :good: HIT AND RUN IS NOT NICE
.
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
d3xtr0 said:
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
Click to expand...
Click to collapse
Good stuff. :good:
Just picked up a T800 as a birthday present to my mom.. Its going to be hard to give this thing to her..lol
Anyways.. just used this to root and it worked perfect.. Had already took ota to LP..
Thanks !!
delete post !
tids2k said:
delete post !
Click to expand...
Click to collapse
What?
ashyx said:
What?
Click to expand...
Click to collapse
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
snapper.fishes said:
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
Click to expand...
Click to collapse
Why the forum doesn't allow users to delete their own posts is beyond me?
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
lloydb9382 said:
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
Click to expand...
Click to collapse
Correct.
thanx so much it worked great ,
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
almony8 said:
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately AT&T lock the bootloader, so atm you're stuck with a device that cannot be modified in any way.
Sent from my SM-T805 using XDA Free mobile app
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
cyaclone said:
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
Click to expand...
Click to collapse
Use Root Validator and post the output. Root checker doesn't give enough information.
ashyx said:
Use Root Validator and post the output. Root checker doesn't give enough information.
Click to expand...
Click to collapse
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
cyaclone said:
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
Click to expand...
Click to collapse
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
ashyx said:
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
Click to expand...
Click to collapse
BINGO!, it was Lux. I did an uninstall and rebooted and had ROOT.........WOW, strange that this would be the answer, but it worked for me at this moment.
Thanks
Not sure if it matters but what version of twrp is being installed?
AKfortyseven said:
Not sure if it matters but what version of twrp is being installed?
Click to expand...
Click to collapse
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version.
Click to expand...
Click to collapse
= 2.8.6.1