I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Well it's like anything. If you don't know why you need something you probably don't need it
Sent from my HTC One using XDA Premium 4 mobile app
bloodyniceben said:
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Click to expand...
Click to collapse
the phone never come unrooted .. you never had root installed properly
when it's flashed correctly from recovery it will not just go away
http://download.chainfire.eu/396/SuperSU
Flash that from recovery and you'll be rooted
I had SuperSU installed, everything was fine, anything I did with the phone worked. After a week it said the SU binaries were missing, and you couldn't get into SuperSU to do anything, but previously you could. If the phone was never rooted correctly like you say, i would have had this problem from the start.
Also after rooting I used a root checker which said I was rooted, but after this Su binary issue started, it said I wasn't rooted.
Still, I'm back to unrooted now, and the only reason I did it was to get Sense 6, which has since come out as an update, so I'm no worse off
Ben
Sent from my HTC One using XDA Free mobile app
bloodyniceben said:
I had SuperSU installed, everything was fine, anything I did with the phone worked. After a week it said the SU binaries were missing, and you couldn't get into SuperSU to do anything, but previously you could. If the phone was never rooted correctly like you say, i would have had this problem from the start.
Also after rooting I used a root checker which said I was rooted, but after this Su binary issue started, it said I wasn't rooted.
Still, I'm back to unrooted now, and the only reason I did it was to get Sense 6, which has since come out as an update, so I'm no worse off
Ben
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
This is a rom issue not a root issue. Could have also been an issue with the kernel. To be honest if you dont really use the root functions then there maybe no need for you to have it. To be honest most people dont really need root. They just wanna seem cool with some things they can show off on their device instead of using it for anything important or handy. I would advice to judge for yourself. Take the extra options/security risk and weigh it against remaining stock which has less options/secure.
I agree with the previous post, if you don't know what it is, you probably don't need it. As far as SuperSu disappearing, it sounds like either you didn't install it correctly or something changed. The ideal way to install SuperSu is to install via the recovery. And even so, if you reinstall your OS, you will need to reinstall SuperSu. Software does not simply disappear, something had to be done to hasten it's departure. An easy fix to your issue would have been to download the SuperSu zip package from http://download.chainfire.eu/supersu, and install it via your recovery. What I personally don't like about locking a bootloader is that now it says TAMPERED at the top of the screen.
Your issues seem to be with the restoring to stock process which HTC do make a bit convoluted, triggered by the root error not rooting itself.
Now to answer your question: My main reason for rooting is I want to take fine grained backups. Second is lots of clever people have come up with mods and improvements I like to install over the stock Sense ROM.
If you don't need anything that needs root, no need to root. Simple as that.
bloodyniceben said:
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Click to expand...
Click to collapse
if you want RUU search @ htc1guru.com with firmware/software version
flash same firmware again + flash custom recovery + flash SuperSu it will resolve your problem
Related
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
hpsauce37 said:
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
Click to expand...
Click to collapse
hello you are in need of the new 4.3 superuser.zip
http://download.clockworkmod.com/test/superuser-4.3-beta3.zip
if you are using CWM, when it asks to fix su upon reboot, select NO
Wow thank you!!!!!
You have no clue, or maybe you do, how lost I got trying to root my HTC One. This is all new to me, but this forum has helped massively. I found that the supersu zip I had was the older version when I already had 4.3 uploaded before rooting. This community rocks!
why do my gapps processes keep crashing?
NM forgot to full wipe
So I have the same issue - my only question is that I am running 4.4 now. Does this super user file still work or is there a 4.4 version?
Just use "SuperSu" if you face any root acces issues
Sent from my loved HTC One S using (most time buggy) Tapatalk
HHEELLPPP
Hi there, Im new to the rooting world, I have a htc one m7 from sprint trying to sim unlock it, as far as I know I unlocked the bootloader, tampered it, and rooted, but no access to super user so I can sim unlock it. I downloaded and installed this App that you mention, but still keeps saying no binary updated, and with this 4.3 version says there was an error installing superuser. Please help, I dont know what to do.
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Any updates on this? I'm trying to get root on an HTC One M7 that I just purchased and I'm running into the same error.
Thanks!
Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.
nigerson said:
Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.
Click to expand...
Click to collapse
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.
powdered_donuts said:
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.
Click to expand...
Click to collapse
Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)
http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)[/QUOTE]
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx
powdered_donuts said:
http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)
Click to expand...
Click to collapse
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx [/QUOTE]
So, I am on mj5 right now since I got the OTA update and I am no longer rooted because of this. How can I flash to stock or reroot and install xposed? Or am I ****ed?
*EDIT USED KINGO INSTALLED FRAMEWORK ALL IS GOOD IN THE HOOD *
Hi guys, thanks for the forum and i hope to become a part of it. I've been under so much stress since yesterday, my galaxy s3 (on EE in the UK) for the first time decided it's data was corrupted yesterday after my battery died, never done this or anything like it before, and it wouldn't let me access the phone itself unless the data was reset.
I had a lot of very precious pictures in my gallery from the weekend, which unfortunately chose not to backup to google+ for the last few days, even though it always has up until recently. All night/day i've been trying to figure out and get software to recover these photos, which i think is possible as i did it a long time ago on a blackberry, but not android yet. I'm just hoping it can be done so the photos aren't forever lost, the other stuff gone doesn't bother me so much.
The guide i'm following (here: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705) says it needs to be rooted first, and i can't even get past step 1. I've only ever rooted my old galaxy S1 (which worked back then) but i can't seem to get the S3 to do it. And now my phone also believes there's no sim card in and i get no signal now.
this is the guide i followed: http://www.ibtimes.com/how-root-sam...-jelly-bean-official-firmware-tutorial-975812
though i think i need a newer PDA file to flash my i9305 with. I'm on the EE network running 4.3 jelly. It installed Super SU but root checker says it still isn't rooted.
So have i messed this up? And is there any hope for me getting these pictures back?
Thanks in advance for any help, it's much appreciated.
if you are running on 4.3 then you are not following the right guide to root...
use THIS ONE instead... if it fails to root use the workaround part, i used it and worked....used the workaround to install custom recovery and then flashed chainfire zip from his website and updated SU and worked.
are you still able to boot the phone?
Thanks for the response, tried that guide and still getting no signal on my phone (no mobile connection at all, sim card isn't recognised as being there) and i don't think it's rooted right. Still saying SuperSU has stopped working when i try to open it.
I put the Root_SuperSU.1.02-Busybox.1.21.0.zip on the internal SD and tried that too.
Which is the chainfire zip you're talking about, could you possibly link it? I don't really get what you mean by custom recovery, do you mean it's the same as flashing the Busybox thing from recovery mode?
And yeah it still boots up normally...
use that tutorial to install a custom recovery...then install this SuperSU - http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1 - flash it in custom recovery....after that update app with playstore and should work.
but i suggest you get it to a specialized shop to get your photos back...
#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!
#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.
How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated
Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!
Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues
thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.
Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6
CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
I'm using a Samsung-SGH-I537UCUCOC7, Android Version is 5.0.1
TowelRoot didnt work for my device so I used KingRoot as a last resort. However I only wanted to use it to install the root and not have it around as its a bit intrusive. I tried using SuperSume but no matter what I do when I run it, it always stops at 10%. I've tried 5 different times.
Do I have any other options?
Do you have full root or does it go away when you reboot? If you have permanent root and SuperSUMe is not working there is also a script file you can use. You'll have to search for it. I had the same problem with a Kyocera Hydro Icon I had. I ended up using the script, but I think I figured out why at first neither of them were working.
If you could try something as a test for me I'd appreciate it. In my case I rooted the phone with an older version of kingroot, then kingroot updated itself to the new app...but not the new binary. So I unrooted with the newer app and then rerooted with it also so I would have the new binary. After that the script worked for me and I bet SuperSUMe would've too, but I tried the script first.
So try unrooting and rerooting with the newest version then try SuperSUMe...if it fails then try to find the script.
RealWelder said:
Do you have full root or does it go away when you reboot? If you have permanent root and SuperSUMe is not working there is also a script file you can use. You'll have to search for it. I had the same problem with a Kyocera Hydro Icon I had. I ended up using the script, but I think I figured out why at first neither of them were working.
If you could try something as a test for me I'd appreciate it. In my case I rooted the phone with an older version of kingroot, then kingroot updated itself to the new app...but not the new binary. So I unrooted with the newer app and then rerooted with it also so I would have the new binary. After that the script worked for me and I bet SuperSUMe would've too, but I tried the script first.
So try unrooting and rerooting with the newest version then try SuperSUMe...if it fails then try to find the script.
Click to expand...
Click to collapse
I used version 5.0.4 of kingroot. How low do you want me to go?
Also the binary thing your talking about I noticed it when I downloaded SuperSU it said it was missing some binary and I couldnt use that app either even after I rooted with KingRoot. It sounds like my only hope is that script you were talking about but I'll try a lower version of KingRoot first. I have no idea where I would look to find that script so I can get more info what I'm suppose to search for let me know.
RemixDeluxe said:
I used version 5.0.4 of kingroot. How low do you want me to go?
Also the binary thing your talking about I noticed it when I downloaded SuperSU it said it was missing some binary and I couldnt use that app either even after I rooted with KingRoot. It sounds like my only hope is that script you were talking about but I'll try a lower version of KingRoot first. I have no idea where I would look to find that script so I can get more info what I'm suppose to search for let me know.
Click to expand...
Click to collapse
For me I rooted with whatever version you get from their website, but after you root it downloads and updates itself. I unrooted and rerooted with the update to get the new binary. Also, I'll see if I still have a copy of the script on my cpu. If I do I'll post you a link.
Sent from my SM-T210 using Tapatalk
RealWelder said:
For me I rooted with whatever version you get from their website, but after you root it downloads and updates itself. I unrooted and rerooted with the update to get the new binary. Also, I'll see if I still have a copy of the script on my cpu. If I do I'll post you a link.
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
I used version 4.5 instead of the latest 5.0.4 and afterwards ran SuperSume. It got rid of it no problem and I still have my root access. Thank you.
last question, I also own a Samsung Galaxy S7 Edge. It was my first Android phone ever and I wasnt aware that AT&T keeps the bootloader locked on their phones. Will any amount of begging and crying to them get them to unlock the bootloader? If the answer is no are there any unofficial means to unlock my bootloader for the phone?
RemixDeluxe said:
I used version 4.5 instead of the latest 5.0.4 and afterwards ran SuperSume. It got rid of it no problem and I still have my root access. Thank you.
last question, I also own a Samsung Galaxy S7 Edge. It was my first Android phone ever and I wasnt aware that AT&T keeps the bootloader locked on their phones. Will any amount of begging and crying to them get them to unlock the bootloader? If the answer is no are there any unofficial means to unlock my bootloader for the phone?
Click to expand...
Click to collapse
Not too sure but I think it's possible. They unlocked and rooted the verizon and t-mobile versions, so possibly...maybe even by the same process. Search youtube.