Related
I had Emanon's ROM on it for a while, but it just came crashing down so I flashed CM7.2... boots a lot faster, seems a bit more stable.
But I used to have full access, and now I don't. How do I get it back? I just want to switch out the bootanimation.zip.
Came across this:
status_six said:
Hi there, you need to have s-off (aka security off or full root) to write to /system and /data with the device booted, i.e. using root explorer etc.
You can also do it with s-on, but you have to to that with your PC via cmd prompt and adb shell which is less convenient.
Great guide to getting s-off here, took me <10 mins!
http://forum.xda-developers.com/showthread.php?t=794314
Click to expand...
Click to collapse
I've just finished mucking around with a HTC, so I'm a bit confused, but I gather there's no fastboot mode on the Mini, so I can't see how I can access the phone's flash from the PC without using the ADB shell...
And I'm not sure s-on/off is even relevant to the Mini... halp!
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Kimmoth said:
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Click to expand...
Click to collapse
Go to the su app and grant the permission for ES
you are coming from HTC so I am clearing some points some of them are of-topic
no fastboot instead download mode
bootloaders are not locked so no s-on no s-off in Samsung devices
use Odin multidownloader to flash firmware through PC
never use rom manager on this mobile, else a brick will be waiting for you
galaxy mini is easily root able
just flash an update.zip in recovery and you will be rooted
after root to change something in system
type mount -o remount,rw /system then do whatever you want to
stock rom cannot be backed up with the help of cwm
I've done a fair amount of research and am still having trouble getting this installed on an emulated device. I have tried the base adt-sdk images for 4.1.2, 4.3 and 4.4.2 none of which I was able to attain the same "rooted" functionality as a phyical device. Most of the threads I read were a lot like this: http://forum.xda-developers.com/showthread.php?t=1731095
Xposed always gives me the following error: "Failed to get root access. Make sure your device is root properly and you have not blocked shell commands."
When I
Code:
adb shell
into the device I have [email protected], so I have access to root. The su binary is in both /system/bin and /system/xbin. I have also tried remounting the /system partition as rw, but nothing seems to help.
I'm not sold on any particualr version of android as long as it is >=4.1.2. I know some SELinux stuff came in at 4.3.
Any help you could offer would be great,
Thanks!
It worked flawlessly for me using Genymotion. I'm guessing you're using the normal Android emulator - apps won't get root on that directly and I'm not familiar with it.
You could, however, manually replace the necessary files. I'd recommend changing the installation mode to "Recovery" then checking the flashable ZIP's updater-script and basically replicate it from the shell (the updater-script is a shell script).
GermainZ said:
It worked flawlessly for me using Genymotion. I'm guessing you're using the normal Android emulator - apps won't get root on that directly and I'm not familiar with it.
You could, however, manually replace the necessary files. I'd recommend changing the installation mode to "Recovery" then checking the flashable ZIP's updater-script and basically replicate it from the shell (the updater-script is a shell script).
Click to expand...
Click to collapse
Where does it drop the script?
Blackdragon1400 said:
Where does it drop the script?
Click to expand...
Click to collapse
The script is inside the ZIP, which I think I saved to /sdcard/Android/data/de.robv.android.xposed.installer/ - check the output on your screen after pressing install, it should be noted there.
GermainZ said:
The script is inside the ZIP, which I think I saved to /sdcard/Android/data/de.robv.android.xposed.installer/ - check the output on your screen after pressing install, it should be noted there.
Click to expand...
Click to collapse
Alright, I will give it a try tomorrow, and post an update on the results. Thanks for the help!
Note that there are still a few minor things that are done via root, even when using the manual recovery installation mode. So the app needs to get root access.
Hey all
I'm having some trouble getting r/w access back on system on my 5803 on .726 firmware.
I have root and working recovery, just no r/w on system. Every time I check system access in terminal it sits at "ro" and not "rw"
I had full access in Kitkat, but when I flashed Lollipop I seemed to have lost r/w access. I have tried updating my recovery, RICDefeat, and byeselinux, all to no avail.
I feel like I'm busy missing something completely obvious, but I can't for the life of me figure out where I'm going wrong. Can any of you fine souls help?
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
chris5s said:
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
Click to expand...
Click to collapse
It seems that I can enable that way, but it doesn't persist after a reboot. And mounting system in recovery doesn't seem to do anything either. If I try run certain things in recovery it seems like they don't really work. I can change recoveries and ROM, but things like debloating scripts don't seem to work. It's quite strange.
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
chris5s said:
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
Click to expand...
Click to collapse
I suppose I could, but that's not gonna solve my problem with flashing things in recovery
Still struggling with this :/
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
pedro5148 said:
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
Click to expand...
Click to collapse
Thanks for the suggestion, but it doesn't work.
Hello guys, it's the first time that i post in XDA, i don't know if i am in the right place (sorry if no, and sorry for my bad english), but i have a tablet RK3066 (DL tablet 3003) (at least is what cup-id say) and i have recently flashed it to stock firmware, before, i had root acess in it, i don't remember how i did it at the first time, but i was with serious problems to do it.
Ok, now, after i flashed it, and try to root again, i tryed to use Kingoroot via pc, and it says "root success", but Supersu.apk don't update the binary and even if i tap cancel update, the app that need root permission don't is prompted and can't get permission.
Ok, you can say, so, you haven't root installed, try another way!
But, how can i do not have root installed if, even with this things, in adb i have all the permission?!
And the most curious, i know if you will use adb shell it will return a line with this $, and then you type "su" to it turn into #, but here no! When i use adb shell it comes already with a #, to be more especific, it comes like this "[email protected]:/ # ".
So, i don't know more what can i do cause i have root acess via adb, but Supersu.apk don't update binary and don't prompt to permissions.
I have a custom CWM for RK3066 generic from androidtab, but with some erros to mount some folders like sdcard, system...
If someone know how to fix this i will be thankful.
I was thinking about a way to change apk permissions via adb, someone can say to me how can i grant permissions to apk via adb commands?
Thanks, and sorry for my bad english, i am brazilian that never studied in a english school, and sorry if i am in the wrong place for this!
PS01: I already try to unroot but without success, any way, i can unnistall and install supersu any time but no work, can't update binary.
PS02: I have this issue too via cwm:
HTML:
E:Can't find misc
E:Can't mount /cache/recovery/command
E:Can't find misc
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
E:Can't mount /sdcard/
If can help you, i am posting the cache/recovery/last_log files pulled via adb. and a SS of the adb shell in #.
I already try to use TWRP but the touch is with some issues in this recovery mode!
PS03: I used KingoRoot to root it again, then, it installed KingoUser(to grant permissions, it is working), but i want to use Supersu, and Supersu cannot update binary.
If you're running Android > 4.2, you may try the solution in the attachement. If you're running Windows, and if your Android system is 32 bit, just (double) click on the *-32.bat file.
nmset said:
If you're running Android > 4.2, you may try the solution in the attachement. If you're running Windows, and if your Android system is 32 bit, just (double) click on the *-32.bat file.
Click to expand...
Click to collapse
Sorry, i forget to say this, is 4.4.2 updated by developers of the tablet.
this kind of archive is to update the binary or is another way to root?
Thanks for reply !
nmset said:
If you're running Android > 4.2, you may try the solution in the attachement. If you're running Windows, and if your Android system is 32 bit, just (double) click on the *-32.bat file.
Click to expand...
Click to collapse
YOU ARE THE MAN!!! hahahaha... thanks to it guy... now i will try to solve the ummounting error...thanks again.
how i close the thread?
Yakchimi said:
how i close the thread?
Click to expand...
Click to collapse
There should be a howto in the forum's manuals to close a thread
The kingroot stuff puzzled me to the point that I started to play with it. I quickly found out that it was difficult to remove. I could do it with a few scripts in the attachement. The key point is removing file attributes. I look forward to hear of success or failure with details.
nmset said:
The kingroot stuff puzzled me to the point that I started to play with it. I quickly found out that it was difficult to remove. I could do it with a few scripts in the attachement. The key point is removing file attributes. I look forward to hear of success or failure with details.
Click to expand...
Click to collapse
But isn't Kingroot is "KingoRoot", and the thread back cause i was using the user of kingoroot, but play store update it's and broken again, and i don't know how to use the files you gave me..
kingoroot !!! I was all way through far from your problem ! I can't really be of help to you in that case, just trash the files, sorry !
Ok
nmset said:
kingoroot !!! I was all way through far from your problem ! I can't really be of help to you in that case, just trash the files, sorry !
Click to expand...
Click to collapse
Hey, i did it, after root again with kingoroot via pc, installed supersu, open it, kingouser ask for permission to supersu, i gave it, and supersu updates binary, then i unnistalled kingouser..
thansk all you.
I'm attempting to mount the xbin folder to copy over a file into it (sqlite3) and am unable to. When I attempt to mount R/W in Root Explorer nothing happens. If I copy the file directly and attempt to mount from the prompt Root Explorer states that the copy failed. I've even attempted chmod and that also fails.
I did a clean install of Marshmallow, flashed TWRP 2.8.5.0, flashed ElementalX-N6-2.03 kernel, then SU Beta 2.49. Root Checker tells me that I have root access and busybox is installed properly.
As a test I tried all of the above on other folders such as bin and that failed as well. I've attempted copying sqlite3 in TWRP over to bin (couldn't find xbin in the file manager) and it said successful, but doesn't show when I boot back up. Does anyone have any idea what is causing this?
dudeman27 said:
I'm attempting to mount the xbin folder to copy over a file into it (sqlite3) and am unable to. When I attempt to mount R/W in Root Explorer nothing happens. If I copy the file directly and attempt to mount from the prompt Root Explorer states that the copy failed. I've even attempted chmod and that also fails.
I did a clean install of Marshmallow, flashed TWRP 2.8.5.0, flashed ElementalX-N6-2.03 kernel, then SU Beta 2.49. Root Checker tells me that I have root access and busybox is installed properly.
As a test I tried all of the above on other folders such as bin and that failed as well. I've attempted copying sqlite3 in TWRP over to bin (couldn't find xbin in the file manager) and it said successful, but doesn't show when I boot back up. Does anyone have any idea what is causing this?
Click to expand...
Click to collapse
ElementalX hasn't got the R/W protection removed. You'll have to use Hellscore (or maybe some others) until the protection is removed in Ex. It is next on the list for that Kernel I thin.
danarama said:
ElementalX hasn't got the R/W protection removed. You'll have to use Hellscore (or maybe some others) until the protection is removed in Ex. It is next on the list for that Kernel I thin.
Click to expand...
Click to collapse
Thanks! That resolved the mounting problem but for some reason copying over the file still fails. I even chmod 0777 on xbin and it won't copy. Hmm.
dudeman27 said:
Thanks! That resolved the mounting problem but for some reason copying over the file still fails. I even chmod 0777 on xbin and it won't copy. Hmm.
Click to expand...
Click to collapse
Convert or uninstall unnecessary Google apps in /system the free space on stock /system is only about 2mb, this was one of the reasons I initially couldn't install layers.
Sent from my Nexus 6 using Tapatalk
djkinetic said:
Convert or uninstall unnecessary Google apps in /system the free space on stock /system is only about 2mb, this was one of the reasons I initially couldn't install layers.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You sir are a saint! I read about that and thought 16 MB was enough, but I went up to 64 MB and everything works perfectly now. Thank you.
danarama said:
ElementalX hasn't got the R/W protection removed. You'll have to use Hellscore (or maybe some others) until the protection is removed in Ex. It is next on the list for that Kernel I thin.
Click to expand...
Click to collapse
Hey, I'm on Hellscore kernel and I cant mount system as R/W either. I am having exactly the same issues as OP. I cant edit the build.prop or change layers. I got one layers theme to work but I cant change it since I cant uninstall it from /system. Any idea?
BluntSmokeTrauma said:
Hey, I'm on Hellscore kernel and I cant mount system as R/W either. I am having exactly the same issues as OP. I cant edit the build.prop or change layers. I got one layers theme to work but I cant change it since I cant uninstall it from /system. Any idea?
Click to expand...
Click to collapse
Do you have root explorer? If so, does the mount r/w button work?
danarama said:
Do you have root explorer? If so, does the mount r/w button work?
Click to expand...
Click to collapse
Yes, I have root explorer. When I hit the button nothing happens. I downloaded the app called Mount /system and when I hit the button to mount it in there it tells me my device may not be rooted or compatible. In terminal emulator when I type su the $ changes to #, and in supersu everything has the proper root rights so I know my root is working.
I guess I should also mention that I am running the xTraSmooth 6.0 rom that came pre rooted with the hellscore kernel. I flashed it from stock M after flashing TWRP.
BluntSmokeTrauma said:
Yes, I have root explorer. When I hit the button nothing happens. I downloaded the app called Mount /system and when I hit the button to mount it in there it tells me my device may not be rooted or compatible. In terminal emulator when I type su the $ changes to #, and in supersu everything has the proper root rights so I know my root is working.
I guess I should also mention that I am running the xTraSmooth 6.0 rom that came pre rooted with the hellscore kernel. I flashed it from stock M after flashing TWRP.
Click to expand...
Click to collapse
I got weird behavior like that as well. Try converting apps to free up space. I had 64 MB free om the system partition when mine started working.
dudeman27 said:
I got weird behavior like that as well. Try converting apps to free up space. I had 64 MB free om the system partition when mine started working.
Click to expand...
Click to collapse
I've been looking through the thread for the rom and some other people had the same issue. They reflashed the rom and it seemed to fix it for some reason. So I'm going to try that in a bit and see how it goes.
BluntSmokeTrauma said:
Yes, I have root explorer. When I hit the button nothing happens. I downloaded the app called Mount /system and when I hit the button to mount it in there it tells me my device may not be rooted or compatible. In terminal emulator when I type su the $ changes to #, and in supersu everything has the proper root rights so I know my root is working.
I guess I should also mention that I am running the xTraSmooth 6.0 rom that came pre rooted with the hellscore kernel. I flashed it from stock M after flashing TWRP.
Click to expand...
Click to collapse
Well not sure about.that xtrasmooth. Seems.like it has plenty of.issues.. Try and download hc again or try another rom.
danarama said:
Well not sure about.that xtrasmooth. Seems.like it has plenty of.issues.. Try and download hc again or try another rom.
Click to expand...
Click to collapse
No other issues than that really. I'm gonna reflash
BluntSmokeTrauma said:
No other issues than that really. I'm gonna reflash
Click to expand...
Click to collapse
Actually, I think someone said they did that in that rom thread to fix this.
danarama said:
Actually, I think someone said they did that in that rom thread to fix this.
Click to expand...
Click to collapse
Yep. I read thru it and saw that, just got done and it fixed the issue. Sweet.