Develop Bugs

[PATCH] Working Superuser/su for newer Sense ROMs

Anyone following the RUU threads already knows about this and it's starting to get more attention now. The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
WAL journaling, as built with these new Sense ROMs, is using exclusive locking. Why is this important for Superuser? It's the one situation where you have an application running within Android's process space and one outside of it, both accessing the same sqlite database. When su runs, it opens the sqlite database to check whether you have allowed access for said command to run. If not, a call is made to the Android application, which fires up and prompts you for an answer. Problem is, su has the database open with an exclusive lock (i.e. nothing else can touch it), so Superuser (the Android app) fails to open the database and cannot run. It'll either force close or do nothing.
To fix this, I have modified Superuser and su. Both changes have been submitted to ChainsDD for review. You can look at his git repository's pull requests to see the changes I'm proposing. I'm basically changing the journal mode being used by su one that is non-exclusive and Superuser to close its' database when sitting idle. I couldn't change Superuser's journal mode no matter what I did; it seems to be set deeper in the stack than I can access.
Here are the links to my pull requests on Github if you want to review the code:
https://github.com/ChainsDD/android_packages_apps_Superuser/pull/14
https://github.com/ChainsDD/android_system_extras/pull/1
Anyway, the end result is I have a working Superuser. Here are the caveats:
This is not an official build, so it's signed with my key, not ChainsDD. He has merged my patches into his Github repository so they should be making their way into a release soon.
I've artificially incremented the version number to 9.9.9, to make sure if you install my version, it'll "win" over any other installed version. Also, this prevents the Market from nagging you for updates.
I don't recommend using this version unless you must. In other words, you are on one of the Sense ROMs which is broken. Use an official build otherwise.
If you ran the RUU and have trashed your custom recovery (Clockwork), this isn't going to help you root the device again. Superuser is a tool for managing root access, not obtaining it.
If you are running Virtuous, you DO NOT need this.
Download Patched Superuser Flashable Zip​

great work rmk! but i still prefer to stick with your virtuous.

I'm trying to work around the no root available for 1.72 problem with my stock HTC Z rom updated to 1.72 OTA, but with Rage method temp-root I'm stuck with a frozen terminal after the 'Force Close' step, starting the terminal the 3rd time in the process. I've replaced the gfree_temp_root package's su file with the one provided here, used the APK provided here (pre-installed the apk too before the attempt). It's unfortunately stuck with a frozen black terminal window. Probably the Rage thingy doesn't work with the new 1.72 update, or am I using these files correctly at all?
(guide http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29 )

ChainsDD merged my patches into his repositories today so they should make it into an official release soon.

Nice! Is ChainsDD going to be changing Journal Mode himself?

thanks for this, confirmed working on DHD.

Just for a correct understanding:
I need to have root like described here to use SU right?
Or is it now possible to get the new Update via OTA and get root with this method and its a solution for rooting 1.72?
Thanks!

Dacoco said:
Just for a correct understanding:
I need to have root like described here to use SU right?
Click to expand...
Click to collapse
That's a DHD thread and this is the DZ/G2 forum. So you're either in the wrong forum, or looking at the wrong procedure (which could brick your phone).

Soo.... Us stock 1.72 people can root??

MacaronyMax said:
Soo.... Us stock 1.72 people can root??
Click to expand...
Click to collapse
There has been more than one report that rage doesn't work either, on the 1.72 ROMs.
Also, there's the issue of S-OFF that needs addressing, whether that can be re-done at 1.72.

I dont understand, or I miss some information. The 1,72 ROM is not patched yet (or what?).. Then. If I install 1,72 I will loose root. So in what cases I will need this patch?

denich said:
I dont understand, or I miss some information. The 1,72 ROM is not patched yet (or what?).. Then. If I install 1,72 I will loose root. So in what cases I will need this patch?
Click to expand...
Click to collapse
Check this thread - http://forum.xda-developers.com/showthread.php?t=886023
The patched su/Superuser is just part of the solution.

steviewevie said:
That's a DHD thread and this is the DZ/G2 forum. So you're either in the wrong forum, or looking at the wrong procedure (which could brick your phone).
Click to expand...
Click to collapse
Oh! You're right. I just followed some links. Okay thanks.

