Database Develop

Problem rooting - Failed: Too many links

I'm having a problem rooting my Nexus One (I have also read the newbie FAQ and searched the forum to no avail) - I have followed the instructions listed on the androidandme site.
When I try to unlock using fastboot I get this returned:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
When I start the phone in fastboot mode it now says *** UNLOCKED *** at the top of the screen. I then flashed Amon-Ra's recovery image, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-
RA-nexus-v1.6.2.img
sending 'recovery' (3954 KB)... OKAY
writing 'recovery'... OKAY
I assumed everything was going to be fine despite the issues unlocking. On trying to boot into recovery mode all I get is a screen with an exclamation mark and the android robot.
On turning the phone on as usual it seems that I can not run "Root required" apps such as the N1 torch.
I have tried running the OEM unlock command again but it seems to think that it has worked, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFODevice was already unlocked!
OKAY
It would seem from the newbie guide that I still need to flash the recovery image but that seems to be going fine. I can't see that I've messed up so far so is there some way to "unroot" my phone or go through the OEM unlock process again?
Thanks.

You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.

jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
I tried this, but still don't have root permissions - any thoughts?
I have read and searched and read some more and searched some more, and now just need some help...
Thanks in advance.

2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.

jongie123 said:
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
Click to expand...
Click to collapse
I suggest One thing. Pay 15.47 american Usd, at Online Kitchen for Modaco, Viola, Your done, always rooted.. Always Su'd up..
The Bootloader is simple on a windows machine, and so is root.. On Modaco's site there is a whole tutorial on this.. Plus search the threads, a whole ish load too..
i"d pay the 15.47.. Just Nike it, Just do it.. It's so much easier.. Just click-click, bake, download, flash, done..
Go..Go..!

jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?

If you just need root, get 'superboot'. It needs to be flashed to the "boot" partition (after unlocking the bootloader).
What it does is copy the root files to the data ROM and sets up permissions the first time the phone is booted (runs some sort of script I guess).
Link to superboot (free), make sure you get the right version:
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/

look up "get root back".... Try these commands via ADB:
adb remount
adb shell chmod 6755 /system/xbin/su
....This should "fix_permision" and get you root back, IF you ever had it....

papermonk said:
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
Click to expand...
Click to collapse
Using adb you can issue "adb reboot recovery" and wind up in recovery mode. You can also hold down the power button and trackball (connected or disconnected from the computer) and enter fastboot. From there, select bootloader and then recovery.

I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.

sadhuKashmir said:
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
Click to expand...
Click to collapse
If you are rooting a G1, correct me if I am wrong, but couldn't you just use one of the one click root methods?
I thought all of the patches denying one click root were contained in official FW's of GB and the G1 did not get it.

Getting my rooting concepts straight

I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
So far so good? Am I missing anything?
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?

Didn't miss anything.
You can go several ways: since your bootloader is unlocked, to save yourself the pain with ADB loop method, which is completely unneeded, you can just use the regular method, skipping the "unlock bootloader" part, which leaves you with "flash custom recovery" part (totally independent) and then just flash whatever ROM you like, pre-rooted. You don't need to flash a rooting file over your ROM, you just can change your ROM to pre-rooted one.

So you are saying that I can flash a custom recovery, then load a custom rom that is pre-rooted?
How do I flash a custom recovery if I am not rooted? I thought that in order to get the recovery you needed to root via superboot?
And I must have a custom recovery in order to have a pre-rooted rom, otherwise the phone will reject the package, right?
So the only thing that prevents root on the Android is the rom and recovery partition's own integrity check for whatever you are flashing? In other words, people can lose root by flashing a stock rom, and you can get root by flashing a pre-rooted rom. I seem to remember seeing some pre-rooted packages saying that you must have previously had root in order for it to work. Is that not correct, then?
Thanks.

hgcrpd said:
I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
Click to expand...
Click to collapse
Not exactly - root access simply indicates having the su and superuser.apk binaries installed, and the suid bit set on su. But you are close enough. If you are running FroYo, Cyanogen and Lox have published flashable rooters.
You will already need a custom recovery to flash either of these - but since your bootloader is unlocked, a custom recovery does not pose any problem - see below...
hgcrpd said:
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
Click to expand...
Click to collapse
Yes.
hgcrpd said:
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
Click to expand...
Click to collapse
Couple of points here:
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
2. Recovery does not use the same shell and variables as /system. Busybox is usually installed in recovery to allow you to run things via ADB or scripts when in recovery mode without manually calling them off of system (something that would be a problem if you were formatting and rewriting system, for example).
hgcrpd said:
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Click to expand...
Click to collapse
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you? In any case, I would just install the SDK - it's free, fast and gives you access to fastboot and adb. You need fastboot to install a custom recovery, and adb is useful for lots of things.
And there are plenty flashable root zips for FRF91. You need to first install a custom recovery!
http://forum.xda-developers.com/showthread.php?t=715799
http://forum.xda-developers.com/showthread.php?t=686627
So, if I were you:
1. Install the Android SDK on your computer to get ADB, fastboot and the necessary drivers.
2. Download and flash a custom recovery using fastboot.
3. Reboot into recovery.
4. Copy Lox or Cyan's rooter to your SD card using adb push.
5. On the phone, in recovery, do a nandroid backup!
6. Flash the zip from step 4.
7. Reboot your phone and confirm that you have root - the easiest way is to start up a terminal session and type "su". The Superuser authorization program should pop up and ask you to approve the application's request for root access. Grant it. If the prompt turns from "$" to "#", you have root.

