Develop Bugs

Dealing with Sprint / HTC Preinstalled Junk - Startup Auditor or Just wait for Root?

I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!

If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.

gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?

berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.

okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it

I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.

elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.

go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?

elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D

All done!!! :-D now to flash rom... good times!
Thanks all

Simple root(compared to joeykrim) for shw-m110s and galaxy cousins

http://forum.xda-developers.com/showpost.php?p=8406167&postcount=223
So this already has a home. But I'm seeing that it works, very likely in ALL galaxy S cousins, and in fact possibly even in all 2.1 and 2.2 android phones. This is NOT the joeykrim method but it's related (but simpler and better, and obvious to most of you devs). Sadly this slowly gets rediscovered somewhere about once every two weeks for the past couple of months . There's a thread in epic started a few days later with the same trick, and a thread on droid forums:
http://www.droidforums.net/forum/re...08-multiple-phones-root-them-unroot-them.html
a couple of weeks earlier with the same trick. And a page on cyaongenmod where they show it for just one of the cousins.
It's nice for anyone who doesn't want to flash, and/or doesn't have a fully working recovery mode needed to use some of the one click methods (update.zip). Moreover... it probably works on pretty much EVERYTHING. The one clicks distract attention from the fundamental solutions because they don't always work on everything and new phones come out like popcorn.
Also I've included some useful related information about how to setup some of the popular initial root tools (with some personal bias, but not unlike a custom ROM), and how to undo it all. Making it a whole package custom ROM alternative (albeit a very lite alternative ). I haven't seen another post with all of this in one place.
I don't know where I should post this though because there is no general forum that I guess is likely to get read much that connects all the devices this may work on. But since it's working on more devices now and probably on froyo too, it seemed it might be helpful to someone to expose it a little beyond the shw-m110s sticky on issue 6. (even it has already been exposed before).

isnt this the same as superoneclick lag fix?
this didnt work for me on my i9000 froyo rom.

Ok.. well, does rageagainstthecage still work? Do you know? Did you try just that? the information "it didn't work" isn't very helpful. But then when you have one button you tend to get one response, and that's partly my point.
If you can get root with rageagainstthecage, the rest can all be worked out. And much more easily if more people in the community start to fear less the internals cause they're given information about what's going on, and it's VERY simple, as you can see in my post.. there's only ONE thing (properly installed su) you need to have root on ANY device. (getting root is a different issue, but the hard part is done) And there's no reason not to be explaining that in the BIG FAQ.
Indeed.. it looks like it probably is the same thing (but it's not really documented) . That did not exist when I first posted it.. hence why I worked it out myself. Personally I'm not a fan of one click anything, not as the primary reference at least. Because, ok.. it seems rageagainst the cage probably works on anything. A decent faq somewhere actually EXPLAINING what's required for root, and what rageagainstthe cage does (losely) and at least an example of how to use it on some device then is a good starting place for new phones.. new froyos.. good reference info.
However instead what happens is somebody else comes out with their latest method.. releases it as the mysupermagiconeclick method.. or even if it's script, without any explanation (and most people wouldn't understand, but maybe a few would). And then what happens?
Joeykrims script gets adopted on like 5 diferent devices where it isn't even needed(no offense to him.. he provided what he knew and got some people going who wouldn't have been otherwise). Multiple problems are created because of it. and that's not even a one click. That's a script for people who aren't too afraid to type script and still nobody noticed it wasn't needed?
Now a big one click comes out and someone just says "this doesn't work".
I see so many people saying "I don't know how to use adb" (even after you just told them "type adb push". It's very different that the winmo atmosphere a few years ago.
Anyway, I rageagainsthecage is the only alternative I know of to flashing or update.zip so it would be good if it got a little more attention I think and if people stopped treating the task of copying in 3 little files with permissions like some mystery work for "devs" to handle and folks to praise on high. I mean it's nice if someone can make a gui(and it takes work).. but it's amazing how hard it is often to just find an explanation of the very simple thing that's actually being done. (edit: even in Clshortfuses superoneclick thread.. he links to an older thread with the commands, but it's in page 49 or so.) There's like 5 commands needed with about 2 slight variations (nand unlocking and the setuserid joeykrim problem) that will root anything without flashing or destroying data, and that's not explained in a simple faq around here.)

By the way another reason it might not work is the rageagainsthecage exploit doesn't always (usually though) work the first try, and works better on some usb ports than others.

