Database Develop

Is rooting really that good?

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

ROM Flash not working - multiple attempts, different ROMs

I soft bricked my Sprint HTC One M7 and can't get a new ROM working. I'll start by saying I am probably in over my head and never should have done this to begin with. On the bright side, this is a backup device essentially being used as a toy. I have spent hours trying different things and searching the forums without finding any threads with the same issue. My apologies in advance if there is a thread I could have read but I could not find one. So, on to what I have done and the current issues I am having.
I'm not sure all of this background is necessary but it can't hurt. I successfully unlocked the phone, loaded TWRP, and I thought, rooted the phone, all using the guide on htconeroot.com. I attempted to run a program that requires root access and it said "no root access". I then used fastboot to load SuperSU 2.46 and it all went south. After I loaded SuperSU 2.46, the phone hung on the HTC One load screen.
At this point, I decided I would just Flash a new ROM to the phone. After spending hours trying to get adb to recognize the phone (a whole different story), I finally managed to get adb sideload to work and flashed the most recent version of Android Revolution. I went through the entire install process and got a message saying the install was successful. However, when the phone rebooted, as it was loading it switched to say recovery at the top and loaded into TWRP. I noticed the message icon at the bottom, center of the screen and tapped it. It switched to a gray screen which said "updating partition details..." at the bottom. It just hangs on that screen. I wiped cache with no luck and had same result when I re-flashed.
I tried Viper ROM 8.0 and had the exact same issue as Revolution.
I attempted Bad Boyz 1.4 which got a little further but still wouldn't load. I tried Bad Boyz 1.2 to see if their ROM with Sense 5.0 would work. That version said install successful and rebooted. I got really excited when it showed updating Android and started counting through app updates. It got to the unlock screen with the time and HTC default background picture. When I pull up the lock to unlock the phone, I get error messages that messages stopped unexpectedly and HTC Sense stopped unexpectedly. It then sits on a white screen with the green HTC logo for ~10 seconds and then reboots. If I let it go without trying to unlock it, it still reboots after 20-30 seconds, caught in an unending boot loop.
I am at a loss at this point. Do I try a few other ROMs until I find one that works? Am I doing something wrong? I should add that the guide I used said nothing about a Nandroid backup so I don't have one ?, and I really don't want to go back to stock anyway.
Thanks in advance for any help.

Bucknut816 said:
I soft bricked my Sprint HTC One M7 and can't get a new ROM working. I'll start by saying I am probably in over my head and never should have done this to begin with. On the bright side, this is a backup device essentially being used as a toy. I have spent hours trying different things and searching the forums without finding any threads with the same issue. My apologies in advance if there is a thread I could have read but I could not find one. So, on to what I have done and the current issues I am having.
I'm not sure all of this background is necessary but it can't hurt. I successfully unlocked the phone, loaded TWRP, and I thought, rooted the phone, all using the guide on htconeroot.com. I attempted to run a program that requires root access and it said "no root access". I then used fastboot to load SuperSU 2.46 and it all went south. After I loaded SuperSU 2.46, the phone hung on the HTC One load screen.
At this point, I decided I would just Flash a new ROM to the phone. After spending hours trying to get adb to recognize the phone (a whole different story), I finally managed to get adb sideload to work and flashed the most recent version of Android Revolution. I went through the entire install process and got a message saying the install was successful. However, when the phone rebooted, as it was loading it switched to say recovery at the top and loaded into TWRP. I noticed the message icon at the bottom, center of the screen and tapped it. It switched to a gray screen which said "updating partition details..." at the bottom. It just hangs on that screen. I wiped cache with no luck and had same result when I re-flashed.
I tried Viper ROM 8.0 and had the exact same issue as Revolution.
I attempted Bad Boyz 1.4 which got a little further but still wouldn't load. I tried Bad Boyz 1.2 to see if their ROM with Sense 5.0 would work. That version said install successful and rebooted. I got really excited when it showed updating Android and started counting through app updates. It got to the unlock screen with the time and HTC default background picture. When I pull up the lock to unlock the phone, I get error messages that messages stopped unexpectedly and HTC Sense stopped unexpectedly. It then sits on a white screen with the green HTC logo for ~10 seconds and then reboots. If I let it go without trying to unlock it, it still reboots after 20-30 seconds, caught in an unending boot loop.
I am at a loss at this point. Do I try a few other ROMs until I find one that works? Am I doing something wrong? I should add that the guide I used said nothing about a Nandroid backup so I don't have one ?, and I really don't want to go back to stock anyway.
Thanks in advance for any help.
Click to expand...
Click to collapse
You have a CDMA Sprint htc one (M7WLS variant) ARHD is a rom for GSM htc one (M7_UL or M7_U variants). You can only flash custom recovery, custom roms, kernels ect that are made for the Sprint HTC One (M7WLS).
So you can flash twrp for sprint, then flash a sprint custom rom
or
return to your stock rom using a sprint RUU.
You can find the sprint roms in the "Sprint HTC One" section of xda. TWRP recovery for sprint can be found on their website, the filename should ends with "wls.img"
If your phone was running on android lollipop then using a lower version than supersu2.46 is what caused the bootloop. Thats why you shouldn't follow outdated guides from 2013 like the one at htconeroot.com
We can help you flashing the custom recovery/rom or the RUU, its up to you.

