Database Info

[Q] US Cellular Galaxy S4 Root Help

Tried the Noob Friendly "Ask ANY Question" thread, got no answer so I'm going to make a thread just to try and get some help.
Bought a GS4 with US Cellular, currently trying to root it using the motochopper method.
I followed the root instructions using Motochopper exactly, and it appears to work. Superuser is installed on my device, etc, but whenever I attempt run Superuser, I am informed that the Superuser binary must be updated. Naturally, I click "Install", but I am greeted with this message:
"There was an error installing Superuser. Please send a log of the error to the developer."
There is no log.
Yes I have USB Debugging enabled
Yes I installed the drivers
What am I doing wrong here?
The ONLY thing I can think is that there might have been an error with the driver installation - When I plug my phone into my computer it tries to autoplay-install drivers even though I already ran the installer for the drivers before I plugged the device in.
I'm completely lost, any help would be appreciated.

Bump....
Anyone out there who has any experience with USC GS4?

Saimouer said:
Bump....
Anyone out there who has any experience with USC GS4?
Click to expand...
Click to collapse
I'm not any help, but I experienced the same thing on both of my GS4's and am still looking for a solution.

I'm not a pro but...
I also had this exact same problem. After all the time I spent looking for an answer and not finding one, I eventually found a different method. Which is the twrp method found at galaxy s4 root (dotcom) . Also if you have problems with that method, there are lots of comments and one of them probably address your issue. Speaking from recent experience I'm going to suggest downloading Root checker from the play store because it sounds like you don't actually have root yet. Also, what I had to do with me Sch-r970 is uninstall superuser and go with supersu instead (which is what is included with the above method) , and yank my battery out immediately after running Odin so it doesn't wipe it out. I honestly was just wanting to root mostly to use my s4 as a hot spot but after rooting, have yet to figure that out yet. Good luck.

[Q] Root/Custom Rom Help LG LW690 (Optimus C)

Hello,
I am new to the forums and android in general. Anyways, I am wondering if any one could advise me on the best steps to root and update my oldish android phone. It is currently on android 2.2.1 and has no support for 2.2.3 which is why I believe I need a custom rom.. I have looked thru numerous threads and sources but have yet to find a method i fully understand and trust, as i hear it.. you guys are very helpful and i am hoping that is true cause im about to pull my hair out at this point
Thanks in advance for any help, its appreciated very much.

Its great that you are showing interest in this. (Edited out, the device is stated in title xD).
Rooting shouldn't be as hard at installing a custom ROM. Older devices are rarely supported nowadays, unless it's really popular like the HTC Wildfire or something.
The best way to root your Optimus C is by using GingerBreak. Many users that have your device use that.
Info on other useful guides (rooting,cwm,ROMs) go here - http://androidforums.com/optimus-c-all-things-root/
Sent from my Nexus 5 using Tapatalk

Thanks for taking the time to repond/help. Anyways, after some more research I think I found a easy root solution.
http://forum.xda-developers.com/showthread.php?p=13086954
This method seems both easy and very sraight forward. Could any one please confirm? Id just like a lil insight before taking the plunge. lol
Note* I would link the posts stating this does work to gain root access but i cant post outside links untill i have 10 posts on XDA.

Don't worry, the root method should work just fine.
Sent from my Nexus 5 using Tapatalk

Ok, got it rooted
The next step would be to download rom manager and make a custom recovery using clockworkmod?
Btw~ incase someone is confused in the future. The root procedure was a few simple steps.
Before doing these steps make sure usb debugging is active. Also temp disable your anti-virus as it will flag the apk as a virus, This is a false positive.
1. Download the file from the first post in the thread. http://forum.xda-developers.com/showthread.php?t=1049944. (the easy way for me "since i don't have a usb cord" was to click the QR code link on the first post and scan it with one of the many free qr scanner apps from the play store.
2. Navigate to the download and install the APK.
3. Open Gingerbreak.
4. Click "root" and wait for your device to reboot. Thats all :laugh: "if the process takes more then ten minutes reboot your device and run it again"
5. You can go ahead and uinstall/delete the apk once you have sucessfully rooted.

The next step would be to download and install the devices custom recovery.
Don't just install any, again go to that site I had provided you with earlier that have the stock and custom .imgs with steps on how to install it.
Sent from my Nexus 5 using Tapatalk