1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
Click to expand...
Click to collapse
I see. So the post on modaco is not quite correct when it says that root is a pre-req for Amon_RA's recovery. I'm guessing that's only a pre-req if you flash via a terminal session on the phone? (By the way, is there an official terminal app? The only one I could find was Terminal Emulator.)
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you?
Click to expand...
Click to collapse
Bootloader was unlocked when I bought it. The phone is a grey-market item that I purchased here in China, and every grey-market phone that comes in gets modified by the importers in order to add Chinese language support and such. I think that's all they did, since I've been able to do updates and get OTA without a problem.
Thanks! I will give the SDK route a try, if I get time before the superboot for FRF91 comes out.

[Q] cant boot into recovery

so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04

drawde40599 said:
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
Click to expand...
Click to collapse
Use fastboot to re-flash recovery img

lcchan1 said:
Use fastboot to re-flash recovery img
Click to expand...
Click to collapse
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?

drawde40599 said:
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
Click to expand...
Click to collapse
download clockwork recovery from the app store.
Flash its recovery, then boot into recovery after a successful flash.
Out of curiosity, why did you install a non-rooted version of 2.3.3.?

You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.

Rusty! said:
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Click to expand...
Click to collapse
HELL YA !! thank u much

Thread moved to Q&A, a sub-forum dedicated exclusively for questions like these. Please post all further questions here. Do not post new question threads in development, as you are not doing any even remotely related to Android development. That said, I'm glad you were able to figure out your issue.

Downloading clockworkmod will not work. He is not rooted so he can't flash the recovery with it.
Sent from my Nexus One using XDA App

This happened to me 2 days ago (word by word)!!
From Amon Recovery's page, this is what the problem is:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here"
Here: http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
My problem was even more complicated because I tried flashing froyo without a wipe so my phone started going into boot loop!
Thanks to danger-rat's reply, I was able to get into recovery at least once and then everything came back under control. He said "Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to..."
Here's my thread:
http://forum.xda-developers.com/showthread.php?t=980577
edit: I just realized that you are not able to fastboot either? I was able fastboot and flash recovery onto my phone and then without turning the phone off - I was able to go into recovery straight after flashing amon_recovery.img

passimg back to an earlier version of Android, root, then install a pre-rooted GB...
If you get the "main version is older" error, you're out of luck and your only option is to unlock the bootloader or wait for a new method to be found...
Sent from my Nexus One using XDA App

[Q] Root Nexus One 2.3.4 (stock)

Anyone know how to root Nexus One 2.3.4? I've done a few search but I can't find a full guide for that.
Thank you. Peace.

Since Gingerbreak doesn't work with 2.3.4(IIRC), what you can do is:
1.
- Downgrade to 2.3.3.
- Use gingerbreak to get root, flash custom recovery.
(If you downgraded to froyo, you can root it with z4root or SuperOneClick)
- Get ChainsDD's Superuser in flash-able .zip file. Copy it to SD card.
- Get 2.3.4 OTA update patch, copy it to SD card. If you don't want to lose custom recovery, open zip file with any archive utility, delete /recovery from zip. It will prevent stock recovery from restoring.
(If you downgraded to froyo and rooted, you need to get all OTA patches for upgrading to 2.3.3 and 2.3.4)
- Boot to recovery, flash (modified) OTA update patch. Don't reboot the device yet.
- Flash Superuser.
If you can use any application that requires root permission, you're done.
2. Unlock bootloader, push custom recovery and Superuser.
3. This requires Android Kitchen.
- Downgrade to 2.3.3 and root, flash custom recovery, same as 1.
- Get 2.3.4 system dump here.
- Use Android Kitchen to make rooted stock 2.3.4 package. When it's done, copy it to SD card.
- Backup all your data before proceed.
- Reboot to recovery, flash the package you made.
- Reboot and check. If nothing's wrong, you will have rooted stock with custom recovery.

Or when you're on 2.3.4, go to fastboot, flash a custom recovery, flash the superuser.zip

illuminarias said:
Or when you're on 2.3.4, go to fastboot, flash a custom recovery, flash the superuser.zip
Click to expand...
Click to collapse
You need to unlock bootloader to do that.

