[Sandman333]

Cydia Impactor does not work. It cannot find my phone at all. Yes I have USB Debugging enabled. Yes I have Install from Unknown Sources enabled. The program simply does not work with my phone for whatever reason.

Does anyone know anything about this?

[Sandman333]

I think my problem might be that I don't have the adb whatever installed? I looked at this site: Android Debug Bridge | Android Developers

It says

You can find the adb tool in <sdk>/platform-tools/.

Ok, where is that at? There is no link provided. The problem with the way these sites are written is that they expect the reader to have specific familiarity with the terms and concepts outlined. For someone who is coming into this cold, there is absolutely no way to find the tools the author is talking about. VERY poor documentation of the procedures.

[Sandman333]

I downloaded and installed the Android SDK. I finally found the adb application. Launching it opened a CMD window briefly. I tried Impactor again, and still it will not connect. I tried the USB link. I tried the "Bridge" (whatever that is) and entered my phone's IP on my home network. Nothing. Conclusion: Impactor sucks. This method does not work.

[doogald]

I think my problem might be that I don't have the adb whatever installed? I looked at this site: Android Debug Bridge | Android Developers

Ok, where is that at? There is no link provided. The problem with the way these sites are written is that they expect the reader to have specific familiarity with the terms and concepts outlined. For someone who is coming into this cold, there is absolutely no way to find the tools the author is talking about. VERY poor documentation of the procedures.

To be honest, I am sort of fine with this - rooting your phone (especially this one, with its locked bootloader!) is a big step, a risky one, and if you can't figure out how to install ADB, maybe you have no business rooting your phone... However, it's your phone - if you want to risk wrecking it and can afford to buy a new one if it happens and its unrecoverable, more power to you.

Here is a good ADB guide, with an easy mini-ADB in the second post which should be all that you need and should get you through it: http://androidforums.com/faqs/443072...3-05-21-a.html

[Sandman333]

I understand exactly what you are saying, but then again how is anyone ever supposed to learn?

[Sandman333]

I downloaded and installed the Android SDK. Launching it only flashes a CMD window very briefly. It appears to do nothing else. I found the ADB application under the Platform - Tools folder. Launching that flashes a CMD window for a little longer.... and nothing. Impactor still will not find my phone. I have the correct usb drivers installed according to Device Manager. It seems there is no COMPLETE set of instructions, and PLENTY of conflicting information.

[doogald]

I downloaded and installed the Android SDK. Launching it only flashes a CMD window very briefly. It appears to do nothing else. I found the ADB application under the Platform - Tools folder. Launching that flashes a CMD window for a little longer.... and nothing. Impactor still will not find my phone. I have the correct usb drivers installed according to Device Manager. It seems there is no COMPLETE set of instructions, and PLENTY of conflicting information.

Start and type "CMD" into the search field (I think - it's been a while since I've used windows...). This will open a command window. Then change directory to the location of the sdk files and run ADB from there.

So, if you have the SDK installed in c:\android-sdk-windows\platform-tools, your first command would be:

cd \android-sdk-windows\platform-tools

This should change the prompt to c:\android-sdk-windows\platform-tools > and you can run adb from there by entering ADB at the prompt. (If you have ADB installed in a different folder, type the path to that folder instead.)

That's how you are supposed to use ADB on Windows. It's a command line tool.

[Sandman333]

Start and type "CMD" into the search field (I think - it's been a while since I've used windows...). This will open a command window. Then change directory to the location of the sdk files and run ADB from there.

So, if you have the SDK installed in c:\android-sdk-windows\platform-tools, your first command would be:

cd \android-sdk-windows\platform-tools

This should change the prompt to c:\android-sdk-windows\platform-tools > and you can run adb from there by entering ADB at the prompt. (If you have ADB installed in a different folder, type the path to that folder instead.)

That's how you are supposed to use ADB on Windows. It's a command line tool.

Well, that kept the CMD window open. However, Cydia Impactor still will not find my phone. Now what? This is the problem. There seems to be no way to learn what to do here because there is no complete instruction set anywhere (at least that I can find).

[doogald]

Well, that kept the CMD window open. However, Cydia Impactor still will not find my phone. Now what? This is the problem. There seems to be no way to learn what to do here because there is no complete instruction set anywhere (at least that I can find).

If you do the command:

adb devices

what output do you get back?

[Sandman333]

OK, I finally figured out that there were a LOT of things that were left out of the instructions. I am now able to talk to my phone through Impactor and over telnet.

Things not in the instructions: Even though there are no errors shown in Device Manager with your phone installed, that does not mean that you have all the required drivers. Do an internet search for "Motorola Device Manager". Download and install with your phone plugged in and hopefully it will install the two ADB drivers that you need. If it doesn't, uninstall the device from Device Manager and start over and reinstall until it picks the drivers up. This seems to be entirely luck of the draw. I finally got mine to install.

Win7 does not have telnet installed by default. You will have to go into Control Panel and up at the top is a link to "Turn features on or off". Click that, check Telnet in the tree that comes up, and save.

