Root no root after 181 update

mnkyvndor

Newbie
Lost root after 181 update... no big suprise... but voodoo ota rootkeeper is not restoring root... will try re-rooting later in the AM after i wake up
 

iploya

Android Enthusiast
Please explain. I also lost root with the update, and wasn't sure whether we would have to wait for developers to come up with another root solution or if it can be done now?

Thanks
 

Bodycount

Android Enthusiast
The Motofail version of root still works. There's a link to it somewhere on these forums, no clue where though.
 

iploya

Android Enthusiast
The Motofail version of root still works. There's a link to it somewhere on these forums, no clue where though.

I tried Motofail a few times. I get

"'adb' is not recognized as an internal or external command, operable program or batch file."

I did check to ensure that USB debugging is on, and I also installed Motohelper driver thing to make sure (I think) that I have the latest drivers.
 

srq2625

Member
I ran Voodoo OTA RootKeeper, backing up SU, before installing the .181 update. Then ran it again after the update to restore SU. No issues, no worries.
 

Bodycount

Android Enthusiast
I tried Motofail a few times. I get

"'adb' is not recognized as an internal or external command, operable program or batch file."

I did check to ensure that USB debugging is on, and I also installed Motohelper driver thing to make sure (I think) that I have the latest drivers.

Try this version attached to this message. It worked for me.
 

Attachments

  • motofail_windows.zip
    1.8 MB · Views: 97

mnkyvndor

Newbie
Thread starter
Sorry i havent responded yet... didnt get the update emails... anyhoo... not really sure what more you want explained
 

iploya

Android Enthusiast
Try this version attached to this message. It worked for me.

Thanks, I just tried yours too. Same problem:
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
'adb' is not recognized as an internal or external command,
operable program or batch file.
[*] Device found.
[*] Deploying payload...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
[*] Owning phone...
'adb' is not recognized as an internal or external command,
operable program or batch file.
[*] Rebooting device...
'adb' is not recognized as an internal or external command,
operable program or batch file.
[*] Waiting for phone to reboot.
'adb' is not recognized as an internal or external command,
operable program or batch file.
[*] Attemping persistence...
'adb' is not recognized as an internal or external command,
operable program or batch file.


I've tried this in each of USB Mode, PC Mode, Charge Only Mode, and Windows. Same result in each.
 

iploya

Android Enthusiast
Now THIS is weird.

I previously had the Motofail folder on my desktop. I tried dragging/dropping to a folder on my C drive. Now it WORKS.

Thanks.
 

tucstwo

Lurker
Now THIS is weird.

I previously had the Motofail folder on my desktop. I tried dragging/dropping to a folder on my C drive. Now it WORKS.

Thanks.

This most likely has to do with how the .bat file locates the ADB commands in its folder. For some reason, it didn't like being on your desktop and preferred being right on your c drive.
 

VoidedSaint

Resident Ninja
i wasnt able to root .173 (i think) but i was able to root .181 and im good, now i just want a rom to remove the bloat... this phone feels and looks alot different than the nexus.. but it is much worth it considering the issues i had with the nexus
 
Top