Thanks for the quick reply. I probably should have realized the CDMA vs GSM issue. I used to sell Sprint phones 20 years ago.
I would rather go with a custom ROM on the phone without all of the bloatware/sprint garbage.
I understand the issue with ARHD but what about Bad Boyz? I am using their Sprint ROM v 1.2 from the Sprint M7 section with no luck. It loads Android all the way to the lock screen with the time, status bar, and sense skyscraper wallpaper but then crashes. I tried 1.4 first and it got to the unlock screen but no status bar or sense background (skyscraper wallpaper).
You mention TWRP for Sprint. Is there a specific Sprint version and if I used a different version would it have gotten that far? Should I install a different version of TWRP and try flashing Bad Boyz again?

Bucknut816 said:
Thanks for the quick reply. I probably should have realized the CDMA vs GSM issue. I used to sell Sprint phones 20 years ago.
I would rather go with a custom ROM on the phone without all of the bloatware/sprint garbage.
I understand the issue with ARHD but what about Bad Boyz? I am using their Sprint ROM v 1.2 from the Sprint M7 section with no luck. It loads Android all the way to the lock screen with the time, status bar, and sense skyscraper wallpaper but then crashes. I tried 1.4 first and it got to the unlock screen but no status bar or sense background (skyscraper wallpaper).
You mention TWRP for Sprint. Is there a specific Sprint version and if I used a different version would it have gotten that far? Should I install a different version of TWRP and try flashing Bad Boyz again?
Click to expand...
Click to collapse
If there is a specific version of twrp mentioned in bad boyz thread, use that one. Otherwise any recent version should work but yes it must absolutely be a sprint twrp recovery.
Here are all the sprint version: https://dl.twrp.me/m7wls/
The M7_UL have different partition layout than the Sprint version (see both links below). The kernel (/boot partition), the OS (/system partition) and the radio (/radio) are not located at the same place on the memory. If flashing a M7_UL rom a Sprint phone you'll end up with the OS flashed on the Kernel partition, the Kernel flashed on the radio partition etc... This should be easily fixed by re-flashing a custom rom (if the rom does include its own kernel and radio to overwirte the bad flash). In the worst case, you'll have to flash a RUU to fix everything and then relfash sprint twrp and a sprint custom rom
http://forum.xda-developers.com/showthread.php?t=2317621
http://forum.xda-developers.com/showthread.php?t=2236254

Thanks for all the help. I was able to work on it again last night. I updated TWRP and was able to get viper ROM loaded and working...mostly. I had to delete HTCSetupwiz.apk to get out of the hands-free activation loop. The only problem is, the home key does not work. I get the haptic response from it but it doesn't do anything.
I tried Viper 8.0 and 9.0 and had same issue. I tried to switch to Bad Boyz and adb was hanging at ~7%. I am feeling much more comfortable with all of this and I think I can fix the loading issue with Bad Boyz. I just tired of fiddling with it last night. Before I do that, any idea how to get the home key working with Viper?
Would it be best to flash the ruu and start over just to make sure there are no lingering problems from screwing up the partitions?
Thanks again for all the help.

