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.
Related
Hello all. Ordered my Verizon Moto x Dev Edition during the painful cyber monday sale. I've been lurking around and reading up on what needs to be done. I have a basic idea of the process. Just making sure it is correct.
So to begin i need to unlock the bootloader, which is done through the motorola website here
https://motorola-global-portal.cust...2LzEvdGltZS8xMzg2MDc1NzQwL3NpZC9KcTFvblVHbA==
Before or after i unlock the bootloader i will ota update to 4.4, so i will be following this guide to achieve root
http://forum.xda-developers.com/showthread.php?t=2536200
This is quoted from the above thread
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
I assume for step 3, I just place the mfastboot.exe in my android sdk platform-tools folder. This is what i really need clarification on. The rest is pretty self explanatory.
After all that i have read and seen the bootloader unlocked screen, looks pretty ugly. So i plan on replacing that also, following this post
http://forum.xda-developers.com/showthread.php?t=2417961
That is a informative thread, but it is a little hazy on what format and what needs to be done to flash a replacement image on a dev edition. Maybe someone could enlighten me more.
I'm sure this is all pretty easy to do once i have the phone to tinker with, I am just preparing myself in advance. I would greatly appreciate some help and tips if one could provide.
Thank you
just run the mfastboot in the same directory as TWRP. Your platform tools folder will work fine. When you open the command window just type mfastboot instead of fastboot.
For the image it needs to be a .bin which it should already be. Place it in the same folder as fastboot, Then fastboot flash logo (logofile).bin
Like you said it is all pretty explanitory. Much easier than attempting to root the locked versions.
Awesome. Thanks so much for the help. Greatly appreciated!
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
Root away friend.
Sent from my Moto X DE
I thought all you had to do was flash TWRP, and then when rebooting from recovery TWRP would say something like "your device does not appear to be rooted, would you like to root it now?".
Also I thought devices shipping now already have 4.4 on them, but maybe that was bad info.
I know that was true on 4.2.2, didn't check it on 4.4. Just flashed the latest SSU zip and rooted that way.
Sent from my Moto X DE
I am in the same boat as the OP. I was wondering where do you get the mfastboot.exe from to place in your platform tools folder? I am not a noob to fastboot as I have had nexus devices but the mfastboot is new to me. Thanks in advance!
Travisdroidx2 said:
I am in the same boat as the OP. I was wondering where do you get the mfastboot.exe from to place in your platform tools folder? I am not a noob to fastboot as I have had nexus devices but the mfastboot is new to me. Thanks in advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1138092
Got my Moto X DE a few hours ago. Unlocked and rooted
Also got native tethering working. I used the method in this post
http://forum.xda-developers.com/showthread.php?t=2536166&page=4
Used the pre-built exe provided by <:GeeK:> at post #35. Worked like a charm.
I can see why there are not many custom roms, because this phone is great. All you really need is unlock and root and everything is good. That being said........i feel the withdrawls already from find and flashing new roms....
now to research what verizon bloatware i can remove.....
Does anyone know what bloatware is safe to remove. Is there a list somewhere, i seem to not be having any luck finding the proper information about this.
Edit
Also wonder about gravityBox for 4.4. anyone use this on their moto x?
Thanks
Installed xposed and gravitybox. WOW! Its amazing. My need for flashing Roms is satisfied.....for now. This phone rocks.
Still looking for information on bloatware removal.
Edit*****
Was able to rid my device of vzw tones, navigator and something else. Had no luck finding the vzw voicemail apk to delete it, just disabled it in app manger.
Sent from my XT1060 using Xparent Skyblue Tapatalk 2
I've had the phone since launch and have been waiting for a root method to surface that does not require rolling back to 4.2.2. Would something like this be possible?
Sorry if this has been asked before. Thank you
EDIT: VZW Dev edition
Bg8780 said:
I've had the phone since launch and have been waiting for a root method to surface that does not require rolling back to 4.2.2. Would something like this be possible?
Sorry if this has been asked before. Thank you
EDIT: VZW Dev edition
Click to expand...
Click to collapse
You have a Dev edition phone just unlock the bootloader.
Wow....
murso74 said:
Wow....
Click to expand...
Click to collapse
Sorry, I realize this is probably a dumb question but I've been really busy in the past couple years and have been out of the root game for awhile. A lot has changed since my OG Droid days.
You have a DEV EDITION. unlock the BOOTLOADER and root it.
Plain and simple.
Sent from my XT1053 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2603358
All you need to know.
I thought this was the easiest guide and it includes the files you need http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
After you unlock follow the steps to install TWRP. When you reboot you'll be rooted.
Thanks everyone! Like I said before sorry for the stupid question I finally have the time to get back into the rooting stuff. Unlocked the bootloader via Moto's site and it bricked my phone lol. Pretty ironic the one time I brick a device is going the OEM's route to unlock. So learned a lot unbricking it. All rooted now and back to stock recovery. Thanks for the replies and resources. ☺
@Bg8780
The link supplied by @Restola is a very complete and newbie friendly set of instructions, including directing you to Moto's web site to obtain the unique unlock code needed for your phone. The included mfastboot is a little older, as are the Moto Device Drivers, and ADB. Consider viewing -> http://mark.cdmaforums.com/ADB.htm to get them.
And a TIP if you use the instruction's Method B of booting into fastboot/booloader mode, you need to make sure your phone is not plugged into anything until after you see the Fastboot AP screen on your phone.
Additionally, after completing the install of TWRP, it doesn't have you reboot into it (NEEDED!!), and actually rooting (via installing SuperSU or having TWRP itself root you).
You can also use the thread @KJ linked, it has two has 2 sections you need to expand... "How To Unlock Your Bootloader" which talks to you about what is needed and getting the code from Moto's web site, and "Rooting Unlocked Bootloader" which talks you through the process to root. It contains LINKS of up to date files that will work with 4.4 and 4.4.2. However the TWRP from -> http://techerrata.com/browse/twrp2/ghost came out after those instructions were posted.
EDIT: Never mind, I see you're already done... I'll just leave this here anyway in case someone else comes a long...
KidJoe said:
@Bg8780
The link supplied by @Restola is a very complete and newbie friendly set of instructions, including directing you to Moto's web site to obtain the unique unlock code needed for your phone. The included mfastboot is a little older, as are the Moto Device Drivers, and ADB. Consider viewing -> http://mark.cdmaforums.com/ADB.htm to get them.
And a TIP if you use the instruction's Method B of booting into fastboot/booloader mode, you need to make sure your phone is not plugged into anything until after you see the Fastboot AP screen on your phone.
Additionally, after completing the install of TWRP, it doesn't have you reboot into it (NEEDED!!), and actually rooting (via installing SuperSU or having TWRP itself root you).
You can also use the thread @KJ linked, it has two has 2 sections you need to expand... "How To Unlock Your Bootloader" which talks to you about what is needed and getting the code from Moto's web site, and "Rooting Unlocked Bootloader" which talks you through the process to root. It contains LINKS of up to date files that will work with 4.4 and 4.4.2. However the TWRP from -> http://techerrata.com/browse/twrp2/ghost came out after those instructions were posted.
EDIT: Never mind, I see you're already done... I'll just leave this here anyway in case someone else comes a long...
Click to expand...
Click to collapse
Yep all done now but thanks KidJoe, your comment doesn't go unappreciated.
[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
mateopase said:
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
Click to expand...
Click to collapse
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
IINexusII said:
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
Click to expand...
Click to collapse
Awesome, thanks. Looks like that's what I'll end up doing. I really messed up my phone though when trying to get back to stock. Hopefully my stock image request will be approved soon and I'll be able to go through the process again.
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
mateopase said:
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
Click to expand...
Click to collapse
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
crpalmer said:
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
Click to expand...
Click to collapse
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
mateopase said:
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
Click to expand...
Click to collapse
Honestly, I haven't looked at what options are available for images to flash.
When I asked for firmware, I believe that I asked on a Friday evening and received access on the following Monday morning. So maybe you'll get access in another 15-16 hours? That is your safest bet if your phone is working well enough to last you until then.
I have never done an OTA update as when I first got into Android I was flashing ROMs nearly every week and never waited for updates just flashed a new ROM, however when I got my Nexus 6 I decided to just root and stick with stock.
I woke this morning and the 5.1 update was available but when I download it and select install and reboot it boots into recovery (TWRP) and I can't see where the download is - I presume I am having to flash it myself? So I have to reboot and it says I am up-to-date with 5.0.1 and then an hour later the download is available again and I go through the same process.
Can anyone help, tell me where i am going wrong.
I had same issue after relocking bootloader and this worked for me and hopefully it may work for you. Put phone in fastboot mode.(hold power + volume down) then use fastboot command fastboot -w
How do you define stock if you have TWRP. LOL
Sent from my Nexus 6
DebianDog said:
How do you define stock if you have TWRP. LOL
Sent from my Nexus 6
Click to expand...
Click to collapse
Well OK stock except for the recovery. I presumed you would know what I meant. I will ensure my posts are word prefect next time.
md1008 said:
I had same issue after relocking bootloader and this worked for me and hopefully it may work for you. Put phone in fastboot mode.(hold power + volume down) then use fastboot command fastboot -w
Click to expand...
Click to collapse
Thanks I'll give it a go
Same issue here. Let us know how you make out.
Hate to do a "me too" post, but I've had the exact same experience.
I'll wait to see whether the fastboot -w method works before I do anything else.
I did try to find the (410.4Mb) download on my N6, but I suspect that the failed update must have deleted it, as it's asking me to download it again.
fastboot -w just wiped userdata so needed to do a fresh install and was still at 5.0.1. So just had to install my backup again to get back to where I was this morning.
Ouch! Sorry to hear it (though glad that you had a backup) - thanks for saving the rest of us from trying that particular route.
I'm still looking for a way to get to 5.1.
You can't do an OTA update with a NON-STOCK recovery.
You can however, if your bootloader is unlocked, download the factory image, extract it, and flash the system.img, bootloader.img, radio.img, cache.img etc...use fastboot to flash those.
Or you can fastboot flash the stock recovery, and take the OTA again.
Thanks.
I assume that I can also use Nexus Root Toolkit to "Flash Stock + Unroot" (without wiping the device), then take the OTA update to 5.1, and then use NRT to Root again?
Just doing a full backup at the moment before I start playing!
UPDATE: The above worked fine.
I started with 5.0.1, rooted, unlocked Bootloader
Then, in Nexus Root Toolkit, I used:
1) Backup (using Create Nandroid Backup w/Custom Recovery option)
2) Flash Stock + Unroot (using No Wipe Mode. I also had to enable Force Flash Mode)
Then, on the phone, accept the OTA 5.1 update, which downloaded and installed first time.
Back to NRT, and:
3) Root and also flash Custom Recovery
I ended up with 5.1, rooted, unlocked Bootloader (and all my apps and data were untouched).
Since doing the method recommended in the second post the OTA update hasn't been available on my device?
Have you tried rebooting the phone?
Or going into Settings > About Phone > System Updates > Check for Updates
It's always possible (if unlikely) that Google have stopped the roll-out to fix some of the issues that people have been reporting with SmartLock, etc?
Philip said:
Have you tried rebooting the phone?
Or going into Settings > About Phone > System Updates > Check for Updates
It's always possible (if unlikely) that Google have stopped the roll-out to fix some of the issues that people have been reporting with SmartLock, etc?
Click to expand...
Click to collapse
yes and yes done that too
Philip said:
UPDATE: The above worked fine.
I started with 5.0.1, rooted, unlocked Bootloader
Then, in Nexus Root Toolkit, I used:
1) Backup (using Create Nandroid Backup w/Custom Recovery option)
2) Flash Stock + Unroot (using No Wipe Mode. I also had to enable Force Flash Mode)
Then, on the phone, accept the OTA 5.1 update, which downloaded and installed first time.
Back to NRT, and:
3) Root and also flash Custom Recovery
I ended up with 5.1, rooted, unlocked Bootloader (and all my apps and data were untouched).
Click to expand...
Click to collapse
Why did you take the scenic route? This is by far the longest method to do that.
Instead of flashing stock with nrt, why not just flash stock normally? That way you could have just flashed 5.1 without having to take any OTA...
And further, if you wanted to keep recovery, why not just flash the system and boot image keeping everything else as it is? Then just flash SuperSU from twrp?
2 commands
fastboot flash system system.img
fastboot flash boot boot.img
Boot into recovery and flash root.
Much quicker than the method you used.
rootSU said:
Why did you take the scenic route? This is by far the longest method to do that.
Click to expand...
Click to collapse
Well, my fist step was a backup, which you conveniently left out - you may be happy to update your phone without backing it up first, but I chose not to take that chance.
Apart from that, it's about the same number of steps - I was happy to take 5.1 OTA (which meant that I was certain that it was the correct version for my phone), and Nexus Root Toolkit is a much nicer piece of software to use than fastboot. I know that some people don't like NRT because they feel that it demystifies the black arts of updating and it threatens their voodoo status, but I find it an excellent piece of software and recommend it to you.
In the meantime, while you had to go and find the appropriate system.img and the appropriate boot.img and download them before fastbooting them, these were steps that I was able to avoid whilst enjoying my "scenic" journey.
So you take the high road and I'll take the low road - but I reckon that it took me no longer to update my phone than it took you to update yours!
Philip said:
Well, my fist step was a backup, which you conveniently left out - you may be happy to update your phone without backing it up first, but I chose not to take that chance.
Apart from that, it's about the same number of steps - I was happy to take 5.1 OTA (which meant that I was certain that it was the correct version for my phone), and Nexus Root Toolkit is a much nicer piece of software to use than fastboot. I know that some people don't like NRT because they feel that it demystifies the black arts of updating and it threatens their voodoo status, but I find it an excellent piece of software and recommend it to you.
In the meantime, while you had to go and find the appropriate system.img and the appropriate boot.img and download them before fastbooting them, these were steps that I was able to avoid whilst enjoying my "scenic" journey.
So you take the high road and I'll take the low road - but I reckon that it took me no longer to update my phone than it took you to update yours!
Click to expand...
Click to collapse
It took you loads longer haha.
rootSU said:
It took you loads longer haha.
Click to expand...
Click to collapse
And that bothered you so much that you had to tell the whole world about it? Wow!
Philip said:
And that bothered you so much that you had to tell the whole world about it? Wow!
Click to expand...
Click to collapse
To be honest no. The route you took was so long that I thought you just didn't have a clue about what you were doing so I thought I'd help out and let you know the quicker version... And if anyone reads your post and thinks its the best way to do it, well now they have some contrast.
What bothers me is your attitude however. But I don't care enough to get into an argument with people who would rather waste their time and the people they try to help than listen to constructive criticism.
But yeah, your way is needlessly long so I hope people don't take your lead.
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...