elsewhere:warlordxp said:
I have a problem with rooting my JP6
The Odin version seems to get well. But after reboot no root.
Then i tryed the SuperOneClick version.
I get this msg.
Pushing rageagainstthecage...
failed to copy 'rageagainstthecage' to '/data/local/tmp/rageagainstthecage': No such file or directory
OK
Click to expand...
Click to collapse
and I found the same thing on some german site.
maybe /data/local/tmp doesn't exist on froyo for I9000. If anyone was playing with a prompt and had instructions that point out that you only to need to copy it to ANY place where you can write and execute, they might figure out what's going on in one minute, and find another place to copy it to like just /data/local or wherever tmp got moved to. In every case I've seen problems, it was never that the exploit didn't work.
Now ok.. it's possible that somehow they've figured out a way to completely block writing new executable files anywhere from a shell. In which case it would need to get installed through an apk maybe, but it's still possible. Applications do run, all the time; so can this. Knowledge is power... not one click buttons.

ok then ill give you a bit more detail.
you are right, i cant see why it is failing although i can see where it is failing. if i had access to the script to see the steps its trying to take i could work it out but its compiled into a binary as far as i am aware.
the script pushes the file to the device, and it runs for the first loop. it installs the su command and superuser.apk, then loops back to make further changes (i.e. it kills adb and reestablishes a connection). when it loops back it tries to mount something, and fails saying "failed to find mount point" or something similar.
the su command works in shell/terminal until the phone is rebooted, then it is lost. the superuser doesnt work at all (i.e. no superuser requests are generated by apps requiring it, they just fail saying root not available).

kanemari said:
ok then ill give you a bit more detail.
you are right, i cant see why it is failing although i can see where it is failing. if i had access to the script to see the steps its trying to take i could work it out but its compiled into a binary as far as i am aware.
the script pushes the file to the device, and it runs for the first loop. it installs the su command and superuser.apk, then loops back to make further changes (i.e. it kills adb and reestablishes a connection). when it loops back it tries to mount something, and fails saying "failed to find mount point" or something similar.
the su command works in shell/terminal until the phone is rebooted, then it is lost. the superuser doesnt work at all (i.e. no superuser requests are generated by apps requiring it, they just fail saying root not available).
Click to expand...
Click to collapse
Great it sounds like you basically understand what is going on and aren't afraid of a tiny bit of typing. I think MANY people fit that description including myself a few weeks ago. But... the steps are not usually explained as you say. So... click the link in my first post again. It's all explained there. I've started a section there on exceptions.. including what I think might be going on with yours, but your description is a little different from the ones I copied in, so we don't know yet. So go at it, and good luck. I'll be glad to help if I can but my crusade is to get more people who want to to be able to play with it themselves (and to be able to ask questions too, though especially when getting new devices/roms rooted)
I assume you know about adb and and how to run it by hand in the first place. I don't describe that and there are faqs that do, including I think the Big FAQ. That obviously must work first.
P.S. I may add some linux/mac scripts shortly... piece of cake to do.. already did it for the joeykrim method. CLShortFuse is adding linux support but it involves 175 MB of cross-platform compatibality libraries and is at least almost as hard to setup as it is to just use adb. To each his own. It's a neat accomplishment if it works.
For me I push the unroot script to my phone and can unroot when I walk in a store if I want to. I like Rynza's apk for that, but it doesn't work with my phone (3 button, yes... update option, no )

too much verbage for me daddybear...
but anyway ill give it a shot next time i need to root my device and let you know if i come up with anything useful.

The first to admit to cracking the code . But you only get full credit if you know the reference too!
the su command works in shell/terminal until the phone is rebooted, then it is lost.
Click to expand...
Click to collapse
actually.. if this is really true.. it's almost certainly a joeykrim style problem. The other symptoms are harder to follow, especially depending if superuser never worked or only didn't work after reboot. Anyway, this will certainly get resolved in time I'm sure. If you had su working at all.. then it's just a matter of applying the right tweaks/work arounds (which are likely already known).

Z1 Compact 5.1.1: Replaced KingRoot with SuperSU, then endless Sony Logos & Reboots

