Database Develop

[Q] How do I root developer edition?

I just received my moto x developer version. I must be an idiot because I can't find instructions on how to root it. Every post I can find is about rooting the locked version. People talk about the fact that I don't need an exploit because my boot loader is unlocked. I get that but I don't know how to root. Can someone kindly point me to a tutorial on how to root if my boot loader is already unlocked.

Install a recovery from the dev section. Either TWRP or CWM will be fine.
Then download SuperSU
flash supersu in recovery.

Moto x - Developer edition root
gunnyman said:
Install a recovery from the dev section. Either TWRP or CWM will be fine.
Then download SuperSU
flash supersu in recovery.
Click to expand...
Click to collapse
Thanks! I'll give it a shot. Much appreciated!

There are a few threads... but to elborate on what gunnyman has said... If your bootloader is unlocked, either Dev Edition, or you have a phone from a carrier like T-Mobile or Sprint that allow you to unlock via Moto's web site then its pretty easy to flash alternate recovery, and root from there.
Steps see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP (has links to the files you need too.) and there are threads in the General and Developer sections here too.
Same process works if you have 4.2.2 or 4.4 on your phone.

Is there a way to root the developer edition and keep stock recovery ?
Pete

Flash custom recovery, flash root package in custom recovery, re-flash stock recovery
Sent from my Moto X DE

pasta1234 said:
Is there a way to root the developer edition and keep stock recovery ?
Pete
Click to expand...
Click to collapse
You don't have to flash the custom recovery, just boot into it. Once you have the root .zip on your phone reboot into the bootloader and fastboot boot (recovery) and flash the root zip from there. You will have root and stock recovery.

The reason I'm asking is to retain the ability to recieve OTA updates ?
How does one boot into a custom recovery without loading it?
Pete
3UR0TR45H said:
You don't have to flash the custom recovery, just boot into it. Once you have the root .zip on your phone reboot into the bootloader and fastboot boot (recovery) and flash the root zip from there. You will have root and stock recovery.
Click to expand...
Click to collapse

pasta1234 said:
The reason I'm asking is to retain the ability to recieve OTA updates ?
How does one boot into a custom recovery without loading it?
Pete
Click to expand...
Click to collapse
When you enter the fastboot command, use "boot" instead of "flash" and it will just temporarily boot into the recovery without flashing over the stock partition. You can flash the root zip as normal and when you reboot your phone, the custom recovery will be gone.
As far as receiving OTAs, I'm not sure if you'll get them or not. If you go modifying things like kernel, ROM, or even things like the build.prop, chances are it won't work or will break something. The good thing about having an unlocked bootloader is that it's nearly impossible to hard-brick the device unless you're reckless.

Are you sure this works? When I try 'fastboot boot recovery.img' it gives me a "failed command" error. I kicked off another thread asking how to do this since this is what I typically do with Nexus devices. I know that fastboot now has a -c command that might help but I don't know the magic to put after -c to make it work.
If anyone has been able to 'fastboot boot recovery.img' on a Moto X, please lemme know. This would be my preferred path rather than flashing the custom recovery and then the stock recovery back.
3UR0TR45H said:
When you enter the fastboot command, use "boot" instead of "flash" and it will just temporarily boot into the recovery without flashing over the stock partition. You can flash the root zip as normal and when you reboot your phone, the custom recovery will be gone.
As far as receiving OTAs, I'm not sure if you'll get them or not. If you go modifying things like kernel, ROM, or even things like the build.prop, chances are it won't work or will break something. The good thing about having an unlocked bootloader is that it's nearly impossible to hard-brick the device unless you're reckless.
Click to expand...
Click to collapse

pboggini said:
Are you sure this works? When I try 'fastboot boot recovery.img' it gives me a "failed command" error.
Click to expand...
Click to collapse
What happens when you just type fastboot?
Sent from my XT1060 using Tapatalk

This has been said already but you can just "fastboot flash recovery twrp.img", flash your superuser zip then "fastboot flash recovery recovery.img". You are using the correct image name in the command, correct?

Yes, this was said in the thread I started but then I saw someone suggest what I'd been wanting to do. To answer the questions, if I just type fastboot it gives me the help output like it should, fastboot devices shows my device, fastboot reboot works, fastboot reboot-bootloader works, etc. Essentially, I believe that either there is a command string that I could hand to -c or this just won't work on MotoX's like it does all the Nexus devices that I've played with.
Fortunately I did hit Moto up and they gave me permission to download the 4.4 image so I do have the stock recovery.
Ryno77 said:
This has been said already but you can just "fastboot flash recovery twrp.img", flash your superuser zip then "fastboot flash recovery recovery.img". You are using the correct image name in the command, correct?
Click to expand...
Click to collapse