LFact said:
You need to unlock bootloader to do that.
Click to expand...
Click to collapse
unlock bootloader will wipe all data on device.

Hi guys, thank you for the tips.
So the best way is tho unlock the bootloader? I have no issue to do that since my warranty is finished. Doesn't matter whether it wipes out my data. I have few questions:
1. After I unlocked my bootloader, can I update any upcoming firmware OTA in the future? Or I have to flash it via sdcards.
2. I've heard about rebooting will unroot the phone. Is it true?
3. How do I unlock my bootloader?
4. Is changing rom will reset the phone to factory setting? Will my phone get unrooted?
Sorry I'm quite a noob here. Peace! Appreciate any helps.

1. With unlocked bootloader you do what you want.
2. No.
3. Read the wiki or a another guide. Mainly get the needed software onto a computer and run fastboot oem unlock when the phone is in the bootloader.
4. Flashing/updating to any rom that does not have root included you will loose root. With unlocked bootloader that is no issue. Flash custom recovery then flash su = root.

Great! Thanks!! I will search for a guide and unlock my bootloader soon!

I just picked up a nexus one unlocked with 2.3.4 stock. I want to downgrade to 2.2.2 or 2.2.1, root it with super one click, then after I get root go to rom manager and get my recovery and then flash a cyanogenmod rom. Saying all that what is the easiest way to downgrade to 2.2.1 or 2.2.2 ???
Thanks

vinnyjr said:
I just picked up a nexus one unlocked with 2.3.4 stock. I want to downgrade to 2.2.2 or 2.2.1, root it with super one click, then after I get root go to rom manager and get my recovery and then flash a cyanogenmod rom. Saying all that what is the easiest way to downgrade to 2.2.1 or 2.2.2 ???
Thanks
Click to expand...
Click to collapse
Use passimg.zip. However, if it has really unlocked bootloader, all you have to do is use fastboot to flash custom recovery and any custom rom you want without doing so.

I have locked bootloader and have stock 2.3.4 on my nexus one... How to downgrade it to 2.3.3?

william31518 said:
I have locked bootloader and have stock 2.3.4 on my nexus one... How to downgrade it to 2.3.3?
Click to expand...
Click to collapse
Use passimg.zip, though it depends on your main version saved in bootloader. If you can get FRG33 or FRG83 passimg.zip(though I wonder if you can find it...), use that, then (manually) update them until you reach 2.3.3.

Hey peeps I've unlocked my bootloader and rooted it. So far so good. Thanks for all the helps.

cjoshua said:
Hey peeps I've unlocked my bootloader and rooted it. So far so good. Thanks for all the helps.
Click to expand...
Click to collapse
I feel daft; I have unlocked the bootloader but cannot root, how ridiculous is that.. Am on 2.3.4 build GRJ22.
I'm trying to install "Root" (point V) on http://forum.xda-developers.com/showthread.php?t=636795 but cannot enter the recovery, getting "triangled" for ever & ever.
Please help guys..
(P.S. It is 06:30 here and I've just worked the whole night, that doesn't make anything any easier..)

Not sure what the guide says, but:
Download and place this zip on your SD.
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
When connected in fastboot, type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Then flash the su zip - DONE!
Note:
name-of-recovery.img should be replaced with the actual name of the recovery image you have.
The recovery image needs to be located in the same folder on your PC as fastboot.
If your using mac or linux, fastboot may need to be substituted for fastboot-mac or fastboot-linux, etc.

danger-rat said:
Not sure what the guide says, but:
Download and place this zip on your SD.
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
When connected in fastboot, type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Then flash the su zip - DONE!
Note:
name-of-recovery.img should be replaced with the actual name of the recovery image you have.
The recovery image needs to be located in the same folder on your PC as fastboot.
If your using mac or linux, fastboot may need to be substituted for fastboot-mac or fastboot-linux, etc.
Click to expand...
Click to collapse
Thanks for the reply!
I think the problem is in that the "recovery-RA-passion-v2.2.1" isn't supporting build GRJ22 yet. Doing the above correctly (I think) but cannot boot into recovery.

You think wrong. Do it EXACTLY as danger said.

albundy2010 said:
You think wrong. Do it EXACTLY as danger said.
Click to expand...
Click to collapse
Woa, easy mate.. Found the problem, I think. There's no SD card in the phone. Would that explain it?
(Need to wait a while now until I can use the girlfriend's..)

SD isn't required to install recovery, but you will need it for the su zip.
What sort of message are you getting when you flash recovery?

danger-rat said:
SD isn't required to install recovery, but you will need it for the su zip.
What sort of message are you getting when you flash recovery?
Click to expand...
Click to collapse
I get OKAY on both "sending" & on "writing" the recovery in fastboot. I just cannot boot into recovery. It gets stuck on the triangle and I have to pull the battery

[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