alray said:
If there is a specific version of twrp mentioned in bad boyz thread, use that one. Otherwise any recent version should work but yes it must absolutely be a sprint twrp recovery.
Here are all the sprint version: https://dl.twrp.me/m7wls/
Click to expand...
Click to collapse
Sorry to bug in... yeah I know, no need to tell me, people have been telling me plenty enough of their kind thoughts..., but the universal builds http://android.cmphys.com/twrp-m7/
should work on M7_U, M7_UL, M7_WLS, M7_WLV
they use "by-name" partitions, etc
maybe even the official builds, as mdmower is the maintainer, but unsure, since I haven't checked.
Obviously, still doesn't allow you flash a ROM not meant for your particular device, especially that many installer-scripts still use hardcoded mmcbkls, which would seriously break things
hmm, that reminds me.... have to check on something else too

Help, moto x 2014 stuck in 'MOTO' logo

Hey, I have a moto X 2014 (xt1097)(brazil), unlocked bootloader,previously had root.
I updated to marshmallow about a month ago and had no problems whatsoever with it aside from the fact that root didn't already work for it.So yesterday I saw a post about a user that flashed the "SuperSU 2.62 v3" and got root, so I did the same but without flashing twrp(I just booted it)... It worked (sort of) but it was having some problem about a super su binary not working(I lost the screenshot).
With that I started searching for a way to make it work correctly, until I saw someone in a post saying that they wiped the phone and re-flashed the root file and it worked correctly, and that was what I did.. with one little difference I flashed the latest superSU file released (SuperSU-v2.64),but it didn't work, it initiated but there were notifications all the time about something not working(a lot of things).
With that in mind I started the same process I had done to flash the first superSU,wiped the data and cache, turned it on so that I could enable debug mode to start flashing the superSU but this time the phone didn't get out of the big `M` (powered by android) logo.
I seached a fix for it, on other posts people said that wiping everything(except system) and rebooting worked for them, but for me it didn't.
So I need help with this, if anyone can help please do so, thank you.
UPDATE: I just remembered that before that I didn't use the "unroot" function in the superSU version that didn't work, so I think that I got bootloop because of that, but I still don't know what to do.

HTC Desire 626s - Need to completely start over

Hopefully someone has some input on this.
My phone is a 626s, a32eul on T-Mobile. I've had this phone since it came out and really grew to liking it, but lately it's been nothing but a headache. I had it rooted with Kingroot (was the only root at the time that worked) since I got it, but never went any further because there wasn't any ROMs available at the time. Recently I started messing around again and decided to reset and try to upgrade to Marshmallow, but I seem to have caused more problems with it than I anticipated.
I've lost the stock recovery completely, currently have TWRP installed. I've tried to remove Kingroot but no matter what I try it won't go away. I followed a replacement procedure from Supersu, but Kingroot is still present. None of the uninstalls seem to work, tried deleting all related files that I could find with root explorer but it still comes back. Factory reset and wiped everything several times, still there . .
My main reason for all this is to load a de-bloated ROM ( I only have 8G of storage, less than 1G after all the useless BS apps update themselves ) I've turned off all the auto-update stuff on the phone and Google, but it still manages to loop back and download everything anyhow.
Would anybody have some input on this? I'd like to get it back to when I took it out of the box for the first time so I can start over, or at very least get rid of King for good so SU can take over? I've found a couple image files for the stock recovery, but all seem to be corrupted or not correct for this phone.
Thanks in advance for any help you can provide . .

And now I think I've done it. Was messing around in TWRP, I think I fat-fingered the system option when wiping, have no operating system now . . I think my frustration has gotten the better of me on this one.

I might have this thing finally figured out. Seems when I upgraded my laptop to Win10, I never re-installed C++ to keep the RUU file running. I must have sobered up enough because its downloading the file right now after 8 hours of smashing my face on 2 keyboards . .

Yes.
re flash with the original RUU then flash twrp recovery.
With twrp recovery install supersu.
Then you will be rooted.
Best way to flash the RUU.
#1 rename the RUU to 0PM9IMG.zip
#2 Copy it to the sd card.
#3 Put sd card in the phone.
#4 Boot to download mode.
Vol DWN plus Power.
#5 it should ask and say hit vol up to flash the ruu when you boot to download mode.
#6 Hit volume up.
No messing around with windows this way and it works alot better off the sd card.
Download one of the RUU's that we have uploaded to here.
If you need the RUU zip rile let me know.

Noob needs help with XT1096 on Verizon network w/ TWRP and keeps getting OTA prompt

Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!

aeb401 said:
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
Click to expand...
Click to collapse
Try using your favorite applications manager for root and freeze MotorolaOTA. This will prevent the update from being downloaded and you won't get messages about installing the OTA update.