Fastboot Boot Recovery.IMG not Working after Update

I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben

ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.

nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?

nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?

ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard

Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!

nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.

So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?

neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?

xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?

neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.

nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?

fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem

rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you

jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?

rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.

Unlocked Bootloader, Can't root? [XT1096]

Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...

I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html

There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.

RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.

oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.

So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!

TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.

Oneplus 3T stuck on twrp splash screen

Hey guys so I'm a complete noob when it comes to this sort of stuff but I've been following a guide to root my phone which I can't link here because newbie.
But after trying to boot the phone into recovery mode with "fastboot boot twrp.img" the phone gets stuck on the TWRP splash screen.
I'm kind of stuck here guys and any help would be appreciated, thanks in advance.

stefinho said:
Hey guys so I'm a complete noob when it comes to this sort of stuff but I've been following a guide to root my phone which I can't link here because newbie.
But after trying to boot the phone into recovery mode with "fastboot boot twrp.img" the phone gets stuck on the TWRP splash screen.
I'm kind of stuck here guys and any help would be appreciated, thanks in advance.
Click to expand...
Click to collapse
Just popping in right quick, but your command is wrong.
It should be "fastboot flash recovery recovery.img" (no ") The 2nd recovery in that string is going to be the name of your recovery. If it is twrp.img, then use that. If it is Mondaysux, then it'll be mondaysux.img.

Woody said:
Just popping in right quick, but your command is wrong.
It should be "fastboot flash recovery recovery.img" (no ") The 2nd recovery in that string is going to be the name of your recovery. If it is twrp.img, then use that. If it is Mondaysux, then it'll be mondaysux.img.
Click to expand...
Click to collapse
Yeah I already input that command first as the guide said followed by the command that I stated to boot it, thanks though

What version of TWRP are you using?
I'm assuming you're on OOS 4.0+ and are still encrypted? If so, use the latest unreleased official version.

Anova's Origin said:
What version of TWRP are you using?
I'm assuming you're on OOS 4.0+ and are still encrypted? If so, use the latest unreleased official version.
Click to expand...
Click to collapse
I tried using an older version first as that was the one that the guide linked me to but after it didn't work I found that version you linked myself and tried it but I'm getting the same result

Also, the command to reboot to recovery is "fastboot reboot recovery"
Putting boot into anything is making the fastboot drivers think you are trying to flash a kernel (boot.img)
Edit: Also what root version (specifically) did you use?

Try using fastboot to wipe the recovery partition before flashing twrp again.
The commands are:
fastboot erase recovery
fastboot flash recovery [twrp file name].img
Then reboot to recovery

stefinho said:
Hey guys so I'm a complete noob when it comes to this sort of stuff but I've been following a guide to root my phone which I can't link here because newbie.
But after trying to boot the phone into recovery mode with "fastboot boot twrp.img" the phone gets stuck on the TWRP splash screen.
I'm kind of stuck here guys and any help would be appreciated, thanks in advance.
Click to expand...
Click to collapse
Why not use the volume keys from bootloader to go to recovery
And using system in f2fs format twrp takes time to reach main menu
So I suggest after flashing latest recovery as suggested by other members wait for 5 to 7 minutes

Anova's Origin said:
Try using fastboot to wipe the recovery partition before flashing twrp again.
The commands are:
fastboot erase recovery
fastboot flash recovery [twrp file name].img
Then reboot to recovery
Click to expand...
Click to collapse
Tried that but still getting the same result

How long are you waiting while on the splash screen and how much of the phone's internal storage have you used? As mentioned above, TWRP will take longer to boot while you use the phone's default f2fs storage system. The more space you use on the phone, the longer it takes to boot.

kunal1540 said:
Why not use the volume keys from bootloader to go to recovery
And using system in f2fs format twrp takes time to reach main menu
So I suggest after flashing latest recovery as suggested by other members wait for 5 to 7 minutes
Click to expand...
Click to collapse
Okay so going into recovery with the volume buttons instead actually worked and I feel really dumb, thanks you very much though

TWRP Install Being Rejected??

Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!

Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...

cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.

You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.

Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html

Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".

redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!

Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going