Ok so.. I have a problem, I was about to setup a custom recovery when all of a sudden Super User decided to update and now im a little lost. I have still have root acess and all of my root only apps are working perfectly fine. but every time i use a root app or reboot my phone since the SU update i get a message saying my binary files need to be updated. I try to update them and it fails every time, I have looked though a few threads and the only fix i could find was to use busybox installer. But.. busybox will not install on my device. How do i go forward with this? I don't want to mess anything up.. specially since i just thought i had it all figured out. :crying:

Nevermind, I guess i found a decent work around, I uninstalled the update and forced it to not auto update. I don't know if this is a bad practice but it seems to have solved the issue.

I like LG' phones. I am using LG P500 and very like...:good::angel:

Basic Root Question

I very recently purchased (as in less than a week ago) a Google Pixel (5") from the Google Play store. I would like to root it, but have a few questions that I could only seem to find vague answers to online. Firstly, does the Google Play purchased version of this phone come automatically with an unlocked bootloader? I saw several posts online that this was the case, but the posts are all pretty old (10/2016, about 9 months ago) and nothing really since then. Is there a way to verify/check if the bootloader is unlocked?
Secondly, the phone I got has Android 7.1.2 (build NKG47L). These - posts look to be the most recent info on rooting this phone, but they mention a different build number. Does anyone know if this is still an accurate process?

Unlock bootloader in developer options by toggling, then use OEM unlock in fastboot, Install TWRP, and flash latest superSU in TWRP. Done.......
Sent from my Pixel using Tapatalk

Are you the same alienjon as on FB, with the Light Whip?
Bootloader is probably locked - it was on mine when new from Google Play - Aus and about 6 months ago, but locked bootloader is part of Google policy so it probably still is. Unlock like this:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
be aware that unlocking the bootloader will wipe your phone (would keep your data secure it someone had stolen it and was unlocking it to hack it), so do that early.
I root as per Chainfire's instructions, there's no easy way to update and keep root at the moment (Flashfire is supposed to work but it doesns't for me) so I reroot after each update, worked for the June update.
There are a few things to be aware of; TWRP is up to 302rc2 but some people have had trouble with that, I still use twrp 302 rc1 which works reliably (just boot it, to flash SU then reboot I haven't installed it). SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
https://plus.google.com/+Chainfire
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.

@maulich That's perfect. Took me about an hour and a half to root, but most of that was reading and re-reading instructions to make sure I didn't mess anything up. I did notice that there is now some device protection feature that gets disabled when you unlock the bootloader. I checked online and it seems that this basically is a feature that factory resets the device in case someone tried to force themselves into a stolen device. I'll look around, but any suggestions for security features to implement for a rooted device?
@Clancy_s Sorry to disappoint, but no relation to an alienjon on FB. You are correct that it was locked, but I really love how easy it is to unlock. I'm used to phones purchased from Verizon that are beastly to unlock. My last phone (Galaxy S5) never got a workaround for the bootloader from what I recall (though after the Towel Root process stopped working it was almost a year and a half before a new rooting procedure was discovered - kudos to the devs that figured that problem out!)
In any event, thanks for the input on unlocking and rooting. I looked at a few different websites, but the procedure appears to be the same for unlocking that you found. This is the rooting procedure I used and worked fine, though the directions weren't as straightforward as you'd think; ie: the latest TWRP has a .zip but no .img to download on their website and I didn't trust anything else I found online that claimed to be the correct .img file. I used the next most recent version (RC1 - I saw several warnings against the alpha builds) and didn't have any problems. I also used the latest SuperSU (2.82, I believe). A few posts mentioned sticking with 2.79 because of bugs with the newer version, but those were from several months ago and elsewhere it stated that this issue was fixed. It seems to be working great for me
Clancy_s said:
SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
Click to expand...
Click to collapse
Unfortunately I didn't see your post until after I rooted. I can verify, though, that flashing the SuperSU zip worked fine without any additional steps. (ie: boot into TWRP image, flash TWRP and SuperSU zips, which I did together).
Clancy_s said:
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
Click to expand...
Click to collapse
I did not. When I tried to submit my initial post I got a server error. It didn't look like anything had gone through so I went back and resubmitted, which worked. I later realized that the first post did, in fact, go through but I couldn't figure out how to delete it. My apologies for the dupe.

alienjon said:
I couldn't figure out how to delete it. My apologies for the dupe.
Click to expand...
Click to collapse
In a web browser either on the PC or on the phone, click the exclamation point in the triangle /!\ in the lower left corner of the post you want to report, report it to a moderator and ask them to please delete it, or move it, if you ever post something in the wrong section.

Thanks. I'll remember that in case it comes up again.

Phone was rooted and not sure how to remove

A couple of months ago I bought a used Samsung Galaxy S 7 edge from a place called Aarons. A friend and I quickly realized that the phone had been rooted at one point, and I only recently believe I figured out what was used. The phone of course was wiped when I got it, but whatever was used was never removed. Normally I wouldn't care so much however it is preventing security updates. I'm not very good with this kind of stuff so I am NOT sure what to do to either remove it from my phone or get the updates I need.

if nothing helping you should considering flashing stock firmware as last option, i think this will work

If you want to unroot, I think some unroot.zip files that can found across the net might be helpful.
Also, if it is rooted with magisk, I don't think there is a reason to remove it.

First you have to figure out what app it was rooted with. It's probably Magisk or SuperSU. If it's one of them you can either unroot the phone through the parameters of the "root control" app or flash the unrooting zip which you can download it from the official magisk thread or the supersu website.

This is what I found concerning what was on the phone. I may not every be right about it. Which is why I wanted someone with more knowledge to help. As I said my main concern is my inability to do security updates. whatever it is, it's even preventing me from connecting my phone to my PC.
If you'll can determine the best course of action from the screenshot that would be great. Like I said, I know nothing about this kind of thing, so I have no idea where to start with flashing the firmware our weekday unroot.zip I should be looking for.
Edit: so apparently I'm prevented from posting the image because I have under 10 posts. I'll figure that out later, but I was using sd maid when I found this info. Under device it says hero2lte @ 6.0.1 (23). Under root status it says none for su binary, but that there is a built-in superuser app.

Little help with rooting Kyocera Torque E6710, please.

Yes indeed, I'm an Android n00b, but not a total n00b. Sincere apologies if this has already been addressed/solved. I've been lurking around these forums for a couple of weeks now (and read all the recommended threads and joined obviously) and haven't been able to find a solution. Kingoroot seemed to work (both pc and android), but only upgraded to 4.1 jellybean. The minimum required is 4.4 so essential apps can be installed. At this point, just knowing whether or not it's possible would be great.
My search actually started two months ago when I picked up this phone. Extensive searches have yielded results, but most have been non-functional like this site...
https://koselas.com/how-to-install-custom-rom-on-kyocera-torque-e6710/
and the ones found on the forums here just didn't work or the question was never answered. (here for example...https://forum.xda-developers.com/general/rooting-roms/kyocera-torque-e6710-unlock-t3241129).
Any information will be greatly appreciated. Thanks to all of you who even bother to read this and have a great day.

Andr0id n00ber said:
and the ones found on the forums here just didn't work or the question was never answered. (here for example...https://forum.xda-developers.com/general/rooting-roms/kyocera-torque-e6710-unlock-t3241129).
Any information will be greatly appreciated. Thanks to all of you who even bother to read this and have a great day.
Click to expand...
Click to collapse
Howdy, I found the method which worked for me toward the end of this thread: https://forum.xda-developers.com/showthread.php?t=2204320&page=60
UPdownLoAD said:
I don't recall if FR 1.60 or 1.90 will work, but ONLY one of those two will work. You need to reboot immediately after trying and then install SuperSU from the Play store, as Framaroot will NOT install SuperSU as it says it will.
After you install & opened SuperSU to update binary, follow my instructions I posted in the link to get hotspot working. Make sure you choose grant all w/o notification in SuperSU because it will NOT pop up giving you the option to grant root access request.
It works for sure. If you are having trouble, try a hard reset prior to rooting.
It should also be noted there is no stock ROM to flash if you screw up, so make sure you backup the files you remove from /system should you choose to uninstall bloatware.
Beyond that, it must be user error. I have rooted 7 Torques on various firmwares, including 3.000sp with no difficulty other than trying to figure out which version of FR works.
Click to expand...
Click to collapse
I used Framaroot version 1.9.0 on my Kyocera Torque E6710 running Android 4.1.2 (stock), Software version 3.000SP.
Framaroot version 1.9.3 didn't work for me.
LMK if this method works for you

@VinGrif...
Thank you very much for taking the time to answer this question. At the moment, I've got a large backlog of work and other projects so, it may be another week or two before there's time to do this. Once completed, I will update on the success (and which worked). Just wanted you to know that your answer was appreciated, but I'm swamped for the holidays. Thanks again!