steviewevie said:
Check this thread - http://forum.xda-developers.com/showthread.php?t=886023
The patched su/Superuser is just part of the solution.
Click to expand...
Click to collapse
According to this- there is now root method to 1.72.. I don't understand, why this patch is needed if rooting 1,72 is not availeble?

denich said:
According to this- there is now root method to 1.72.. I don't understand, why this patch is needed if rooting 1,72 is not availeble?
Click to expand...
Click to collapse
Cause the Virtuous 0.8.X is build from the Egypt 1.72.X Release, if I understood it right

b1oh4zard said:
Cause the Virtuous 0.8.X is build from the Egypt 1.72.X Release, if I understood it right
Click to expand...
Click to collapse
Is the Egypt RUU rootable?
That could solve our problems!

&partialy working for me.. still creating read-only -wal and -shm files
here is an another solution: http://saraev.ca/su/
it is modified to "chmod" own databases - have a look at README file included
don't forget to grant permissions to superuser itself
EDIT: this is a dirty workaround, I hope someone can make it better...

seo said:
&partialy working for me.. still creating read-only -wal and -shm files
here is an another solution: http://saraev.ca/su/
it is modified to "chmod" own databases - have a look at README file included
don't forget to grant permissions to superuser itself
EDIT: this is a dirty workaround, I hope someone can make it better...
Click to expand...
Click to collapse
The one in your link is a dirty workaround for sure, it modifies baksmali code. Mine is working as intended. The wal and shm files are only present when you're actually sitting in the Superuser app. I'll modify the code some more to close the DB anytime it's not being read or written from. As it stands it's already rare to trigger a case where a request would fail.

rmk40 said:
The one in your link is a dirty workaround for sure, it modifies baksmali code. Mine is working as intended. The wal and shm files are only present when you're actually sitting in the Superuser app. I'll modify the code some more to close the DB anytime it's not being read or written from. As it stands it's already rare to trigger a case where a request would fail.
Click to expand...
Click to collapse
yeah i know that..

Hi,
This patch works only on Desire Z or I can install in my Desire HD?
Regards,

[Q] Unroot EVO and still keep a custom rom?

Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
The image that is used in unrooting is a stock ROM. What I want to do is setup my phone - the way I want it with Mikfroyo - with all the tweaks etc and then "just do the unrooting part". If that makes any sense - I don't need any superuser permissions etc.
Long story short - can a phone be unrooted with a custom ROM instead of a stock ROM?

im pretty sure this is impossible dude, sorry, just leave it all rooted, whats the problem

I know you can't unroot and keep a custom ROM but I wonder if there is a way to hide the fact that you're rooted from the app. What kind of message pops up when you install it?
Sent from my PC36100 using XDA App

It just says that Good cannot run on a rooted phone and just locks the app - I have to call IT to get an unlock code using the device ID that is displayed in Good's pop-up message.

It has to be checking for something specific and I bet there is a way to fudge it but unfortunately that's outside my realm of understanding. I would ask one of the devs here about it.

What permissions does the App request when you install? It could just check for SuperUser

SSjon said:
What permissions does the App request when you install? If could just check for SuperUser
Click to expand...
Click to collapse
I which case you could either delete superuser or use it to block the app... perhaps?

I am sure its more complicated than that - if they are touting themselves as a replacement for blackberry security for iPhones and Android - I seriously doubt a simple fudging of the superuser permissions will deceive it. Also, I'd like to comply with my company's requirements for using an Android phone so I don't get into trouble.
So from what I understand - you cannot have a custom ROM on an unrooted phone. Thanks so much guys - I'll just have to learn to live with the bloated stockware and manual restores arghh......

It's not possible.... to unroot, you'd have to RUU, which returns the phone back to stock. And then, you'd have no way of flashing a custom rom unless you rooted again

ok this is one thing that I am starting to not understand here...
so many people when they answer - say "yes" it can be done or "no" it can not be done...
...ummm where is the why? It would be very informative to know such things or if someone has even tried said thing before.
like why can't you just run a ROM or other flash file from renaming the file and letting the stock loader do the flashing? ......answer: because the stock loader does a file signature check - see? that makes sense and answers the why. it also helps users to retain the information as well as understand it.
I would love to know why the OP can't just run the unrevoked s-on tool from here http://unrevoked.com/rootwiki/doku.php/public/forever#custom_splash (in the FAQ section) without removing his custom ROM and just make sure he doesn't use any apps that need the su access. sounds like it should work? has someone done this and found that it does not work? flashing back to s-on should just prevent flashing to any other ROM's I would think from everything I have read in this forum.
or once s-on is back does it also check the current ROM on the phone and would cause some issues? would be great information to know. because if the security only checks file signatures of flies to be flashed and not the current ROM it seems like the OP could do what he is wanting to.
well, just thought I would ask to see if I could gain some more understanding as to the mechanics of everything