Z1 Compact 5.1.1: Replaced KingRoot with SuperSU, then endless Sony Logos & Reboots
Got a pair of refurb Z1c D5503s, and updated both to 14.16.A.1.216-R3D (Android 5.1.1) using the Sony Companion.
Both phones show "bootloader unlocked", so I did a successful root of one of the phones, using KingRoot.
Then I attempted (and failed) to use Replace_Kinguser_with_SuperSU v 1.2 , which grabbed its own update to 2.4 when started.
While the SuperSU claimed to have replaced Kinguser sucessfully, upon reboot, the phone began an endless loop of reboots, never making it past the Sony Logo.
I was able to stumble through recovering from the TA partition using flashtool, so now I am back where I started, with Sony stock 14.6.A.1.216
The tutorials I can find are very outdated versus the software packages themselves. For example, I still have no idea where the "/drivers" directory might be for flashtool, or why the new version hides the directory in ".flashtool".
But I'd like to root the phone, so as to not just disable, but to remove the bloatware from the minimal internal memory, and I'd also like to root the phone to be able to take full advantage of the micro-SD card for data and apps.
But what to replace Kingroot Kinguser with once it is rooted, and/or how to do so without crashing the phone on reboot so badly?
Sorry to be so clueless... these "new" phones are our (myself and my wife's) upgrade from a pair of Samsung Exhibit IIs, just to show you how out-of-date I am on rooting phones. (^.^)
Thanks!

packetfire said:
Got a pair of refurb Z1c D5503s, and updated both to 14.16.A.1.216-R3D (Android 5.1.1) using the Sony Companion.
Both phones show "bootloader unlocked", so I did a successful root of one of the phones, using KingRoot.
Then I attempted (and failed) to use Replace_Kinguser_with_SuperSU v 1.2 , which grabbed its own update to 2.4 when started.
While the SuperSU claimed to have replaced Kinguser sucessfully, upon reboot, the phone began an endless loop of reboots, never making it past the Sony Logo.
I was able to stumble through recovering from the TA partition using flashtool, so now I am back where I started, with Sony stock 14.6.A.1.216
The tutorials I can find are very outdated versus the software packages themselves. For example, I still have no idea where the "/drivers" directory might be for flashtool, or why the new version hides the directory in ".flashtool".
But I'd like to root the phone, so as to not just disable, but to remove the bloatware from the minimal internal memory, and I'd also like to root the phone to be able to take full advantage of the micro-SD card for data and apps.
But what to replace Kingroot Kinguser with once it is rooted, and/or how to do so without crashing the phone on reboot so badly?
Sorry to be so clueless... these "new" phones are our (myself and my wife's) upgrade from a pair of Samsung Exhibit IIs, just to show you how out-of-date I am on rooting phones. (^.^)
Thanks!
Click to expand...
Click to collapse
Use SupetsuMe from Playstore.
Best regards,
Coempi

packetfire said:
Got a pair of refurb Z1c D5503s, and updated both to 14.16.A.1.216-R3D (Android 5.1.1) using the Sony Companion.
Both phones show "bootloader unlocked", so I did a successful root of one of the phones, using KingRoot.
Then I attempted (and failed) to use Replace_Kinguser_with_SuperSU v 1.2 , which grabbed its own update to 2.4 when started.
While the SuperSU claimed to have replaced Kinguser sucessfully, upon reboot, the phone began an endless loop of reboots, never making it past the Sony Logo.
I was able to stumble through recovering from the TA partition using flashtool, so now I am back where I started, with Sony stock 14.6.A.1.216
The tutorials I can find are very outdated versus the software packages themselves. For example, I still have no idea where the "/drivers" directory might be for flashtool, or why the new version hides the directory in ".flashtool".
But I'd like to root the phone, so as to not just disable, but to remove the bloatware from the minimal internal memory, and I'd also like to root the phone to be able to take full advantage of the micro-SD card for data and apps.
But what to replace Kingroot Kinguser with once it is rooted, and/or how to do so without crashing the phone on reboot so badly?
Sorry to be so clueless... these "new" phones are our (myself and my wife's) upgrade from a pair of Samsung Exhibit IIs, just to show you how out-of-date I am on rooting phones. (^.^)
Thanks!
Click to expand...
Click to collapse
Did the suggestion work for you?

levone1 said:
Did the suggestion work for you?
Click to expand...
Click to collapse
In a way, yes, but now I have a phone without the KingRoot bloatware/possible malware, but where the USB connection to my PC cycles between "up" and "down" more than once every minute, leaving me thinking that the Super SUme program itself is the source of the problem for my phone.
I have no idea how to debug this issue, other than to start all over again, and verify that the problem only shows up after the Super SUme scripts run.
This is starting to be a lot of work for a phone.

packetfire said:
In a way, yes, but now I have a phone without the KingRoot bloatware/possible malware, but where the USB connection to my PC cycles between "up" and "down" more than once every minute, leaving me thinking that the Super SUme program itself is the source of the problem for my phone.
I have no idea how to debug this issue, other than to start all over again, and verify that the problem only shows up after the Super SUme scripts run.
This is starting to be a lot of work for a phone.
Click to expand...
Click to collapse
Flashtool is the way to go. Did you figure out the directories yet? There is a /Flashtool folder and a /.flashtool folder. The drivers are in /Flashtool. With Ft working, you can get it done easier, but it will take a little work.

levone1 said:
Flashtool is the way to go. Did you figure out the directories yet? There is a /Flashtool folder and a /.flashtool folder. The drivers are in /Flashtool. With Ft working, you can get it done easier, but it will take a little work.
Click to expand...
Click to collapse
Flashtool is no problem, but I was unable to find an up-to-date guide on using it, and some of the instructions are no longer applicable to the current version, so I did not want to brick the phone making a classic noobie mistake.
I will start over after I make contact with the Super SUme fellow, as perhaps he has a suggestion that can help.

packetfire said:
Flashtool is no problem, but I was unable to find an up-to-date guide on using it, and some of the instructions are no longer applicable to the current version, so I did not want to brick the phone making a classic noobie mistake.
I will start over after I make contact with the Super SUme fellow, as perhaps he has a suggestion that can help.
Click to expand...
Click to collapse
K... Let me know if you want links, etc. I don't mind.

levone1 said:
K... Let me know if you want links, etc. I don't mind.
Click to expand...
Click to collapse
Thanks for your kindness... my problem is clearly that I do not know how to install Super-SU and remove Kingroot manually, and the Super-SUme script seems to do some sort of damage to phone-side USB functionality in the specific case of a Sony Z1 compact running Android 5.1.1 before being rooted. (Saying this clearly so the next guy can find this with a search)
So, is there a set of instructions that allows one to do by hand what is done by Super-SUme? I'm sorry to be so clueless, but it has been several years since I unlocked a pair of phones for my wife and I, and in that time, Android has gone from 3.x to 5.x.
Kingroot can be copied over to the root directory of the 5.1.1 phone, and it runs without problem, so then the problem may be a result of the work done by the Kingroot developers to maintain a toehold on each smartphone their tools root.
=-=-=-= Warning, Opinion Follows, Use At Your Own Risk =-=-=-=-=
There is a disturbing/amusing post here on xda from the Kingroot guys that describes the various tools that remove their software as "malware". The loss of perspective that the use of such a term evinces is troubling. Or maybe revealing of the actual motivation of the Kingroot guys. [I dunno, I'm so old-skool, I designed computers that used "ECL", and "bit-slice ALUs", and none of them was smaller than three refrigerators, not counting optional STC vacuum-column 6250bpi reel-to-reel tape drives. Shoot, that was so long ago, we did not even buy any "ones", we'd have a guy come in 3 days a week to cut zeros in half, and bang them flat to hand-craft the "ones" for us so we we'd have both ones and zeroes! (^.^) ]
One would expect that the Kingroot fellows, being in the unlocking biz, would figure out for themselves that if they made the same error as the phone vendors, and made anything extraneous "irremovable", that they would need a stopwatch to measure they very short time lag before someone came out with a countermeasure to remove the extraneous stuff they installed when unlocking to allow the removal of vendor extraneous stuff. If their "purify" tool is any good, people will seek it out and use it, and some will pay for a "pro" version. If it is not any good, people will remove it, no matter how they try to make it impossible to do so.
The fact that I paid $3.99 to the Super-SUme guy to sell me code to remove Kingroot and Purify easily should be a lesson to the Kingroot guys. The fact that the tool failed to do the job properly and screwed up my phone is beside the point. The point here is that the Kingroot guys have not built confidence in their integrity, and the fact that they tried to "bundle" extraneous irremovable stuff with their root exploit and made their root exploit hard to remove/replace positions THEIR OWN product as the "Malware" and the Super-SUme product as "Malware Removal".
I don't care if the download is 100 Gig, if he Kingroot guys distributed a package that did not have to "phone home", and could be installed on a phone with no SIM card installed, and no WiFi, and if the resulting rooted system did not try to "phone home to Shenzhen", and could be easily modified as the user saw fit, including removing the whole mess and replacing it with Super-SU, I don't think anyone would have any problem with paying the $3.99 (or even $9.99!) to the Kingroot guys directly, rather than to Google Play Store, so that the Super-SUme guy gets $1 or whatever.
But clearly, there are some who think that money is not what the Kingroot guys are after. And that's the scary part.

packetfire said:
So, is there a set of instructions that allows one to do by hand what is done by Super-SUme?
Click to expand...
Click to collapse
Here is my thread on doing it yourself from scratch - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-stock-5-1-ub-t3203247 I'm not an expert, so I have confidence to say that it is not hard to do. The biggest part is downloading all of the files. I can also guarantee it working on the last 3 fw updates, since I've done it. It is a bit of work and time, though. If you have working adb and Ft, you're good to go.

levone1 said:
Here is my thread on doing it yourself from scratch - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-stock-5-1-ub-t3203247
Click to expand...
Click to collapse
Danke! Worked great, unlike the $3.99 app which if removed/refunded and then reinstalled to verify a good install, no longer allows one to return and refund the purchase!
Anyway, now I am using the rooted status of the phones to remove unwanted bloatware by hand.
THANKS!!!

packetfire said:
Danke! Worked great, unlike the $3.99 app which if removed/refunded and then reinstalled to verify a good install, no longer allows one to return and refund the purchase!
Anyway, now I am using the rooted status of the phones to remove unwanted bloatware by hand.
THANKS!!!
Click to expand...
Click to collapse
No problem. Did you go ahead and flash NUT's dual recovery? Recommended to accompany this method, since by default you won't have busybox or r/w access.

Just Rooted LG G3. Have both KINGUSER&SUPERSU. Can't uninstall/replace. PLEASE HELP!

Just Rooted LG G3. Have both KINGUSER&SUPERSU. Can't uninstall/replace. PLEASE HELP!
Finally succeeded in rooting my LG G3. Have Sprint LG G3 5.0.1 LS990ZVE. Newer to computers and technology such as this, especially android, as far as entering this deep into information. Hours of research and a couple attempts finally lead to success in rooting phone. Process that I found on this website led me the way. Used 'LG_ROOT_SCRIPT'. Well, after being successful, I am now stuck with both KINGUSER and SUPERSU. I cannot get rid of or replace either one. (all I have read is leading me to believe that SUPERSU is superior to KINGUSER, so I would like to have that on operable.) I have tried numerous strategies that I have found all over internet and nothing seems to work. Some processes I am weary of doing because I do not want to accodently unroot my phone. If someone could help and possibly teach me how to go about this, I would be very grateful. Please keep in mind that even though I am not an unintelligent person, I seem to be very inadequate when it comes to subjects such as these. Thank you for your time. Please help.

seezle said:
Finally succeeded in rooting my LG G3. Have Sprint LG G3 5.0.1 LS990ZVE. Newer to computers and technology such as this, especially android, as far as entering this deep into information. Hours of research and a couple attempts finally lead to success in rooting phone. Process that I found on this website led me the way. Used 'LG_ROOT_SCRIPT'. Well, after being successful, I am now stuck with both KINGUSER and SUPERSU. I cannot get rid of or replace either one. (all I have read is leading me to believe that SUPERSU is superior to KINGUSER, so I would like to have that on operable.) I have tried numerous strategies that I have found all over internet and nothing seems to work. Some processes I am weary of doing because I do not want to accodently unroot my phone. If someone could help and possibly teach me how to go about this, I would be very grateful. Please keep in mind that even though I am not an unintelligent person, I seem to be very inadequate when it comes to subjects such as these. Thank you for your time. Please help.
Click to expand...
Click to collapse
I had that same issue. Then it would not let me update the binaries for supersu and get rid of Kinguser. I take it that it is doing the same to you? You either have to do it manually by getting into the actually files and renaming supersu and flashing it. What I did though is I downloaded an apk called SUPERSUME 6.0 that you can find either here in xda Or just by googling it. There will be a minsstream version that you have to pay for, which would be nice to do if you want to support, there is also an apk version you can download for free, just keep searching. All you would have to do is download and install the program. Open and run it. Don't mind it saying sketchy **** that may make you think twice when you first begin program. (i stopped it at first. Lol) just run the program. At the end it will ask you to open supersu or it will just do it for you. Open it and update and you will have supersu ready and running.

seezle said:
Finally succeeded in rooting my LG G3. Have Sprint LG G3 5.0.1 LS990ZVE. Newer to computers and technology such as this, especially android, as far as entering this deep into information. Hours of research and a couple attempts finally lead to success in rooting phone. Process that I found on this website led me the way. Used 'LG_ROOT_SCRIPT'. Well, after being successful, I am now stuck with both KINGUSER and SUPERSU. I cannot get rid of or replace either one. (all I have read is leading me to believe that SUPERSU is superior to KINGUSER, so I would like to have that on operable.) I have tried numerous strategies that I have found all over internet and nothing seems to work. Some processes I am weary of doing because I do not want to accodently unroot my phone. If someone could help and possibly teach me how to go about this, I would be very grateful. Please keep in mind that even though I am not an unintelligent person, I seem to be very inadequate when it comes to subjects such as these. Thank you for your time. Please help.
Click to expand...
Click to collapse
Hey mate dont be afraid to remove Kingroot..
Since you have a custom recovery, you can always just flash superSU (version for your rom/device) via the recovery, and update the superSU binary within the app when you launch it for the first time. You will receive 2 options. Normal update, custom update.. Choose normal update.. Youll be prompted to reboot.. Do so, and you're rooted . Now you need to open superSU app, and configure some settings to your liking.. You're safe to remove Kingroot/user and delete its app data.. Then reboot phone in to custom recovery and clear cache and dalvik-cache from recovery and reboot back in to system.. And you're done..
***NOTE*** if you plan on installing an app called lucky patcher (cant really discuss it because of its usage purpose). Just make sure you disable "Mount namespace seperation" from superSU settings so that the app can function correctly..
Sent from Sony Xperia Z5 E6653

Issues after Xposed instalation

Problems after installing XPOSED
I believe it is because of XPOSED, because it was after its installation.
It plays me playstore, it must have been temporary error or go to know why
Basically, I can't start with root. Nor, pressing volume up and power.
Yes, I try to start with root, the samsung letters are always fixed and the phone does nothing (I waited until 15 min.)
I put tp you, the messaget that i was put in Magisk post, another night¡
Hello, good to everyone
I'm Sergio from Zaragoza, happy to talk with you!
Although, rather, it is asking for some help or a tutorial to see if I can avoid having to wait and restart the entire root process, although I don't think I can help it
My current situation is as follows; my computer died 2 weeks ago and until Friday the new one does not arrive because it was much better to wait for black friday, so now I only have my Android device, which is a Samsung A50 - FN
During these weeks, I survived thanks to him but now I have one more problem! Haha!
I am not a programmer, at the moment and pulling high I am an amateur, so my lack of knowledge is high. However, at the end of October and thanks to a forum partner who explained how the S A50-FN could be rooted, I got the root, sorry but I put the referral of the partner in question as I navigate in this wonderful forum without the app and with the mobile browser is very difficult, since I use an instant translator to understand you well and the truth is very frustrating to navigate (very, very slow) to that you add that due to the problem I write to you (I think that's why, more than anything to find an explanation) I can not install applications, but that is what I think least should matter right now!
Forgive the long text, I just want to explain my best in my current curious circumstances xD¡¡
Basically, before installing two modules of Xposed with all my joy and completely ignorant! Or rather, I could not imagine, that I could leave the phone on the screen of the letters of Samsung! Suddenly my cell phone was not going! I had no means of contacting human haha ​​or anything at all.
So, try with very little hope (I did not remember exactly how it was done) enter the recovery mode and from there, try to find a solution!
Fortunately, on the second attempt I managed to restart the phone and it started! Since if I turned it off, it automatically restarted and stopped working, again the letters of SAMNSUNG, but when I restarted it started and I could use the phone!
Of course, at the cost of right now I have no root and I can not for example install Apps or God knows how many more things will fail on the device!
I could read something and I think if I had TWRP I could uninstall Magisk by flashing the Magisk uninstaller or God knows, if only the two modules at best!
But I don't have TWRP or any custom recovery since I did it with Magisk and ODIN and I didn't need it .....
So, do you think I can do something to fix it or will I be forced to have a computer and do a hard reset and have to do the process again?
Thank you very much for all your unstoppable work! Hopefully you can help me!