Related
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk
Ways to root your Samsung Galaxy Tab 4 7.0All of the guys on the list is tested by me and it's working
For those guys who can't root their tablet, this thread is the right place for you
1. This is the Easiest Way to Root your tablet
KingRoot App Download it here
http://www.appsandroidapk.com/apk/kingroot-v4-6-2-apk-file-for-android/
Download the app
Before installing it Go to Settings > General Tab > Security > and Enable "Unknown Sources"
Install the app and Root your phone.
You might wanting to have a SuperSU instead of kingroot's SU
Google it SuperSU Me Download the latest version or you can find it here in this link
http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Update the SUBinary
Reboot
2. KingoRoot App apk version
Download Link
https://root-apk.kingoapp.com/
Download the app
Before installing it Go to Settings > General Tab > Security > and Enable "Unknown Sources"
Set your device atleast 10 minutes before sleep due to inactivity
Install and Root your Device
Do nothing while rooting "Like tapping or bringing down the notification bar" this is why i make you set the 10minute-sleep
1st/2nd attempt might fail but on the other hand it will succeed
You might wanting to have a SuperSU instead of kingoroot's SU
Google it SuperSU Me Download the latest version or you can find the link here
http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Update the SUBinary
Reboot
3. Root Using TWRP (old)
Requirements
TWRP link is here
http://forum.xda-developers.com/attachment.php?attachmentid=3128455&d=1421957427
Important: Odin3 v1.85 Direct download Link
http://forum.xda-developers.com/attachment.php?attachmentid=581913
PC
On your pc Open Odin3 v1.85
Click PDA and choose the tar file that you've downloaded
Tick Auto Reboot and F. Reset time
Now go to your device, Boot into download mode ( Power it off wait until it vibrates then press Home,Power and Volume Down Simultaneously)
Plug your device into your Computer (Install drivers here's the link http://www.mediafire.com/download/o3exocwabcxax3b/SAMSUNG_USB_Driver.exe)/ Some Pc install drivers automatically just wait them to install or if you already install the drivers skip driver installation procedure)
Click Start if the Odin detects your phone, your phone will automatically reboot
Now Boot your phone into Recovery Mode by (Turning it off and Press Power + Home + Volume up)
It will boot into TWRP
Press Reboot > System and it will ask you if you want to get root and swipe it to install
Update SuperSU and make another reboot
You can also update your TWRP using this zip file
https://www.androidfilehost.com/?fid=24052804347818249
Now if you really can't root your tablet and you're desperate, try another version of your stock firmware, you can find your stock firmware on Google, after that do this procedure again
Done.
Other Links to make your tab Rooted
http://forum.xda-developers.com/showthread.php?t=3111934
http://forum.xda-developers.com/tab-4/help/twrp-install-twrp-root-samsung-galaxy-t3095736
Developers that has credit on all of this
@BRoy_98
@pinksworld
@gatesjunior
and sorry if i haven't mentioned the others, i dont know who to give credits
SORRY SOME OF MY ENGLISH IS REALLY BAD
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Just imagine that I just put all those threads together ahaha: )
thisisapoorusernamechoice said:
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Click to expand...
Click to collapse
I dunno if that issue is real, but no worries we have supersu me
thisisapoorusernamechoice said:
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Click to expand...
Click to collapse
I dont think that if you install first supersu me and then kingroot your tab, after root turn wifi off and use supersu me, no data sent to anyone........ anyways it doesnt send your passowords etc to china, just like browser data and few app datas.... but theres no way to get passwords.... all are crypted or hidden well in smali
thelous said:
I dont think that if you install first supersu me and then kingroot your tab, after root turn wifi off and use supersu me, no data sent to anyone........ anyways it doesnt send your passowords etc to china, just like browser data and few app datas.... but theres no way to get passwords.... all are crypted or hidden well in smali
Click to expand...
Click to collapse
I wouldn't be sure about that. If you type in your password, once rooted, anything can easily capture the keyboard input and log it or send it out. Let me elaborate. It's like the guys who say, "Hey I have a firewall installed so it cannot communicate out." Yeah, o.k., so all the firewalls do is manage IPTABLES, so if I am an application and have root access, I can do what I want to avoid your firewall rules quite easily. Just a thought.
Hmm, updating the binary will remove the @#$%&* thing , we're just going to use the app to root our phone, and I guess wiping cache and dalvik is necessary
BTW tab 4 is best for gaming because of it looks and size but due to a stupid Samsung company, 1.2ghz + vivante gc1000 expect lagging, I hope some kind hearted will make a custom kernel for overclocking this tab.
BTW There's no Tex plugin on gltools, installing default will not work, so you have to find a cracked version of gltools, well if you do that... R.I.P expect force closes
gatesjunior said:
I wouldn't be sure about that. If you type in your password, once rooted, anything can easily capture the keyboard input and log it or send it out. Let me elaborate. It's like the guys who say, "Hey I have a firewall installed so it cannot communicate out." Yeah, o.k., so all the firewalls do is manage IPTABLES, so if I am an application and have root access, I can do what I want to avoid your firewall rules quite easily. Just a thought.
Click to expand...
Click to collapse
Well i didnt say anything about firewalls i was daying if you manually disable wifi and use king root, it wont be able to connect anywhere to send any data.... also you can search by date and time files made during root session and remove everything to prevent any keyloger to work
Have ODIN and a stock image ready!!!
Be careful with this root process! The sm-t237p 5.1.1 OH7 boot loops and won't hold the root or Philz recovery... Yet!:cyclops:
thelous said:
Well i didnt say anything about firewalls i was daying if you manually disable wifi and use king root, it wont be able to connect anywhere to send any data.... also you can search by date and time files made during root session and remove everything to prevent any keyloger to work
Click to expand...
Click to collapse
No. I can easily change the file and date stamp to match any given system file you already have so that it is not easy to find. Also, Kingroot will not run correctly and root your device properly if it cannot contact it's servers to download the proper exploit for your device. Now, if you are talking about disabling wifi only so that Kingroot cannot contact it's servers after you are rooted, well, if you use any data what so ever, it can use that same data connection. As an example, I have to have data of some type to login to my bank site, etc..
SM-T237P Specific maybe others with PhilZ recovery...
Root Success! Check this out... http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
gatesjunior said:
No. I can easily change the file and date stamp to match any given system file you already have so that it is not easy to find. Also, Kingroot will not run correctly and root your device properly if it cannot contact it's servers to download the proper exploit for your device. Now, if you are talking about disabling wifi only so that Kingroot cannot contact it's servers after you are rooted, well, if you use any data what so ever, it can use that same data connection. As an example, I have to have data of some type to login to my bank site, etc..
Click to expand...
Click to collapse
Well, atleast my bank account cant be logged with different ip and if its tried i recice message wheres code that you need write to bank website to access account.... however i havent lodt any accounts yet after rooting with kingroot, it has so manynusers that they cant check all information they recive, just like facebook and whatsapp... (they're spying watnu do but they have too many users so it would take like unlimited time to check all accounts and keybindings thru.....
K94U said:
Root Success! Check this out... http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
Click to expand...
Click to collapse
You can use any kind of cwm to flash a zip file that can root your device, This was an alternative way, just find a cwm to flash hehe
Siegharf said:
You can use any kind of cwm to flash a zip file that can root your device, This was an alternative way, just find a cwm to flash hehe
Click to expand...
Click to collapse
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
K94U said:
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
Click to expand...
Click to collapse
There's kies or custom ota flashing
K94U said:
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
Click to expand...
Click to collapse
235 LTE 5.1.1 rooted as well
http://forum.xda-developers.com/showpost.php?p=64255121&postcount=1
(not spamming in case anyone got the idea)
So I decided it's time to upgrade seeing as my phone prompted me to do so. My phone is rooted and I wanted to keep it that way. I downloaded the latest version D6603_23.5.A.0.570_R2D (Swiss edition) using experifirm and then created the ftf using flashtool. (Latest version for all apps). I then used prf creator to create a flashable zip installable file (see attached picture)
With PRF creator I added the ftf file, SuperSU-v2.65-20151226141550, Z3-lockeddualrecovery2.8.26 and also in the Extra Files section; RICDefeat.zip and byeselinux_flashable.zip
The zip file I then copied to my sd card, rebooted into recovery and installed. Once the upgrade was complete, I discovered to my horror, that root is gone.
My question is, where did I go wrong? What did I leave out etc.
Final question, how to get my phone rooted again?
As far as I understand using the superSU zip without it being modded to be a system install means it will install as systemless (tried to get around MM root verification) with Sony this actually causes a problem whereas the system root (normal SU) works just fine for us with the extras you added.
You did everything right. But superSU needs to be different and duel recovery does not work with MM.
One way is to leave the recovery part blank and just add RecRootv3 under the SU part. This will install SU as system and all the other parts like byeselinux and RICDefeat.
Also you cannot use NUT duel recovery with MM yet it does not work. RecRoot includes TWRP which you boot into by pressing volume down like duel recovery.
Hope this helps. There is not a guide that I can see so it is all a bit confusing for now so I don't blame you for using the lollipop method!
Missed the bit about rerooting! You're gonna have to do the whole downgrade to KitKat, root, update to MM procedure again (unless I missed a new way to do it)... tbh a clean install won't do any harm so back everything up and go ahead. Guides are around if you need them
I hired someone not super familiar with flashing a custom rom, but who knew more than me. We got MM installed but I am having some problems. First, the only reason, I updated the rom was to get mirroring. However: 1. there is no mirroring, but there is cast. I have a Tab 4 and mirroring works perfectly with it and KitKat. I tried about 5 mirroring apps from the Play Store and they all require that the Smart TVs I have (Samsung and LG) be connected to the Internet because using the TV's internet connection is a major nuisance for me. That is not required with my KK Mirroring, and I am wondering whether I should get rid of MM and flash KK. Or, is there an app that will work without mirroring. 2. My SD card is now invisible. When I link my Tab to my windows 7 computer, my SD card doesn't show. (Additionally, come to think of it, none of my files show. All I get is an image of 5100, but when I click on it nothing shows on my windows 7 computer.) 3. Probably related to No. 2 -- Some apps seem to install, but I have no way to access them because no shortcut is placed on the screen and I have no tree of files. (Titanium Backup for instance, can't be accessed. However, when I downloaded ai-keyboard, it mostly worked)
Hate to ask so many questions, but this is what I now have. Would call the person who did the flash, but his wife is due any day, and for all I know, gave birth yesterday.
which M Rom did you installed? kindly mention Rom and recovery build number as well.
are you using any other home launcher than the default? how did you installed titanium backup? normal or copy pasted apk to the system partition?
have you checked the luncher setting? for instance I can hide some apps from the nova launcher but can find it with it's search bar.
check with the default launcher or any other.
did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?
I haven't tested screen mirroring with this device. although I checked briefly with a Samsung S, S4 and a G3 on a LG smart tv with webOS 3 using LG TV plus app, I had to be on a same network with wifi hotspot enabled from my device (didn't required a working internet) and selecting LG tv plus option from the TV.
I still haven't been used to with screen mirroring and cast. so others can help.
Hi Billys,
Thanks a lot for your response. My Internet has been down for about 2.5 days and that is the reason I am late responding to you. The CM version was 13.0.20160222-2140-UNOFFICIAL -P5110. The CM Recovery Version was GT-P5113 CM Recovery 6.0.1.0.tar.
The Launcher is the default that comes with MM. I installed Titanium Backup through the Google Play Store. I have been fooling around with the device and Root checker basic says that root access is not properly installed, which might explain why Titanium Backup is not working. Also, SuperSu won't open.
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
decijp said:
Hi Billys,
Thanks a lot for your response. My Internet has been down for about 2.5 days and that is the reason I am late responding to you. The CM version was 13.0.20160222-2140-UNOFFICIAL -P5110. The CM Recovery Version was GT-P5113 CM Recovery 6.0.1.0.tar.
The Launcher is the default that comes with MM. I installed Titanium Backup through the Google Play Store. I have been fooling around with the device and Root checker basic says that root access is not properly installed, which might explain why Titanium Backup is not working. Also, SuperSu won't open.
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
Click to expand...
Click to collapse
Device specific builds are too outdated. Kindly flash these depending on your model
Espresso3g - P3100 & P5100
EspressoWifi - P3113, P5113, P3110, P5110
For more info, visit this thread http://forum.xda-developers.com/gal...fied/rom-cyanogenmod-13-cm13-0-t3303798/page1
And flash it with the latest TWRP recovery found on andi34.github.io under recoveries
Sent from my espresso3g using XDA Labs
Root is enabled through developer options. Go settings, about tablet. Tab build number 7 times. Back out and open dev options. Scroll down a bit and enable roo & adb. You should be good to roll then
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Champ1919,
I did what you suggested and was able to download TWRP from Andi's. I unzipped the file with the ES File Explorer. Nothing happened. Could you tell me what I should do next. Thanks again.
decijp said:
Champ1919,
I did what you suggested and was able to download TWRP from Andi's. I unzipped the file with the ES File Explorer. Nothing happened. Could you tell me what I should do next. Thanks again.
Click to expand...
Click to collapse
if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery.
decijp said:
Hi Billys,
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
Click to expand...
Click to collapse
when you connect the tab to PC, there is a logo of CM in the status bar, drag the notification menu, and tap the CM menu, there, check If MTP is enabled or it's set on charging only mode. you can also set this in setting-developer. make sure the keypad is not locked as well
billysam said:
when you connect the tab to PC, there is a logo of CM in the status bar, drag the notification menu, and tap the CM menu, there, check If MTP is enabled or it's set on charging only mode. you can also set this in setting-developer. make sure the keypad is not locked as well
Click to expand...
Click to collapse
Billys,
There was no CM logo, but went to settings and USB and you were right. Now I can view the files of my tablet on my PC. Thanks a lot.
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
decijp said:
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
Click to expand...
Click to collapse
It won't automatically get the zip file because you select the zip you flash. Just navigate to whet you put the zip and flash that
Sent from my espresso3g using XDA Labs
decijp said:
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
Click to expand...
Click to collapse
install the latest twrp by using cwm. after install reboot back into recovery. you shuold see the graphical differences between twrp and cwm.
To make a long story short, it appears that my Superuser is misbehaving. Used root checker to analyze and it found that Superuser was installed and that SU Binary files were installed. However, it found a Root User Account Error. (Error: stderr: null, stdout: null, exit..value: 1) It suggested that I reinstall Superuser app from TWRP. .
After much experimentation, I can get into TWRP when I reboot in the recovery mode. (not when I hit the icon on home page -- tells me I need root access) When I hit install, I see CWM 13, An android 4.4 (omni-4-4-4-20160305-1323 expresso-HOMEMADE.zip) and a gapp 6 --- a long time ago when I downloaded 4.4, I didn't know how to get to the corresponding gapp, so I didn't do so. Also, SuperUser doesn't show up at this place, so I don't know how to reinstall it.
Can anyone tell me how to reinstall Superuser and get full SuperUser access?
Also, I am thinking of going back to Android 4.4 to get mirroring. Can someone point me to the gapp file for that. Additionally, when I possibly would be installing 4.4, would I first install 4.4 and then reboot and install gapps. Or should 4.4 and gapps be installed at the same time?
Thanks for everyone's help. Sorry to ask so many questions. However, have gone to youtube and web many times and still am confused about what is going on.
decijp said:
To make a long story short, it appears that my Superuser is misbehaving. Used root checker to analyze and it found that Superuser was installed and that SU Binary files were installed. However, it found a Root User Account Error. (Error: stderr: null, stdout: null, exit..value: 1) It suggested that I reinstall Superuser app from TWRP. .
After much experimentation, I can get into TWRP when I reboot in the recovery mode. (not when I hit the icon on home page -- tells me I need root access) When I hit install, I see CWM 13, An android 4.4 (omni-4-4-4-20160305-1323 expresso-HOMEMADE.zip) and a gapp 6 --- a long time ago when I downloaded 4.4, I didn't know how to get to the corresponding gapp, so I didn't do so. Also, SuperUser doesn't show up at this place, so I don't know how to reinstall it.
Can anyone tell me how to reinstall Superuser and get full SuperUser access?
Also, I am thinking of going back to Android 4.4 to get mirroring. Can someone point me to the gapp file for that. Additionally, when I possibly would be installing 4.4, would I first install 4.4 and then reboot and install gapps. Or should 4.4 and gapps be installed at the same time?
Thanks for everyone's help. Sorry to ask so many questions. However, have gone to youtube and web many times and still am confused about what is going on.
Click to expand...
Click to collapse
If you installed CM13, is actually pre rooted. Just enable it from the developer settings
Sent from my espresso3g using XDA Labs
Finally figured out that I could transfer SuperSu zip file to my Tab and then install it from TWRP. Did so and also wiped clean the cache and now SuperSu is functional and I can get rid of the bloatware and speed up the Tab. Thanks for everyone's help.
Hi.
This is my first post, I hope i'm in the correct forum.
I have a friend whom I requested to Root, Flash TWRP and Install LineagOS and GAAP on my OnePlus One phone.
He successfully flashed TWRP and installed LineagOS & GAAP but could not root my OnePlus One using SuperSu. He mentioned permission issue trying to root.
He went back to his country, so I am stuck trying to root my phone.
I would like to root my LineagOS (formally OnePlus One) using SuperSU.
I have downloaded/copied the latest SuperSu zip file into the Phone Sd/Download folder.
I went into custom recovery (TWRP).
Click on the Install button and verified I can see my SuperSu zip file.
Since this is my first time performing a phone root, I did not click SuperSu zip to install, until some experts can assist. me.
Just a few (Q's).
Questions:
a) Should I run any preliminary steps prior to clicking install SuperSu.zip?
b) Since I have LineagOS, GAAP apps already installed, will they be wiped after rooting SuperSu. If (Yes), any software available to backup/restore LineagOS & GAAP prior to the root process?
c) My friend mention “Permission problems with OPO”. Are there some options to open OPO and allow rooting SuperSu?
BTW: I do have the adb & fastboot installed if I need to enter some commands to get this done.
Thanks.
Tom.
a) No.
Download flashable supersu zip and flash it from here and flash it via TWRP https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
b) No.
But you can take nandroid backup through twrp in case something goes wrong.
c) As far as I know there is no problem with "permission" for rooting.
Happy flashing
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
tomx2x said:
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
Click to expand...
Click to collapse
I think I'm missing something. Did you tried any other method to root? I recommend a clean flash.
1. Download Sultanxda's unofficial lineageOS from here
2. Download Gapps from here. ( ARM-7.1-nano)
3.Download SuperSU from here
4. [Optional] take back up of your apps (No need to back up medias like photo,video,etc)
5.Got Recovery>wipe>advanced wipe
select system,data,cache and dalvik cache (DO NOT SELECT INTERNAL)
6.flash the zips you already downloaded in this order - ROM- Gapps - SuperSU
do not wipe anything after this step
7.Reboot
1st reboot will take some time (10-20 min ). Do not interrupt this process.
PS: I totally recommend Sultan's LineageOS over official LOS. You can actually feel the difference in smoothness and performance. Especially the Camera.
Feel free to check device specific forum for OnePlus One
Happy flashing!
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
tomx2x said:
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
Click to expand...
Click to collapse
Yes. Copy all 3 zip (rom,gapps,supersu) to you phone.
Let me know how it goes..
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
tomx2x said:
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
Click to expand...
Click to collapse
Can you send me a screenshot of supersu app?
I'm using the exact settings and I don't have any problem at all.
Do not let TWRP install supersu.
@psxda97
As you know the Supersu is a zip file. When I open/ then extract, the display will show folders & their contents.
I have attached all the folders & contents from supersu extract for your review.
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Here is the website link where I downloaded SuperSu 2 days ago.
" https://download.chainfire.eu/1114/...r&utm_medium=referral&utm_source=DonanimHaber “
tomx2x said:
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Click to expand...
Click to collapse
I meant this
Edit : So you've no supersu app on you phone?
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
tomx2x said:
[MENTION=7046372]
Should supersu app be on my phone after installation/rebooting?
Tom.
Click to expand...
Click to collapse
Yes.
Go to recover and flash it one more time
Then go to Advanced on twrp and select copy log (without kernel log).
Log will be on root folder of internal. attach the log in your next post
Also send me the screenshot of your about phone settings.
You're still missing something.
tomx2x said:
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
Click to expand...
Click to collapse
Go to system settings>developer options>root access and set it to "apps and adb"
If you flash the SuperSU.zip in TWRP on your device then you should have root.
I think you misunderstood from the beginning, did you download the SuperSU.zip and then extract it on PC and then try to install it? If so, that was completely the wrong thing to do. You might have to remove what you've done so far and then try again from a clean start, you might gave to flash your stock firmware to get a clean start.
Have you looked into whether you need normal SuperSU or whether you need systemless SuperSU?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Additional info provided - Anyone with advice.
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
The problem might be in the LineageOS ROM that you're using, I've seen others have this issue on other devices using LineageOS.
I don't recall what some of the solutions were.
@Sam Nakamura is pretty knowledgeable about the OnePlus devices, maybe he has some useful input.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
I haven't used LineageOS yet so I'm not familiar with its details, I was pretty sure you'd know though. [emoji106]
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Sam Nakamura.
Thanks for the info.
I have previously executed the steps in the order you posted. I was just asking if other sequences to flash these apps were plausible.
With the help of member psxda97, he documented similar steps 1-7 for me. (Please read Post #4 on this thread and my results in Post #7). It's basically a snapshot of what you posted regarding the order seq.
Unfortunately, my phone still did not root after applying the ROM, GAAP & Supersu in this order. I'm not sure why the root is declared successful in TWRP, and the phone remain un-rooted.
Do you suggest I rerun steps1-7 from Post#4 and include your echo statement before installing supersu?
The LineageOS extras, (you mentioned) has a built-in root.
I now have LineagOS from Sultanxda's installed on my phone. It is highly recommended by XDA members over the official LOS, for it's smoothness and camera enhancements. Sultanxda' release is 06/25/2017.
LOS extras has a release date of 06/21/2017. My only issues, whether to choose LOS extras. I will subsequently get the next “Official” LOS release for 6/25 and loose LOS Sultanxda installation.
Tom.
Tried Installing LOS extras 14.1
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
tomx2x said:
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
Click to expand...
Click to collapse
Did you choose the correct arm(32) version of lineageOS su? I'd try the following:
Backup all partitions with twrp so you can return to your set-up later on..
Wipe everything except internal storage
Flash rom, (custom kernel), gapps and su
Boot up and check if it's working now
If not restore your backup and check next point
Alternatively:
Have you tried superSU with forced systemless via twrp terminal (by the way, if done correctly there shouldn't fallow a output with this command line..)
Flash supersu from here:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I never had issues with the beta but you can also use the stable version, downloads on post 1
Using Magisk as root and root management tool
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashable zip via twrp, if successful go to magisk settings, and check superuser and read the rest of Magisk's potential on the linked thread, my preferred method as it allows you to hide root from certain apps which deny service to rooted devices..
Important, it's not a good idea to flash lineageOS su, then supersu, then magisk after each fails, at least restore your clean boot partition from twrp or flash the boot.img from within your rom zip... Best would be clean of course - but as you have a backup of your previous system you can play around and make errors...
Sent from my OnePlus 2 using XDA Labs