Develop Bugs

[Q] Odd Root Access Results

I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?

dferrey said:
I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
Click to expand...
Click to collapse
I have seen this happen before that you can retain some permissions with certain apps but not really remain rooted its a 50/50 shot its odd but not totally uncommon results. Generally it has something to do with apps that had su permissions prior to the update adding new su permissions don't usually occur after

I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.

Sometimes it won't push the files if they already exsist

I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.

dferrey said:
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
Click to expand...
Click to collapse
No its always worked like a charm for me maybe go to the market and install su from there to see if that doesn't change its strange though that prime is still detecting it. This method only works on rooted stock from what I have seen. Each time delete backup when you restore root. You can also give a shot at fixing permissions. I believe that ota rootkeeper ask for permissions to maybe at some point it was denied and it stuck.uninstall ota and reinstall hope you get er fixed

dferrey said:
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Click to expand...
Click to collapse
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
Note: I have never been a superuser on this kindle before, this is my first attempt at rooting - but the 2nd try at rooting is throwing the above error. I can see the file renamed as check_rooted.bak in the dir but cant rename with ES_FileExplorer utility as I dont have write permissions
TIA

harbinger13 said:
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
TIA
Click to expand...
Click to collapse
Download root checker from the market its free if you like make sure you gift the developer a buck
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
When I used kfu the last time it took 2 times to stick don't try much until you know its rooted and you have twrp installed and fff boot loader and have made a backup you can restore if something goes gunny.
---------- Post added at 03:02 AM ---------- Previous post was at 02:51 AM ----------
If you have done everything right it should reboot a couple of times the last thing you will see is twrp screen with a big reboot button click reboot and your done you will then see the fff splash screen of the boot loader it should eventually boot into the os
---------- Post added at 03:10 AM ---------- Previous post was at 03:02 AM ----------
The same rules apply for 6.3.1 watch nat3mil do it http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US

[Q] Problem with superuser/superSU/rooting

This being my first post a HI EVERYBODY is in order.
On with the show.
So, I managed to unlock my bootloader via htcdev website, i slapped on the cwm recovery and managed to put a custom rom on my cell.
The rom in question is the jellyking, works fine, everything is great.
PROBLEM:
although ive tried several cm10 roms i liked jellyking the most but on all of them i had troubles getting root.
what happens is that i download es file manager, set it to give me root and mount system as RW, popup says that the preinstalled (with rom) superuser app granted those rights and that everything should be superb, but I couldnt copy files from my sd to lets say /system/media (wanted to change my bootanim) it says file copy failed, only once i did manage to copy a file but i dont know how.
The question:
when i put a custom rom, do i need to reapply the famous root.zip or maybe install busybox as my first app or maybe flash over the existing superuser app the superSU app which seems to update the root binaries sucessfully.
BOTTOM LINE:
What is the exact (if any) procedure that I need to follow to get perm root access (copy rights) to my own phone, each and every reboot.
Thanks in advance for all Your insights,
Humbly,
egr2lrn

[Q] Can I flash the OTA zip in TWRP?

Finally, the OTA came out. But it's still not available in my area here (Malaysia) so I have to wait for it to come. But I'm a little short of patience here, and while the OTA zip files is out, I thought I could just sideload it via adb. But when I try to make it work, I spent 4 hours facing some adb problems. I'm using Linux most of the time, and I have Android SDK downloaded. It was so troublesome to make adb work. Initially adb just couldn't find my device. So I Googled about it, and did some modifications on the PC to solve the usb problem and finally adb could connect to my device (while in Android). Then I started to follow the instructions to sideload. I booted into TWRP recovery using adb command and just to be sure, I ran ./adb devices again while the device is in recovery. But then adb shows no device connected. Trouble. I thought it's the problem with some drivers so I used Windows to try it again. Same problem again. Then I started to Google about it and found some forums that mention that it only works when I manually boot into recovery (Volume Down+Power+Volume UP). I followed. And finally, it solved it. It was only the first problem. Then I pressed into adb sideload mode in TWRP and started sideload mode. And just to be sure again, ./adb devices, no device connected again. I thought it's some bug in TWRP, I stopped sideload mode, and went back to the main menu of TWRP (where adb once can detect the device) and ./adb devices again. Guess what, it shows no device again. Problematic. I restarted my pc for many times, switching from Windows and Ubuntu for many times, repeated the above steps for many times, but the problem is just so random. I even changed the usb cable but no luck. So I decided not to use adb anymore and I've Googled for just flashing ota in TWRP. But there's just very few articles on it. Most of them are using adb and stock recovery. Some of it mentioned that if custom recovery is present then it shouldn't have to be so complicated but none of them shows how to use custom recovery. And one of them says I could just flash the OTA zip file through custom recovery but no instructions for it. The last one is my ideal method now, but because of lack of references, I'm not sure about it.
In short:
-Nexus 7 with TWRP
-problems when using adb to communicate with my device whether it's in normal boot, TWRP recovery, sideload mode, or whatever
-problem is so random and I cant figure out whats the problem
-tried installing and uninstalling and installing drivers again and again
-I dont wanna lose my data
-fed up
Question:
Is the OTA zip file recovery flashable? I dont wanna mess with adb anymore. It just wont work properly with me. Or I have to wait for OTA to reach me?

Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.

