Related
New MotoX from sprint.
android version 4.2.2
baseband msm8960pro_bp_2323.020.90.00r
kernel 3.4.42.-xline.
system version 139.14.1
build 13.9.0q2.x-116-mx-17-57-1
i did a fair amount of searching but could not find the proper instructions for obtaining root access for the moto x. Need root access or this device would be a deal breaker.
Can someone point me to a link? I would be much appreciated. Thanks Listers!!!
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
I did search the web and the forums; I'm sorry. it was a long day, i had just purchased the phone and wanted to make sure i didn't brick it. I have rooted/jailbroken several other devices but wanted to know if the latest ota update would cause a problem for that.
Again, I'm sorry for for the excess forum baggage.
I'll try again.
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
moises1204 said:
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
Click to expand...
Click to collapse
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
bullpen7979 said:
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
Click to expand...
Click to collapse
ownmoto or whatever?? um... ok... I can tell you haven't browsed the different sections for the Moto X here or you would have seen in the "Moto X Original Android Development" section that its called "PwnMyMoto"
Brokenwall gave you a way to root your sprint device, no matter what stock rom you're running... OTA updates or not. Granted unlocking your bootloader voids your warranty... and he didn't give you a 100% newbie step by step guide which it now seems you were really looking for.
Also in the Moto X Original Android Development is a thread titiled... "[Root] RockMyMoto (Yes, even the first OTA)" which is pretty obvious as to what it is for. If you took a few minutes to read it, you'd know it is what you want if you don't want to unlock your bootloader. Its not a very long thead (141 posts currently) so it wont take long to read. The original post contains everything you need, except how to make sure you have Telnet as part of your Windows install (there are posts in that thread later that say what to do to enable/install Telnet as a Windows Feature inside Add/Remove Programs).
Sorry, if I come across as harsh. I know you just want to root without screwing up your phone, and I get that. But I'm afraid if you haven't been able to look around and find this stuff, you'll likely not be able to properly follow and understand the instructions and will therefore stand a good chance of messing up your phone!!!
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Again, I'm sorry for being stuck here and having to ask the question. I would greatly appreciate the assistance of someone who can speak to my specific situation.
Thank you and regards to those who can help.
Bull
bullpen7979 said:
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
Click to expand...
Click to collapse
The steps taken in the video are exactly explained in the post.
There are a few assumptions.. 1. Your PC has telnet on it, or you know how to install it. (there is a link further in that thread which Windows users can follow. 2. You have ADB Driver and Platform tools from the AndroidSDK installed correctly on your PC, and Moto drivers installed. Again, there are threads on this already, so you'll have to find/follow them.
You could also try to follow this post -> http://forum.xda-developers.com/showthread.php?p=47067076 however, it uses puttytel.exe instead of Telnet so it will look a little different. It too assumes you've properly installed ADB Driver and Platform Toos from the Android SDK along with the Moto drivers.
Another option is the "Tool Kit" -> http://forum.xda-developers.com/showthread.php?t=2477132 which is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. Only thing would be if you want to use "Flash back to stock" you need to download the ROM file separately.
bullpen7979 said:
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Click to expand...
Click to collapse
Right now, there is the rom the phone shipped with. If you have that, you use PwnMyMoto process to root it. The "camera update" that was pushed over the air. If you have that, you use RockMyMoto. And as of yesterday, if you have Verizon X, there is KitKat which can not be rooted (unless your carrier allows you to unlock your phone's boot loader)
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. Bummed. I just want my device rooted so I can send my daughter the one I promised here.
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. I'd even accept remote assistance via logmein. Pretty bummed. I just want my device rooted so I can send my daughter the one I promised her.
I have no idea why this process has been so difficult this time around. I have rooted, downloaded & installed custom roms, etc.
http://forum.xda-developers.com/showthread.php?t=2536200
Please help. I am out of ideas.
jayboyyyy said:
http://forum.xda-developers.com/showthread.php?t=2536200
Click to expand...
Click to collapse
Isn't this just for the verizon model?
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
I have to believe it can be done, I'm just not getting it for some reason.
I'm really sorry, as I have said in multiple posts. Like I said, I would paypal you a reasonable sum if one of the more experienced people out there want to remote in via logmein and help. I know that sounds lame. I'm normally a guy who likes to research it all himself and do this.
I'm normally the guy who helps other people with this stuff, but I just can't hash this out. I've spent the last three days of my free time reading, researching, trying to get the thing to connect as a drive so I can push files to it and run them via adb.. Even went so far as considering buying a wireless adapter to put the files there wirelessly. I'd try now but I'm exhausted. If you can help, please PM me and we can work out something if you are willing. Thanks to those who have suggested methods. I do appreciate your help. I have tried them all except the last kit kat method which I thought was just for Verizon. I'm with sprint. As tired as I am, I'm afraid to brick the thing. I'm very close to asking for a method to restore the phone and take it back. I really wanted wireless tether. I need it for work and to run the ipad on occasion. Sorry this was a long post/thread.
Sorry I'm not as quick as the rest of you. Just want a rooted phone and can't seem to get it done this time on my own.
Any suggestions?
bullpen7979 said:
Isn't this just for the verizon model?
Click to expand...
Click to collapse
No. That will work for any Moto X Developer Edition or Carrier edition with an unlocked boot loader. So T-Mobile, Sprint, etc.. If you can unlock your boot loader via -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth then you can root via this process.
bullpen7979 said:
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
Click to expand...
Click to collapse
To get your phone to show up in windows as Drive Letter, needs USB Mass Storage mode. Ok, You've installed an app for that, fine... but 1. I'm not aware of that app working, and more importantly, 2. I am not aware of any root method in these forums that requires your phone to show as a "drive letter" to work. So I couldn't even begin to suggest what you are doing wrong.
What instructions are you actually trying to follow? Why not post questions on it in that particular thread, including exact details of what you've done, what you see on your phone, any/all errors or messages, etc.???
And if what you really want to do is tether with sprint, I hope you have checked out threads with suggestions on hacks/ways that work to tether on Sprint Moto X before you worry about rooting.
For example, if you want to remain non-rooted, FoxFi could possibly be an option. As I am a Verizon user and haven't used it, I can't say how well it works for Spint, and I can't say how well it works for Verizon, just that Verizon KK users say it doesn't work, but it did with the JB/4.2.2 roms..
KidJoe;
Thanks for your patience. I'm sorry about all of this. I have tried to be as clear as I can be, but I will redouble my efforts. Let me read clearly that last link and I will post back. I do want root access for all the other cool things it enables too, so I'm determined to get it right. I just want to be careful not to miss something and turn a decent phone into a paperweight.
That link you referenced is exactly what I used to unlock. When I reboot the phone, I get a white screen with a red exclamation point that says bootloader unlocked.
Fox Fi is a no go
Update. Just tried Foxfi. Does not work with current status of unlock but not rooted. I need root, but how does one copy files to the device via usb? I remember there being a setting.
I opened a new thread on this subject. http://forum.xda-developers.com/showthread.php?p=47740046#post47740046
Hope that's not against the rules. I really thing the failure is related to my inability (or ignorance of how to ) push files to the device.
Good gravy. This has eaten up WAY too much time.
Apparently its a mixed bag over at sprint. Some can some can't.
http://www.sprintusers.com/forum/showthread.php?t=234246
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the green square before the thread title. I know it's long but you really should read through the whole thread to get a feel for what people have been doing wrong, etc. For example, you NEED to flash it with Moto's fastboot.exe (often called mfastboot but it's not actually called that when you download it from Moto).
The guide you are referring to seems fine, except the mfastboot command assumes you changed the name of the Moto fastboot executable to mfastboot...
I don't mean to be one of those trolls around here but if the guide seems too complicated, I would encourage you to wait for Moto to release the SBF files for 4.4.2 before rooting. I say this because, without those files, things could get tricky of you're not an expert (I'm not) and you do something wrong. When those files come out, you can follow the simple guide on the Moto site for returning your phone completely to factory specs, should you mess up /system or something.
I'm actually doing what I'm recommending to you. I'm confident I wouldn't mess things up but on the other hand this is my only phone, I'm too poor to replace it, and I'm living abroad so sending it back would be tricky.
[EDIT]: By SBF I mean either the real SBF or the package you can download from the Motorola "return to factory" page. I'm not actually sure if they are the same thing or not as I haven't downloaded. But you don't need RSDLite for them...
droib said:
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the [...]
Click to expand...
Click to collapse
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
TheSaw said:
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
Click to expand...
Click to collapse
Given your experience I don't think there is any real chance of phone death by following those instructions. The issue is, as you say, backup, or what happens AFTER you successfully root. Motorola's SBF files are everything your phone needs to go back to stock, and 4.4.2 is not available yet. So for example if you were on 4.4 and you corrupted something important like your partition table, you could just go to Motorola's website, request the files for 4.4 and flash them all using fastboot (mfastboot as they say here) to get back to a pristine phone. Right now, you can make a recovery backup of /system, etc. right after rooting which SHOULD be fine for correcting OS tinkering errors, but you never know... People have posted on the possibility of flashing, for example, the 4.4 recovery.img on top of 4.4.2 in order get future OTAs, etc, but this sort of thing is very risky. Maybe it works or maybe you hard-brick.
This guide will work on 4.4.2 and has all the files you need to download. If you're already unlocked you can skip those steps of course
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
It doesn't tell you how to root, but when you exit TWRP it will ask "would you like to install supersu?" so select yes. Once you're in Android go to Google play and download supersu from the market. Open it and it will ask if you want to install binaries. Select yes and the twrp/cwm option. Your phone will reboot then you're done
This still works to root if your bootloader is already unlocked -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Now there is a newer version of SuperSU. See this thread -> http://forum.xda-developers.com/showthread.php?t=1538053 and use the link for the CWM / TWRP / MobileODIN installable ZIP.
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
Follow these instructions with clickable links to TWRP and SuperSU
Step-By-Step Instructions for Unlocking and Rooting a Moto X Dev Ed
works for both 4.4 and 4.4.2.
Okay, I have rooted my phone. I've read several articles on the subject, and this is the easiest method I've found to do it:
Cozume said:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
Click to expand...
Click to collapse
After you downloaded the files needed for this from here (make sure they're not outdated, if you're reading this somewhere in the future), you can just follow these steps for a quick root access. UNLOCKED BOOTLOADER ONLY.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk
shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?
I can recommend the NTRT, the Nexus Telepathic Rooting Tools.
OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.
we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk
shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>
simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.
Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.
Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!
1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.
I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period
I downloaded the wugfresh tool to try and unlock and root my Nexus 6 used on Verizon but obtained from the Google Play store.
Wugfresh recognizes the device. I have enabled debugging and developer options and have the phone properly set up with the original cable.
When I open wugfresh and after I download the appropriate files, I click on unlock phone and a pop up just says ENCRYPTED.
I tried googling as well as searching this forum and I cannot figure out how to remove encryption without the phone already having been unlocked and reverted back to Lollipop.
Can someone give me a hand? I'm unsure of what to do next.
Thanks!
ghostofdavid said:
I downloaded the wugfresh tool to try and unlock and root my Nexus 6 used on Verizon but obtained from the Google Play store.
Wugfresh recognizes the device. I have enabled debugging and developer options and have the phone properly set up with the original cable.
When I open wugfresh and after I download the appropriate files, I click on unlock phone and a pop up just says ENCRYPTED.
I tried googling as well as searching this forum and I cannot figure out how to remove encryption without the phone already having been unlocked and reverted back to Lollipop.
Can someone give me a hand? I'm unsure of what to do next.
Thanks!
Click to expand...
Click to collapse
All the info you need is in the stickies. Many will tell you not to bother with tool kits. This is due to that you wont know how to fix any issues that may come up. It is always best to learn what you are doing. All you re.ally have to do to un-encrypt is to completely wipe the device. Then you need a kernel that doesnt force the encryption
I checked this sticky - http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Q17: What is encryption and should I disable it?
"First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out."
I clicked that link and ended up at http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
It appears that this would work if my phone was unlocked, but it isn't. I don't yet understand how I can flash anything if my phone is still locked and I don't know how to unlock the phone if the device is still encrypted.
I'm still stuck!
ghostofdavid said:
I checked this sticky - http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Q17: What is encryption and should I disable it?
"First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out."
I clicked that link and ended up at http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
It appears that this would work if my phone was unlocked, but it isn't. I don't yet understand how I can flash anything if my phone is still locked and I don't know how to unlock the phone if the device is still encrypted.
I'm still stuck!
Click to expand...
Click to collapse
Read the stickies on unlocking your phone manually first.
Be careful that some of the stickies and or threads on rooting ect are old. Before you blindly follow instructions check the date and the version its meant for. If its more then a month or so old, or states a different version of android proceed with causion. Also, make sure you read the last maybe 4 or so pages of the threads if not more, as if the instructions ARE out of date you will see people note it there, and either suggest what changes are necessary or point to newer guides.
You really will help yourself out A LOT to learn the little bit it takes to do it manually. Multiple threads every day from people who have one little thing go wrong with the toolkits, that would be REALLY easy to fix if they knew what they were doing.
First read up on how to unlock, its really really easy... Once your unlocked STAY UNLOCKED, and make sure you keep "allow OEM unlock" on... Do those two things and you can almost definitely fix your phone no matter what you mess up.
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...