Now, I am at another point where I am stuck, and the instructions conflict themselves. This is what I am talking about:

First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.

Well, which is first? The two sentences contradict each other as to which should be used first. Further, if you click on the MotoWPNoMo link, it says that you have to have root to make it work. Well, in the process of trying to get root, I am at this stage:

Run the exploit through telnet

Quote:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
The exploit will tell you to use adb to reboot:

I get back an error, saying "sh dalvikm: Permission denied"

I'm guessing this is because of write protection? However, on this same page that is linked to by jcase and describes how to disable write protection, it states:

Pre-requisites:

1.) Working root (su). Jcase's methods are fully supported here
2.) Working adb and fastboot drivers. Yes, that means WORKING. Don't clutter this thread with driver issues
3.) Linux (32 bit) or windows
4.) Disable all firewalls/internet security/antivirus before running. This is the #1 issue encountered when running the application

The 1st prerequisite says you have to have root. jcase seems to indicate that you need write protection removed in order to get root.

So, which came first, the chicken or the egg? Is it any wonder that the instructions are confusing?

[Sandman333]

If you do the command:

adb devices

what output do you get back?

List of devices attached

TA4310CO8E device

[Sandman333]

[doogald]

Before going on, let me just say that I have not rooted my Maxx, and have no interest in doing so. However, I've rooted other phones, so I'm generally aware of the procedure...

Things not in the instructions: Even though there are no errors shown in Device Manager with your phone installed, that does not mean that you have all the required drivers. Do an internet search for "Motorola Device Manager". Download and install with your phone plugged in and hopefully it will install the two ADB drivers that you need. If it doesn't, uninstall the device from Device Manager and start over and reinstall until it picks the drivers up. This seems to be entirely luck of the draw. I finally got mine to install.

Right, that's why I had you do the adb devices command. If your computer didn't list the phone, then you didn't have the drivers installed correctly.

Now, I am at another point where I am stuck, and the instructions conflict themselves. This is what I am talking about:

First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.

Well, which is first? The two sentences contradict each other as to which should be used first. Further, if you click on the MotoWPNoMo link, it says that you have to have root to make it work.

No, it's just sloppy writing. He's saying that you need to have write protection removed before you can proceed with the procedure. Some people who rooted hadn't taken that second step. The second sentence clarifies for people who have not yet rooted that you need to gain root first.

(By the way, these instructions seems to be for the Moto X. The part "and then restore to the 4.2.2 Camera update" is something that we can't do with the Maxx.)

I get back an error, saying "sh dalvikm: Permission denied"

I'm guessing this is because of write protection?

Do you have root yet? I think that you just don't have root.

However, on this same page that is linked to by jcase and describes how to disable write protection, it states:

The 1st prerequisite says you have to have root. jcase seems to indicate that you need write protection removed in order to get root.

No, the opposite: you need root first in order to remove write protection.

[Sandman333]

LMAO, I missed one letter in the CMD line. That's why I got the permission denied....

[Sandman333]

Another bit that is missing: Each time the phone reboots during this process, I have to re-run the telnet command through Cydia Impactor, and then rerun the telnet command through the CMD prompt.

[Sandman333]

Success?



Sent from my XT1080 using Tapatalk

[doogald]

Another bit that is missing: Each time the phone reboots during this process, I have to re-run the telnet command through Cydia Impactor, and then rerun the telnet command through the CMD prompt.

Maybe when you are done you can take the time to write a full set of instructions?

[Sandman333]

Maybe when you are done you can take the time to write a full set of instructions?

Haha, if I wasn't so confused I just might! Don't get me wrong, I know that whoever figures out these exploits has a lot of knowledge I will never have and puts a lot of their time and effort into it. They just need someone to edit their instructions.

Sent from my XT1080 using Tapatalk

[Sandman333]

Success?



Sent from my XT1080 using Tapatalk

[Sandman333]

Sent from my XT1080 using Tapatalk

[Sandman333]

Ok, I did the MotoWpNoMo and got to the point where it told me to press enter to exit. I then ran the command to check write protection status and got nothing at all back. Did it disable it or not?

I ran the command again and got a "1" back. It didn't work. Sigh...

Ran the program again, and this time it seemed to do more than the first time and when I checked with the adb command it returned a 0! Success!

[Sandman333]

So I got root established with RockMyMoto. I got write protection disabled. Now I am at the stage to do SlapMyMoto and after the first command, it tells me that SlapMyMoto does not support rooted devices. WTF? WTH did his instructions have me root then? I rooted to get write protection and now have to unroot in order to root a different way? Where are the unroot instructions?



Figured it out, I had to turn SuperSu off.... dummy me....

[Sandman333]

OK, I am now at the stage in SlapMyMoto where I can take the 4.4 update to KK.

Question, do I leave SuperSu installed but disabled, or what? With all the other missing instructions that I had to figure out..... I just dunno.