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.

[Q] Hboot 1.57 OS 5.11.401.10 reboot loop

Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf

Agil1ty said:
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Click to expand...
Click to collapse
Flash the stock firmware 5.11.401.10! I think your firmware is mismatched.

By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app

Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Flashing the firmware might fix the boot-loop, since you flashed the stock rom! If it does stop the boot-loops, you can re-install TWRP or CWM to get the custom recovery.

Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.

Seanie280672 said:
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Click to expand...
Click to collapse
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD).
The thing is it isn't a normal bootloop (which normally would come with the HTC logo all the time)
It reboots when I try to setup the phone (in the setup menu). Restoring the phone with the link in the OP, ive recoverd my phone, but I would still love to use custom roms again.

Agil1ty said:
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD)
Click to expand...
Click to collapse
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.

Seanie280672 said:
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Click to expand...
Click to collapse
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?

Agil1ty said:
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Click to expand...
Click to collapse
no it doesn't wipe anything, but you can use xposed and its tweaks on stock rom, you just need to root first, just install TWRP, enter recovery and again upon exit it will offer to root stock rom for you.

[Q] ADB wont work in recovery after latest ota

Hi,
I've just done an OTA update to 6.09.401.5
My phone is 801n, S-OFF with locked bl. Hboot is 1.57.
After the OTA I had lost root, so I went on to recovery (stock) to sideload supersu.
Much to my surprise, I can't adb with the stock recovery.
Looking in device manager, it just shows up as mass storage device.
I've added the device ID to the google driver inf:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
and forced the driver, which loaded fine. But adb devices still shows nothing.
Same thing when I force ADB Composite Device.
Also tried disabling and enabling USB debugging without any success.
Do you guys have a similar issue? Are your device ids the same as mine in recovery? ADB works?

Nemesis_00 said:
Hi,
I've just done an OTA update to 6.09.401.5
My phone is 801n, S-OFF with locked bl. Hboot is 1.57.
After the OTA I had lost root, so I went on to recovery (stock) to sideload supersu.
Much to my surprise, I can't adb with the stock recovery.
Looking in device manager, it just shows up as mass storage device.
I've added the device ID to the google driver inf:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
and forced the driver, which loaded fine. But adb devices still shows nothing.
Same thing when I force ADB Composite Device.
Also tried disabling and enabling USB debugging without any success.
Do you guys have a similar issue? Are your device ids the same as mine in recovery? ADB works?
Click to expand...
Click to collapse
You can not sideload with stock recovery nor use adb commands. flash a custom recovery

alray said:
You can not sideload with stock recovery nor use adb commands. flash a custom recovery
Click to expand...
Click to collapse
That seems strange. It was a while ago, but i did root my 4.4.2 install somehow with the bootloader remaining locked (I didnt erase my phone), and keeping stock recovery. Since the BL is locked I probably didnt flash a custom recovery and then revert to stock.
I was pretty sure I just sideloaded it with stock recovery since my device is SOFF.
Are you certain it can't be done?
It's pretty stupid of me then, as I am not sure how I rooted it before then.

Nemesis_00 said:
That seems strange. It was a while ago, but i did root my 4.4.2 install somehow with the bootloader remaining locked (I didnt erase my phone), and keeping stock recovery. Since the BL is locked I probably didnt flash a custom recovery and then revert to stock.
I was pretty sure I just sideloaded it with stock recovery since my device is SOFF.
Are you certain it can't be done?
It's pretty stupid of me then, as I am not sure how I rooted it before then.
Click to expand...
Click to collapse
you can not use adb sideload with stock recovery.
if you don't want to wipe the phone by unlocking the bootloader using htcdev.com you can:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
do wait said above and then unlock bootloader from custom recovery using adb shell or guru bootloader reset tool.

alray said:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
unlock the bootloader with the s-off method and flash a custom recovery.
Click to expand...
Click to collapse
is masking firmware works ?
If this works then no one need htcdev I think it's not possible or can brick
For totally stock locked S On phone I take a same version firmware mix TWRP flashing you don't need htcdev or unlocked ?
How I can unlock with S Off & stock Recovery non root ?

yatindroid said:
is masking firmware works ?
Click to expand...
Click to collapse
with s-off you can flash a custom recovery with a locked bootloader, no risk. just pack the custom recovery image (renamed recovery.img) with an android-info.txt that match your phone info inside a firmware.zip file and flash it in ruu mode.
you can then use the guru bootloader reset tool to unlock your bootloader using the custom recovery or by using an adb shell from custom recovery
If this works then no one need htcdev I think it's not possible or can brick
Click to expand...
Click to collapse
This is not a magical way to unlock, you first need s-off. if the phone is s-on then htcdev is required.
For totally stock locked S On phone I take a same version firmware mix TWRP flashing you don't need htcdev or unlocked ?
Click to expand...
Click to collapse
will only work for s-off, you can not flash a firmware with twrp inside, you can only flash sigend firmware with s-on
How I can unlock with S Off & stock Recovery non root ?
Click to expand...
Click to collapse
you can't, you first need to flash custom recovery using a masked firmware.zip like said above or use htcdev. using the firmware method will not wipe the phone.

alray said:
you can not use adb sideload with stock recovery.
if you don't want to wipe the phone by unlocking the bootloader using htcdev.com you can:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
do wait said above and then unlock bootloader from custom recovery using adb shell or guru bootloader reset tool.
Click to expand...
Click to collapse
Well, im an idiot. That's probably what I did last time as well.
For some reason I remembered using sideload.
Flashed TWRP, installed SuperSU and back to stock recovery.
Thanks a bunch,

what happens if you upgrade a rooted htc one t lollipop

so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx

monrokhoury said:
so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx
Click to expand...
Click to collapse
An OTA update will not work on a rooted phone! For the OTA to work it needs stock recovery, stock rom and all of the files that it is attempting to update. If anything is missing then it will error out and return to your present setup.

and to complete what majmoz already said, if your rom is 100% stock, and you have flashed back your stock recovery, the phone will update fine but you will loose root. You'll need to flash a custom recovery after the OTA to re-root the rom.

Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery? how to do that? and will the current rooting method work on lollipop (and should i follow the same steps to install clockwork recovery)? Will the ota update relock the bootloader?
i'm sorry if i'm asking too many questions but i don't trust any other forum.

monrokhoury said:
Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery?
Click to expand...
Click to collapse
If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
how to do that?
Click to expand...
Click to collapse
The same way you did to flash a custom recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
and will the current rooting method work on lollipop
Click to expand...
Click to collapse
Flash the latest supersu from a custom recovery. Version 2.37 and above should work on lollipop
and should i follow the same steps to install clockwork recovery
Click to expand...
Click to collapse
You always flash the recovery using the same commands, stock or custom, on all versions its always:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
Will the ota update relock the bootloader?
Click to expand...
Click to collapse
OTA updates will never affect the bootloader status (S-ON/S-OFF, LOCKED/UNLOCKED/RELOCKED)

If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
Click to expand...
Click to collapse
So, if I did flash a custom kernel, and did uninstall system programs (but didn't flash a custom Rom), what are my options if I'd like to upgrade to lollipop?
Thanks!
Sent from my HTC One using XDA Free mobile app