Hello all. New S4 comes this week so I am trying to root an old droid 3 that's no longer using Verizon's service but that I am hoping to play with as a stand alone wifi device.
I am using some of the old one-click methods (including Petes) but none seem to work. It's 2.3.4 and on petes I get a message stating "ERROR: adb could not be granted root access via local.prop method". Not very descriptive. I tried using the motofail files and I get errors like
Unable to chmod /data/local/motofail: No such file or directory
Remount failed: operation not permitted
Failed to copy su to /system/bin/su: Read only file system
It's in USB debugging mode, I have all the drivers, it is set as USB charge only, etc. Not sure why all of a sudden it's not working as the method is the same I used in late 2011 when I rooted mine and nothing should have changed. Anyone have any thoughts on things to take a look at? Very odd!
The only thing I can think of is that it's some sort of driver issue but my device is found by the PC. I was using something from motos site called motohelper_2.0.51_Driver_5.2.0 Maybe that driver is too new as it's not the one I used 18 months ago.
I am using some of the old one-click methods (including Petes) but none seem to work. It's 2.3.4 and on petes I get a message stating "ERROR: adb could not be granted root access via local.prop method". Not very descriptive. I tried using the motofail files and I get errors like
Unable to chmod /data/local/motofail: No such file or directory
Remount failed: operation not permitted
Failed to copy su to /system/bin/su: Read only file system
It's in USB debugging mode, I have all the drivers, it is set as USB charge only, etc. Not sure why all of a sudden it's not working as the method is the same I used in late 2011 when I rooted mine and nothing should have changed. Anyone have any thoughts on things to take a look at? Very odd!
The only thing I can think of is that it's some sort of driver issue but my device is found by the PC. I was using something from motos site called motohelper_2.0.51_Driver_5.2.0 Maybe that driver is too new as it's not the one I used 18 months ago.
Last edited: