im new to rooting the vivid. whats the easiest way to just root the thing. is there a one click. can someone help me thanks
Not really! You have to unlock bootloader to root. Thats not hard but it is drawn out. There are defined guides and tools to get you there. READ READ READ! Then go slowly and check each step.
I ended up using a pre-rooted OTA ICS ROM and eventually got ROOT. Nothing else would work for some reason.
But your experience may be smoother. Just don't give up! And ask questions politely if you get stuck.
daspazz said:
Not really! You have to unlock bootloader to root. Thats not hard but it is drawn out. There are defined guides and tools to get you there. READ READ READ! Then go slowly and check each step.
I ended up using a pre-rooted OTA ICS ROM and eventually got ROOT. Nothing else would work for some reason.
But your experience may be smoother. Just don't give up! And ask questions politely if you get stuck.
Click to expand...
Click to collapse
May I direct your attention to the following thread http://forum.xda-developers.com/showthread.php?t=1416836 This should have all the answers.
maybe maybe not
lmftmf said:
May I direct your attention to the following thread http://forum.xda-developers.com/showthread.php?t=1416836 This should have all the answers.
Click to expand...
Click to collapse
I was using that and the AIO and Supertool, neither helped me get rooted.
Flashing pirateghost's OTA ICS pre-rooted ROM did it in the end.
But that was what I was referring the OP to look for and read up on.
Can i find the pirateghost rom here?
daspazz said:
I was using that and the AIO and Supertool, neither helped me get rooted.
Flashing pirateghost's OTA ICS pre-rooted ROM did it in the end.
But that was what I was referring the OP to look for and read up on.
Click to expand...
Click to collapse
Unlock Bootloader, Flash WCX-Recovery, and then Root from within recovery
Maxi1984 said:
Can i find the pirateghost rom here?
Click to expand...
Click to collapse
Nope. He departed XDA after incompetent noobs drove him crazy.
Try Googling him.
Related
so i'm swapping my vibrant for a nexus tomorrow. i'm told he never rooted it but i'm assuming he's accepted all of the ota updates. i'm trying read up on everything for this phone. i've been to the wiki at cyanogenmod and have been looking over the forums here obviously as well.
my main question is will i need to be a pc to root it? to unlock the bootloader i know i will need to be but will i absolutely need to do this before i can replace the recovery, radio, etc....?
thanks in advance
damngood98 said:
so i'm swapping my vibrant for a nexus tomorrow. i'm told he never rooted it but i'm assuming he's accepted all of the ota updates. i'm trying read up on everything for this phone. i've been to the wiki at cyanogenmod and have been looking over the forums here obviously as well.
my main question is will i need to be a pc to root it? to unlock the bootloader i know i will need to be but will i absolutely need to do this before i can replace the recovery, radio, etc....?
thanks in advance
Click to expand...
Click to collapse
yes you will
b33zy682 said:
yes you will
Click to expand...
Click to collapse
yeah. thought so. thanks for the confirmation though. oh, and thanks for answering both threads that my dumb ass somehow created. damn kind of ya
Read my signature.
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
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
tamarw said:
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
Click to expand...
Click to collapse
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
kwyrt said:
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
Click to expand...
Click to collapse
thank you Guess I was just searching for the phrase "root."
tamarw said:
thank you Guess I was just searching for the phrase "root."
Click to expand...
Click to collapse
No problem. Happy rooting. And be careful!
Root was achieved on this device by djrbliss before it was even released actually, but we still do not yet have a full XML.zip of fastboot images to restore with, so it is very dangerous to make any significant mods at this stage.
I have been pushing all my sources very hard to find this file, but so far everyone has come up empty.
Until we have it we are all working without a safety net because signed factory images are needed to restore a soft bricked device.
Stick to rooting your phone, for the time being. You can disable bloatware, and customize the hell out of the stock ROM that's already on there. That should be enough to get you through, for the time being. Don't get me wrong, we're all salivating over a real safety net.
Go with a simple root or safestrap it. I bricked my phone using safestrap.
Root for now, wait for fastboot files.
If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.
ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.
From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........
The title explains it all. I got this phone knowing I could root and install CFW, but wanted to just "use" it for a few days in stock. I don't mind stock, I would jsut prefer a custom firmware. I'm having trouble figuring out what I need to do to downgrade to Lollipop so I can flash TWRP and begin using CFW. A simple set of instructions would be very appreciated. Thanks to anyone who can help!
but2002 said:
The title explains it all. I got this phone knowing I could root and install CFW, but wanted to just "use" it for a few days in stock. I don't mind stock, I would jsut prefer a custom firmware. I'm having trouble figuring out what I need to do to downgrade to Lollipop so I can flash TWRP and begin using CFW. A simple set of instructions would be very appreciated. Thanks to anyone who can help!
Click to expand...
Click to collapse
There appear to be guides here for doing those things with 6.0 installed, such as MicroMod777's guides.
After a few more hours of digging, I figured it out. I may draw up a cleanly laid out guide referencing the posts that helped me for people in the position I was.
Thank you!
No, you don't need to downgrade, just go ahead and install TWRP & CFW.
Careful with downgrading, becuz H811 has Q-Fuse enabled, if you mess up you'll end up with a 9008 hard brick
im having a similar issue im trying to root/unlock 20p and its not finding any device in fastboot it just sits there saying locating any device and never locates anything adb see's the phone just fine anyone know anything about that? thanks for the help in advance
Rooting stock G4H811 already on 20p?
but2002 said:
After a few more hours of digging, I figured it out. I may draw up a cleanly laid out guide referencing the posts that helped me for people in the position I was.
Thank you!
Click to expand...
Click to collapse
Yea, I'm trying to root my new updated G4 that's on 20p. I have one that's soft bricked already that I'm trying to fix and don't wish to brick another.
Can someone point me in the right direction?
Thanks
Im in the same boat. No devices found after fastboot. Any advice?