Related
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
First off, I'm a long-time iPhone user, first time Android owner.
I have an SM-G900A rooted with towelroot and I have to send it back to AT&T for a warranty concern with the front facing camera. I see some elaborate guides on how to flash back to stock. Is that necessary? Will a factory reset from recovery mode do the trick? I'd hate to attempt that first and end up with a brick.
Thanks.
It depends on what you've done with your phone.
The guides are the most complete ways to unroot and remove all traces that the phone was ever rooted. The easiest way to unroot would be to unroot from the settings in the supersu app, that you can find in the playstore. But after that you would need to re-install the supersu app, but don't run it, and then uninstall it again from phone settings. You have to do both steps to remove all traces of root. I've tried each one separate, and yes, some signs were still there. But if you modified the phone in any way, then those modifications may possibly remain.
And no, a factory reset will not remove root. All that does is wipe your userdata, but the root is inside the phone's ROM.
elgrecoFL said:
First off, I'm a long-time iPhone user, first time Android owner.
I have an SM-G900A rooted with towelroot and I have to send it back to AT&T for a warranty concern with the front facing camera. I see some elaborate guides on how to flash back to stock. Is that necessary? Will a factory reset from recovery mode do the trick? I'd hate to attempt that first and end up with a brick.
Thanks.
Click to expand...
Click to collapse
The easiest way is to Odin back to stock ROM.
just follow step 1 to 4 on this guide
http://forum.xda-developers.com/showthread.php?t=2785185
it is pretty simple and straightforward and you phone will be just as you took it out of the box for the first time with no trace of root whatsoever.
.
it worked!
w00t! worked perfectly. Just did steps 1-4.
shortydoggg, thank you for the guide.
eortizr, thanks for the encouragement
Hi all, total newb here. (Sorry I know you probably hate these kinds of threads).
I apologize in advanced if this is a very simple case / has been discussed in the forums.
I've literally read everything I can in regards to this topic but being such a total newbie at this, I'm still not 100% sure if I got this right.
So basically my phone is XT1095 - which I didn't root or unlock boatlader (simply because I don't know why), that suddenly got into a boot loop.
So on that AP Fastboot screen.
So all options (including normal powerup, recovery and factory reset) produces
'failed to validate system image.
boot up failed'.
What should I do at this point? I've read on jcase's thread that this is a simple matter of "easily fixed by flashing proper boot.img".
Where can I find the "stock boot.img"?
I know graffixnyc has KXE21.187-42 files on his website which can be flashed. Is it pre-rooted though?
Or can I just easily use bhp090808's Multi Tool to fix this?
Can it be used while the phone is still in this bricked / bootlooped condition?
Honestly I dont mind being rooted if it means getting my phone fix. But if I can get it done without rooting it then it would be 'great' since if I fail in any way I won't void my warranty.
Sorry for asking a lot of things. As you can notice, I'm totally new at this. I've successfully rooted and install a custom ROM once in my old S3 but it was only because there was a thorough step to step process.
Again, thanks in advance and I really appreciate anyone's help
Cheers.
anyone?
koflok1234 said:
anyone?
Click to expand...
Click to collapse
I wouldn't unlock or root!!! You could lose your warranty. You can try a factory reset, else return your phone for warranty
godutch said:
I wouldn't unlock or root!!! You could lose your warranty. You can try a factory reset, else return your phone for warranty
Click to expand...
Click to collapse
Not a response I expect would found from XDA
I tried factory reset but it's stuck on that screen. Fail to validate image. I think the recovery.img is corrupted?
koflok1234 said:
Not a response I expect would found from XDA
I tried factory reset but it's stuck on that screen. Fail to validate image. I think the recovery.img is corrupted?
Click to expand...
Click to collapse
I doesn't make sense to void warranty to try to fix a problem that is covered under warranty. Maybe your emmc is defective or something like that, don't make matters worse.... You unlock your device when you have verified that everything is working, not when things start failing
I am under warranty but I am currently overseas so sending the phone and process the return is a bit of a hassle. So 'other' options is to do a local repair outside warranty here but that costs a bit.
So if I can fix it myself with a simple procedure then it might be the best way.
I'm having the same issue as well if anyone has figured out how to fix this I would be extremely grateful. I am still under warranty, but I'm nervous they will send me a replacement in worse shape than my current device.
My pure edition was stuck at the splash screen and I didn't previously unlock my bootloader. I also didn't have USB debugging checked so I couldn't find my phone using ADB. Unlocking a pure edition bootloader DOES NOT VOID warranty!!! So I unlocked my bootloader and flashed the factory files and restored the use of my phone. I then updated to lollipop, rooted my phone and checked USB debugging. That way I have full control of my phone and can fix it myself if something comes up. There is the thread saying the warranty won't be void after unlock.
https://forums.motorola.com/posts/677736c888?page=2
The problem now is that it is impossible to root or do anything else with me phone that doesn't involve fastboot
sianaka said:
The problem now is that it is impossible to root or do anything else with me phone that doesn't involve fastboot
Click to expand...
Click to collapse
same here. anybody solved the issue? can we recover through fastboot? anything we can try?
this happend after trying to root the device (step 7 in multi-too to be specific
You should be able to recover via fastboot if you have the factory image, there are some floating around here.
If it's an official one you don't even need to unlock your phone because the image is signed by Moto.
Here is a link to an official guide on how to flash.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
pwvandeursen said:
same here. anybody solved the issue? can we recover through fastboot? anything we can try?
this happend after trying to root the device (step 7 in multi-too to be specific
Click to expand...
Click to collapse
solved.
used fastboot to flash the files from multi-tool (recovery, system boot) booted back up, only pushed root (not TWRP), an d now fully functional again
pwvandeursen said:
solved.
used fastboot to flash the files from multi-tool (recovery, system boot) booted back up, only pushed root (not TWRP), an d now fully functional again
Click to expand...
Click to collapse
Can you possibly explain this step by step? Sorry I'm kind of new to this.
Also, will I be able to do this if my battery is low?
koflok1234 said:
Hi all, total newb here. (Sorry I know you probably hate these kinds of threads).
I apologize in advanced if this is a very simple case / has been discussed in the forums.
I've literally read everything I can in regards to this topic but being such a total newbie at this, I'm still not 100% sure if I got this right.
So basically my phone is XT1095 - which I didn't root or unlock boatlader (simply because I don't know why), that suddenly got into a boot loop.
So on that AP Fastboot screen.
So all options (including normal powerup, recovery and factory reset) produces
'failed to validate system image.
boot up failed'.
What should I do at this point? I've read on jcase's thread that this is a simple matter of "easily fixed by flashing proper boot.img".
Where can I find the "stock boot.img"?
I know graffixnyc has KXE21.187-42 files on his website which can be flashed. Is it pre-rooted though?
Or can I just easily use bhp090808's Multi Tool to fix this?
Can it be used while the phone is still in this bricked / bootlooped condition?
Honestly I dont mind being rooted if it means getting my phone fix. But if I can get it done without rooting it then it would be 'great' since if I fail in any way I won't void my warranty.
Sorry for asking a lot of things. As you can notice, I'm totally new at this. I've successfully rooted and install a custom ROM once in my old S3 but it was only because there was a thorough step to step process.
Again, thanks in advance and I really appreciate anyone's help
Cheers.
Click to expand...
Click to collapse
Well i booted his file, now my device is in a bootloop. i requested the original img file from the motorola site. Search it up in google. I will try it right now. Hope it works!!!
Hi,
I have an unbranded and unlocked nexus 6. I wanted to root and install twrp so I can begin flashing custom roms... Only problem is, I don't have a pc at home to ADB flash twrp, etc.... Is there any method to flash custom rom without having a machine at home? I have absolutely no need for a pc at home, until this precise moment when I get a new phone and I want to start flashing, lol. Im gonna assuming the answer is NO, im thinking there may be some OTG method with files from a thumb drive, but I'll wait to hear from the experts. Thanks in advance.
I have been wondering that very question myself. I really doubt it's possible, but since I have had my N6 and LG G Pad, I don't ever use my antique Pentium 4 Dell PC hardly at all.
Sent from my Nexus 6 using Tapatalk
It's totally possible but highly recommended against. There is an app to root, which then you use flashify to flash recovery but if you ever have a problem, you won't be able to fix it because you need a PC to get a rom back on your phone if you accidentally wipe the os or do some other mischief that prevents you booting, you wont be able.to unlock your bootloader which means you won't be able.to.flash stock or return for warranty purposes either, so as.much as you want to do this, it would really put you in an awful position and you'd be screwed if something goes wrong, which the chances are, it will.
danarama said:
It's totally possible but highly recommended against. There is an app to root, which then you use flashify to flash recovery but if you ever have a problem, you won't be able to fix it because you need a PC to get a rom back on your phone if you accidentally wipe the os or do some other mischief that prevents you booting, you wont be able.to unlock your bootloader which means you won't be able.to.flash stock or return for warranty purposes either, so as.much as you want to do this, it would really put you in an awful position and you'd be screwed if something goes wrong, which the chances are, it will.
Click to expand...
Click to collapse
I have no issues with the first potential problem you mentioned (having to get a rom back on phone using a pc) because I have a backup phone, plus if it gets to that stage, I can use a friends computer if I really need to. But the last comment you made about the chances of an error occurring and saying that it most likely will and i'll be unable to get it back to stock scares me. Is this method really that unreliable? I will read up on it more, and search through the forums.
If you can provide details of the app to root, that would be great. Also, how reliable is the app to root alone by itself? Minus the flashify portion...
nseriessaga said:
I have no issues with the first potential problem you mentioned (having to get a rom back on phone using a pc) because I have a backup phone, plus if it gets to that stage, I can use a friends computer if I really need to. But the last comment you made about the chances of an error occurring and saying that it most likely will and i'll be unable to get it back to stock scares me. Is this method really that unreliable? I will read up on it more, and search through the forums.
If you can provide details of the app to root, that would be great. Also, how reliable is the app to root alone by itself? Minus the flashify portion...
Click to expand...
Click to collapse
It's not the method that's unreliable the app "kingroot" (I believe it is called) works fine. The issues occur with everything and anything else root users do. Flashing a rom, a mod, wiping the os via recovery etc.
Then if anything hardware goes wrong, returning the device for repair under warranty will likely be rejected if its not stock.
danarama said:
It's not the method that's unreliable the app "kingroot" (I believe it is called) works fine. The issues occur with everything and anything else root users do. Flashing a rom, a mod, wiping the os via recovery etc.
Then if anything hardware goes wrong, returning the device for repair under warranty will likely be rejected if its not stock.
Click to expand...
Click to collapse
Gotcha, so maybe I can just root and install apks of apps I really want like adaway, etc... then I should be fine as long as im not using the flash method correct?
nseriessaga said:
Gotcha, so maybe I can just root and install apks of apps I really want like adaway, etc... then I should be fine as long as im not using the flash method correct?
Click to expand...
Click to collapse
I'm not going to commit to an answer there
One thing I will say though, you'll never be able to update with an OTA, so if you're going to root, have a custom recovery,. Allow.oem unlock and have an unlocked bootloader.
Best bet is to do the proper.routing and unlocking using your friends of as a one off. You can then safely.maintain the phone without a pc and use the pc in am emergency. Not unlocking the bootloader from the beginning is.asking.for.trouble
Man I need a new keyboard
danarama said:
I'm not going to commit to an answer there
Click to expand...
Click to collapse
lol I understand.. thx m8
nseriessaga said:
lol I understand.. thx m8
Click to expand...
Click to collapse
Edit above
danarama said:
I'm not going to commit to an answer there
One thing I will say though, you'll never be able to update with an OTA, so if you're going to root, have a custom recovery,. Allow.oem unlock and have an unlocked bootloader.
Best bet is to do the proper.routing and unlocking using your friends of as a one off. You can then safely.maintain the phone without a pc and use the pc in am emergency. Not unlocking the bootloader from the beginning is.asking.for.trouble
Man I need a new keyboard
Click to expand...
Click to collapse
k, I already used the kingroot method and verified using root checker. Installed adaway and everything seems to work perfectly (so far anyway). Uninstalling Kingroot unroots the phone from my quick series of test that I've run so OTA updates doesn't seem like it'll be a problem.
I agree though, if I really want to do any rom flashing, ill just unlock, root, and flash using "proper methods".
Appreciate all your help man.
nseriessaga said:
k, I already used the kingroot method and verified using root checker. Installed adaway and everything seems to work perfectly (so far anyway). Uninstalling Kingroot unroots the phone from my quick series of test that I've run so OTA updates doesn't seem like it'll be a problem.
I agree though, if I really want to do any rom flashing, ill just unlock, root, and flash using "proper methods".
Appreciate all your help man.
Click to expand...
Click to collapse
Uninstalling Kingroot removes root but does not uninstall all modified files. Will show as modified and thus no OTA updates. Another thread on same thing here somewhere. Have to flash system back to stock with PC for any updates.
---------- Post added at 11:13 AM ---------- Previous post was at 11:01 AM ----------
It's also not safe to update without bootloader unlocked anyway. Too many reported bootloops with OTA.
prdog1 said:
Uninstalling Kingroot removes root but does not uninstall all modified files. Will show as modified and thus no OTA updates. Another thread on same thing here somewhere. Have to flash system back to stock with PC for any updates.
---------- Post added at 11:13 AM ---------- Previous post was at 11:01 AM ----------
It's also not safe to update without bootloader unlocked anyway. Too many reported bootloops with OTA.
Click to expand...
Click to collapse
Exactly this. All root methods edit.existing files but do not restore them after unroot. So the system is modified. We're.100% certain there will be no OTA.
Unlock the bootloader and do it properly.
Ok thanks guys. I guess eventually I'll have to get my hands on a PC lol. Thanks again
Even after a year on Android, I'm quite the novice, so please bear with me. So, I rooted my Moto X '14 using CF Autoroot because it was so easy. But, I had no idea how to unroot. So I googled some stuff and I attempted to flash back to total stock rooted rom and recovery. Foolishly, I picked the option to not wipe. So, when it rebooted, it went to the boot screen and crashed.
After trying everything, I realized I had no choice and did an external reset. So, hello 2014 because I'm back on KitKat but still was rooted. After looking around, I realized I can 'unroot' by pressing the option on SuperSU. But, I think all I did was revoke root access because on the bootloader, it still says modified.
I tried to go back to lolipop, but every time I take the OTA, the install crashes, but my phone works fine. So, what I wanna know is how I can go back to stock. Is it easy as flashing as flashing a 5.0 factory image? Or is there more I have to do?
bump
Ownage516 said:
Even after a year on Android, I'm quite the novice, so please bear with me. So, I rooted my Moto X '14 using CF Autoroot because it was so easy. But, I had no idea how to unroot. So I googled some stuff and I attempted to flash back to total stock rooted rom and recovery. Foolishly, I picked the option to not wipe. So, when it rebooted, it went to the boot screen and crashed.
After trying everything, I realized I had no choice and did an external reset. So, hello 2014 because I'm back on KitKat but still was rooted. After looking around, I realized I can 'unroot' by pressing the option on SuperSU. But, I think all I did was revoke root access because on the bootloader, it still says modified.
I tried to go back to lolipop, but every time I take the OTA, the install crashes, but my phone works fine. So, what I wanna know is how I can go back to stock. Is it easy as flashing as flashing a 5.0 factory image? Or is there more I have to do?
Click to expand...
Click to collapse
Just flash system and the root will be gone. Also, if you have other mods like TWRP or different modem the OTA won't install, so in order to get the latest update just flash all the files
Good luck
juliospinoza said:
Just flash system and the root will be gone. Also, if you have other mods like TWRP or different modem the OTA won't install, so in order to get the latest update just flash all the files
Good luck
Click to expand...
Click to collapse
Man, this would've been so helpful a month ago, lol.
Ownage516 said:
Man, this would've been so helpful a month ago, lol.
Click to expand...
Click to collapse
Sorry. Usually I just browse the last 10 questions. And in this post I saw "bump" bit I didn't check that wasn't you who did it LOL.
juliospinoza said:
Sorry. Usually I just browse the last 10 questions. And in this post I saw "bump" bit I didn't check that wasn't you who did it LOL.
Click to expand...
Click to collapse
Haha, it's all good. I just didn't know how that other dude dug this up.