Hello, I am somewhat new here, and I haven't had much trouble with phones before, but I have run into a bit of a snag. I cannot gain root access on my HTC Vivid. I was recently stuck in a boot loop, after trying to flash a different ROM, so I had relocked my phone, and decided I would update to The Vivid's ICS. I fixed the boot loop and everything was fine. I unlocked the phone again, and followed the directions on android authoirty's website to gain root access again. Although everything installed correctly an there was no problems, I cannot gain root access to my phone. If there is any ideas or suggestions I could try, it would be greatly appreciated.
I also wanted to add that I have considered the fact that it is due to the update that I have not gained root, but I would hate to do all that work again, but if I have to I will. If somebody could confirm or deny this, as well as point me in the direction of where I can find the un-updated factory files for the Vivid, that would be extremely helpful.
------------Resolved-------------
It was an error on my part and I forgot to flash the recovery.
What did you did you to to resolve this? I cant get root again. Would like to just keep the factory ICS and have root for now.
papasgot14u said:
What did you did you to to resolve this? I cant get root again. Would like to just keep the factory ICS and have root for now.
Click to expand...
Click to collapse
I actually am using Pirate Ghost's Rum Float Beta 4 right now. It's very good and is almost like stock.
-Meaning I do not think you can have root on stock (to my knowledge). Although I do believe there is a rooted stock release on his website.
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!
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...
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
Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse
ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.
Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...
Hey everyone. Seem to be having a real problem applying an RUU.exe to my phone. I did this a couple years ago without an issue, but now I just get errors, no matter what I try. (Sorry, no error messages at the moment. Computer I was attempting this on had a screen issue. Unrelated. lol)
HTC M8 non H/K, rooted, S-off, unlocked/relocked on 4.4.4. stock rooted rom.
I have some apps frozen through Titanium Backup. Was thinking that may be the issue, but haven't gotten around to trying the unfreeze to see if it helps.
Have attempted using Dual Boot as well, using an sd for the install, and I couldn't get anything at all to work through that.
Was going to RUU so I could just OTA my way to the latest update, but that doesn't seem to want to work.
I'm just looking for the simplest solution to get my phone to the latest update. Don't need anything fancy. A stock rom would be perfectly fine. Wouldn't mind an RUU working, because I can always root after if I really want to. Wiping doesn't really matter. Can backup mostly all I need to.
Any help would be greatly appreciated. More and more of the important apps I use are completely dropping anything below Android 5, and I could really use a solution.
Thanks in advance for any help. ^^
Hey everyone. Is there any solution to my issue? Really need help. Can't use my TD Bank app, the Verizon Fios app, or even the Wal-Mart app anymore, and it's only going to get worse.
Please help me figure out how to update.
Also, I have used an RUU before, AFTER I unlocked the bootloader and went S-off, so I'm unsure why I can't RUU now.