jj14 said:
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
Click to expand...
Click to collapse
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?

ImjuzCY said:
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
Click to expand...
Click to collapse
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.

jj14 said:
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
Click to expand...
Click to collapse
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.

ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
cool! (it will almost certainly require a new XPosed app because of all the changes that Lollipop brought, but it won't hurt to leave it installed)
Edit: Just read http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5 - looks like you will need to uninstall XPosed too

ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5

Broke root. any suggestions appreciated.

Followed systemlessly root guide. Worked perfectly.
Installed busy box last night, broke root. (dont remember if installed /bin or /xbin.)
Reboot, lost root. Cant uninstall BB due to no root.
Tried reflashing suconfig/su/suhide with updated twrp 3.1.1.1. No success.
About to flash factory images, but worried the no.provisioning edit will be deleted, and if the not rootable problem persists, I'll loose hotspot completely.
Any ideas why the happened, and how to go about fixing the problem? Could use Su/magisk, doesn't matter which.
Sorry to make a new thread. If you can help, I'll gladly buy you a beer. Been working on this all afternoon and im getting fed up.
Addition- selected, do not install twrp, but got the "application" installed anyway. Tested, not a permanent recovery.

Download supersu 2.82 and make sure its on your device
Boot into twrp
Hit "advanced"
Hit "file manager"
Scroll down and find "fstab.marlin" and tap on it
Hit "delete" and swipe to confirm
Return to home of twrp and install Supersu 2.82 SR5 (Do not install the su config or suhide)
Reboot to system, check if root is present.
Use root to uninstall busybox files, clear busybox app data, open the app and let it install in the default location it provides.
Then reboot and install suhide if needed.

Where/how to find hosts file in Android 8.0 Oreo?

Hi fellow developers,
I need to do modify my HTC 10's hosts file, but with the latest OTA update to Android 8.0, I find it impossible to make any functional changes to the hosts file. Does anyone have a clue?
I am rooted, and S-OFF with TWRP recovery.
In recovery, I have tried modifying all of these:
/system/etc/hosts
(which is only there normally when the phone is booted and running, I can't figure out where it's coming from)
/data/hosts
/data/data/hosts
None of these work.
Please help, if you know! I cannot find any information online, after hours of research and troubleshooting...
cheers,
Jordan
P.S. Despite S-Off and root, I find that many root procedures don't work when android is booted, disappointed, cannot understand why. Miss my One M8!

jorxster said:
Hi fellow developers,
I need to do modify my HTC 10's hosts file, but with the latest OTA update to Android 8.0, I find it impossible to make any functional changes to the hosts file. Does anyone have a clue?
I am rooted, and S-OFF with TWRP recovery.
In recovery, I have tried modifying all of these:
/system/etc/hosts
(which is only there normally when the phone is booted and running, I can't figure out where it's coming from)
/data/hosts
/data/data/hosts
None of these work.
Please help, if you know! I cannot find any information online, after hours of research and troubleshooting...
cheers,
Jordan
P.S. Despite S-Off and root, I find that many root procedures don't work when android is booted, disappointed, cannot understand why. Miss my One M8!
Click to expand...
Click to collapse
Hello mate.
Have u tried edit hosts file using any text editor? try get Root Explorer, navigate to /system/etc/ and mount R/W. select hosts file & edit.

aM- said:
Hello mate.
Have u tried edit hosts file using any text editor? try get, navigate to /system/etc/ and mount R/W. select hosts file & edit.
Click to expand...
Click to collapse
Thank you aM- for replying, someone hears my cry for help!
I tried to mount /system as read-write and instead got an "Error : The operation could not be completed".
This is frustrating, as again, I got S-OFF specifically for this purpose.
And SuperSU seems to function normally, asking me to grant permissions.
I had the same problem with a terminal editor, being unable to SU, permissions denied.
Are you on Android 8.0 Oreo as well?

jorxster said:
Thank you aM- for replying, someone hears my cry for help!
I tried to mount /system as read-write and instead got an "Error : The operation could not be completed".
This is frustrating, as again, I got S-OFF specifically for this purpose.
And SuperSU seems to function normally, asking me to grant permissions.
I had the same problem with a terminal editor, being unable to SU, permissions denied.
Are you on Android 8.0 Oreo as well?
Click to expand...
Click to collapse
Yes, I'm on Android 8.0. Have you check either your device rooted or not? if rooted, supposedly on terminal also should be no problem.

aM- said:
Yes, I'm on Android 8.0. Have you check either your device rooted or not? if rooted, supposedly on terminal also should be no problem.
Click to expand...
Click to collapse
I should be rooted.. I am unlocked and S-OFF.
I flashed SuperSU-v2.82-201705271822.zip from TWRP recovery.
I have the SuperSU app installed and it seems to run normally.
But I cannot "su" in a shell like you did, cannot mount /system partition as write, really, cannot do anything root.
Do you know what version of SuperSU you rooted yours with?
P.S. Android 8.0 as well, not 8.1 (which I presume hasn't rolled out to OTA yet)

jorxster said:
I should be rooted.. I am unlocked and S-OFF.
I flashed SuperSU-v2.82-201705271822.zip from TWRP recovery.
I have the SuperSU app installed and it seems to run normally.
But I cannot "su" in a shell like you did, cannot mount /system partition as write, really, cannot do anything root.
Do you know what version of SuperSU you rooted yours with?
P.S. Android 8.0 as well, not 8.1 (which I presume hasn't rolled out to OTA yet)
Click to expand...
Click to collapse
Currently I'm using SuperSU from here https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Navigate to system/bin
"su" file in there?
Sent from my HTC 10 using Tapatalk

Thanks so much aM- and fmedrano1977.
I've made progress. I reflashed my phone with the later SuperSU SR5 zip that you posted, wiped dalvik/cache, rebooted. Now I can "su", as well as mount /system/etc as read/write. Success!
There was a couple of catches, at least two or three other apps that don't seem to work with root anymore (like the previous file explorer I had, supposed to support root, but only "root explorer" worked after I bought it).
Now modifying my hosts file seems to have no effect, but I suppose that's another issue for another day. As it stands, I can now edit my hosts file thanks to your help.
Cheers!!

jorxster said:
Thanks so much aM- and fmedrano1977.
I've made progress. I reflashed my phone with the later SuperSU SR5 zip that you posted, wiped dalvik/cache, rebooted. Now I can "su", as well as mount /system/etc as read/write. Success!
There was a couple of catches, at least two or three other apps that don't seem to work with root anymore (like the previous file explorer I had, supposed to support root, but only "root explorer" worked after I bought it).
Now modifying my hosts file seems to have no effect, but I suppose that's another issue for another day. As it stands, I can now edit my hosts file thanks to your help.
Cheers!!
Click to expand...
Click to collapse
Glad to hear that. Happy modify system mate.

jorxster said:
Thanks so much aM- and fmedrano1977.
I've made progress. I reflashed my phone with the later SuperSU SR5 zip that you posted, wiped dalvik/cache, rebooted. Now I can "su", as well as mount /system/etc as read/write. Success!
There was a couple of catches, at least two or three other apps that don't seem to work with root anymore (like the previous file explorer I had, supposed to support root, but only "root explorer" worked after I bought it).
Now modifying my hosts file seems to have no effect, but I suppose that's another issue for another day. As it stands, I can now edit my hosts file thanks to your help.
Cheers!!
Click to expand...
Click to collapse
i was lead here from an answer for my question, i;m curious when getting the host file prepared ,the steps others helped you with,did your device data get deleted ?