It would be good to know if this works with Good for Enterprise. I am stuck on an SGS 2.1 with Telstra and want a non stock ROM but really need to use Good.

ushkand said:
Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
Click to expand...
Click to collapse
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html

bkrodgers said:
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html
Click to expand...
Click to collapse
My thoughts exactly

Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.

ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
Thanks for the information. What is the ROM that you are using?

bkrodgers said:
Or maybe one of the temp root methods would work.
Click to expand...
Click to collapse
are there still temp root methods that work on the EVO?

I am using Mikfroyo 4.5.

Just came across this thread and was seeing if your GFE was still working? I have a DX and put a custom ROM and could not get it to work. I'm waiting for my new PIN and have removed SU to see if it works.

ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
I rooted my HTC Salsa to install apps2sd which is great, but what commands do i have to run and where to be able to rename su.apk ?
Thanks,
Mike

Is There A Way To Unroot Back to ICS

I know there must be a developer at work trying to make it happen but i need to go back to normal stock from the latest epic touch update w/o losing data thanx...

Rooting/unrooting with adb
The safe way is to know exactly what was modified in your system to root the device, and carefully undo the changes in the proper order. IMO, an app that roots a device *should* have unrooting capability as well because the developer of the app knows how the rooting process works, and how to undo the changes. Of course, the rooting process should be done in a way that allows it to be undone.
If you try to guess the process, and you don't know exactly what you are doing, you could brick your device, so be careful. I am not saying that as a disclaimer, but as an actual warning. Please take it seriously.
I had to root my tablet (also running ICS) manually through adb from my desktop Linux system. The method I followed was to install a custom su command in both /system/xbin and /bin, and then a Superuser app. It is not very complicated. I honestly don't know much about this yet, and just followed instructions that were posted at this site. The tablet was new, and I was ready to just re-install Android if things went wrong.
Does anyone know more about this? I tried to find more technical information on rooting, but was flooded with search results on what app to use, and other "user-level" information. I would like a full technical explanation if anyone has bothered posting such a thing. Do the apps all do the same operations? Is the procedure always the same for a given version of Android? And is there a corresponding method of unrooting, that works on all devices? If not, then why not?

jayts said:
The safe way is to know exactly what was modified in your system to root the device, and carefully undo the changes in the proper order. IMO, an app that roots a device *should* have unrooting capability as well because the developer of the app knows how the rooting process works, and how to undo the changes. Of course, the rooting process should be done in a way that allows it to be undone.
If you try to guess the process, and you don't know exactly what you are doing, you could brick your device, so be careful. I am not saying that as a disclaimer, but as an actual warning. Please take it seriously.
I had to root my tablet (also running ICS) manually through adb from my desktop Linux system. The method I followed was to install a custom su command in both /system/xbin and /bin, and then a Superuser app. It is not very complicated. I honestly don't know much about this yet, and just followed instructions that were posted at this site. The tablet was new, and I was ready to just re-install Android if things went wrong.
Does anyone know more about this? I tried to find more technical information on rooting, but was flooded with search results on what app to use, and other "user-level" information. I would like a full technical explanation if anyone has bothered posting such a thing. Do the apps all do the same operations? Is the procedure always the same for a given version of Android? And is there a corresponding method of unrooting, that works on all devices? If not, then why not?
Click to expand...
Click to collapse
I fully agree a 100%, but thanx to SFHUB the problem was solved...

LG G4 Root?

Hello XDA community,
I recently traded in my old iPhone for this new LG G4, and am so glad to be converted from iOS to Android! Anyways, one of the main reasons I switched is because root access would enable me to maximize the potential of my phone. The only problem is...I have looked vastly throughout XDA and other Android developer havens for root guides and have gotten so confused as to where to start. Can somebody direct me to the right place, or even better, guide me through the process?
Thanks!
(I am using the Verizon G4 (VS986) with Android 5.1.)

