618 replies to this topic

[livinginkaos]

I wasn't obviously thinking clearly. The script is not recognizing the phone because adb needs the phone booted. You could try rsd one more time. Sometimes for whatever reason it just doesn't take on the first try. Another thing we can do is try to fastboot the system.img and boot.img from the fxz you have. Just put the boot.img and system.img files in the fastboot folder, put the phone in apfastboot, plug in usb to usb2 connection, open a command prompt, navigate to the folder with the files and do: Fastboot flash system system.img Fastboot flash boot boot.img Fastboot reboot From My S4 Dev Edition

[toddbecker]

I wasn't obviously thinking clearly. The script is not recognizing the phone because adb needs the phone booted. You could try rsd one more time. Sometimes for whatever reason it just doesn't take on the first try. Another thing we can do is try to fastboot the system.img and boot.img from the fxz you have. Just put the boot.img and system.img files in the fastboot folder, put the phone in apfastboot, plug in usb to usb2 connection, open a command prompt, navigate to the folder with the files and do: Fastboot flash system system.img Fastboot flash boot boot.img Fastboot reboot From My S4 Dev Edition

 

I tried RSD a number of times, no luck.

 

One thing I have noticed, whenever I connect the phone to the computer via USB, the resulting drive that is mapped in Windows is not accessible.  Could this be an indication that USB Debugging was not selected?  I am 90% sure it was, but all these problems are leading me to second guess myself.

 

Unfortunately, I am at work, I won't be able to try anymore recovery steps until I get home tonight.  I will get a copy of ADB and try to execute the Fastboot commands directly.

 

Thanks again for the continued support.

[toddbecker]

navigate to the folder with the files and do: Fastboot flash system system.img

 

C:\adb>fastboot devices

99000200796402  fastboot

 

C:\adb>fastboot flash system system.img

  sending 'system' (864977 KB)... INFOData size exceeds download buffer

FAILED (remote failure)

finished. total time: 1.361s

[SamuriHL]

Wrong version of fastboot.  Use the one in the motochopper root exploit.

[toddbecker]

Direct use of ADB seems to have succeeded, however, the phone still hangs with rotating red droid graphic.

Please Login or Register to see this Hidden Content

[SamuriHL]

Sounds like the data partition's corrupt at this point.  Good times.  You'll need to go into recovery and factory reset it.  You will lose your data and need to reinstall everything.

[toddbecker]

Sounds like the data partition's corrupt at this point.  Good times.  You'll need to go into recovery and factory reset it.  You will lose your data and need to reinstall everything.

 

That is fine. However, when I go into recovery and get the dead android, I can't do anything else.  My understanding is that after I get the dead android, I should hold VOL UP + VOL DWN?

[SamuriHL]

Volume down + volume up.

[toddbecker]

Volume down + volume up.

 

OK, are you screwing with me?  volume down + volume up doesn't do anything either.

[SamuriHL]

No, I'm not.  People all complained that it never worked so when I had an HD I spent time figuring out exactly how it works.  Hold volume down and tap volume up and the menu comes up.  

[johnthehillbilly]

Sometimes those of us with fat fingers (or trying to do it while driving LOL ) can't seem to get both buttons at the same time LOL ... I do it like Sam said... hold volume down.... and tap volume up.... works great HD tappin' ..... hillbilly style!...

[toddbecker]

No, I'm not.  People all complained that it never worked so when I had an HD I spent time figuring out exactly how it works.  Hold volume down and tap volume up and the menu comes up.  

I can't even count how many times I tried variations of that, except for the 'tap' THANK YOU!!!

 

OK, now what?  Do I do the wipe cache then the data/factory reset?

[SamuriHL]

Factory reset.  Cache will go with it.  

[toddbecker]

Super duper THANK YOU to SamuriHL, livinginkaos, johnthehillbilly, aviwdoowks

 

My RAZR is back!

[aviwdoowks]

No, I'm not.  People all complained that it never worked so when I had an HD I spent time figuring out exactly how it works.  Hold volume down and tap volume up and the menu comes up.  

BTW The xt897 stock recovery does not have this issue (the secret double press is not borked) as having a well as an apply update from cache!

Works fine on the M

Edit

Rant:

This "secret" double press of the volume keys is borked on our M & is a great source of frustration.

I think we got a borked version of stock recovery & Moto does not care to fix it.

The Photon Q recovery is not borked & double key access is easy.

[butface123]

For some reason the razr m will not root using macbooks any suggestions on why?

I am always getting the -bash: ./run.sh: /bin/bash^M: bad interpreter: No such file or directory

when i execute it.

[cmh714]

I apologize for the problems (not that I created them ). I am looking into this to fix for the utility and the masses. In the meantime, if you run this command it will fix the file.

 

command to run:  tr -d '\r' < input.file > output.file

 

where input.file is run.sh and output.file is whatever you want to call the "new" script.

[SamuriHL]

I just updated the OP with 1.3.  It should bring the xt907 version in line with the xt926 version and should be fixed for linux/mac now.  I hope.  Can someone try it on a mac and let me know?  Thanks.

[aviwdoowks]

I just updated the OP with 1.3.  It should bring the xt907 version in line with the xt926 version and should be fixed for linux/mac now.  I hope.  Can someone try it on a mac and let me know?  Thanks.

Op link gets me 112?

[SamuriHL]

Op link gets me 112?

 

Stupid forum software.  It's fixed.