DId you have a good look through this thread?
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
It seems daunting but the first things you can do prior to the flashing are
-Get the software you need installed and tested
-Learn how to put your phone into download mode
-test to make sure your phone can communicate with your computer the way it should
-Download all the files you need (stock kdz and matching rooted image version)
Take the time to read each step, and if you have any questions, ask before you proceed, not after you have completed the step.
Good luck! The group here is very helpful so do not hesitate to ask.

goofball2k said:
It seems daunting but the first things you can do prior to the flashing are
Click to expand...
Click to collapse
I will definitely look into that thread! Quick question, what exactly is flashing? I know it has to do with modifying the operating system..but I honestly do not understand the purpose and benefit. Could you explain that to me?

Flashing is basically copying OS onto your phone and installing it.

Okay. So in this root you copy an OS with root permission?

cl_miller said:
Okay. So in this root you copy an OS with root permission?
Click to expand...
Click to collapse
Yes. With this method, you are basically putting a portion of the OS on that is already rooted. That is why it is important to make sure you have the correct versions.

Done?
I followed all of the steps provided in the link you shared, and believe that my device is now rooted! At least, I think and hope. How can I be sure? And if it was successful, what should I do next to make use of my root access?
Thanks again

You should see the SuperSU app. Open it, it may/should prompt you to update.
Otherwise, download root checker from the play store

Done! Now, are there any resources for what I can do next?

Modify marshmallow system image?

I haven't took the plunge to 6.0 yet because I'm not ready to part with root yet but what if we were to modify the system.img and re-flash it? I mean similar to injecting root, but don't inject root. We could at least bock ads with a hosts file, push the file to enable tethering, and debloat. Once done, none of those things require root other then to maybe update the hosts file. Anyone that has updated willing to try? I can help by getting files and commands together. Anyway, just thinking out loud here, thanks for reading lol

The problem is with 6.0, Google made changes so that the only way to achieve root is to modify the boot image instead of the System image. Since the VS986 has a locked bootloader, the phone will refuse to boot if you modify it from stock, potentially bricking it.
6.0 + locked bootloader = no root.

As I said above, I'm not wanting to push root to the image, I realize it's blocked now. What I'm proposing is to modify the image to achieve 2 main things, ad blocking and tethering. If we push the 2 files needed for that, then flash the image, root will not be needed for those to continue to work. It won't work if the system is somehow checked for modifications, but kdz should fix that if it don't work.. Anyone willing to try it?

I can't help you with root but Verizon is no longer charging for tethering on most of their plans. I use it all the time on my G4 using stock tethering. Double check with Verizon.

People who still have unlimited data don't have tethering included so we need the modified hotspot. And like I already said, I'm not looking to have root, what I'm wanting to try is a little different. I haven't taken the plunge to 6.0 yet, but I'm looking for someone who has but kinda regrets out cuz they lost root.

jweber228 said:
I haven't took the plunge to 6.0 yet because I'm not ready to part with root yet but what if we were to modify the system.img and re-flash it? I mean similar to injecting root, but don't inject root. We could at least bock ads with a hosts file, push the file to enable tethering, and debloat. Once done, none of those things require root other then to maybe update the hosts file. Anyone that has updated willing to try? I can help by getting files and commands together. Anyway, just thinking out loud here, thanks for reading lol
Click to expand...
Click to collapse
That is exactly what i would like to do. A little debloating, updating hosts and add cerberus as a system app.
this is a step in the right direction : http://forum.xda-developers.com/g4/general/guide-how-to-modify-img-partition-t3196994

This has been asked a few times in the "Root Injection" thread, once by me, with no answer.
It appears the main problem is the download mode exploit may be closed. Entering commands in the send-command app returns "fail".
I once got the command to backup entered without failing but it ran for almost an hour without generating the system.img.

I guess we have to use a fully fledged kitchen. I was hoping to circumvent that
Gesendet von meinem LG-H815 mit Tapatalk

fr4nk1yn said:
This has been asked a few times in the "Root Injection" thread, once by me, with no answer.
It appears the main problem is the download mode exploit may be closed. Entering commands in the send-command app returns "fail".
I once got the command to backup entered without failing but it ran for almost an hour without generating the system.img.
Click to expand...
Click to collapse
In addition that exploit getting patched, Android 6.0 was changed by Google so that you can only achieve root by modifying the boot.img and kernel, not just the system partition. Since the bootloader is locked, if you do manage to modify the system img, you would at best see no results, or at worst brick your phone.