X
Tap here to go to the mobile version of the site.
Scheduled maintenance: Thursday, April 2, between 3pm and 5pm UTC. This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn’t solve your issue and you want to ask a question, we have our support community waiting to help you at @firefox on Twitter

Support Forum

No root access after setting ro.secure=0, and ro.debuggable=1

Posted

I have an alcatel one touch fire e (FFOS version 2.0), and I am trying to root it. I successfully flashed an CWM recovery image to recovery, and attempted to sideload a SuperSu binary (I was following this guide: http://blog.vosnax.ru/2015/04/27/Rooting-an-Alcatel-Fire-E-6015x/ ) After I did that, i still didn't have root access (which according to that guide I should have after running su)

I proceeded with pulling the boot.img (and some other img files) from my device, and unpacked the boot.img, changed the default.prop and repacked it, I tested it, and it worked (as in the phone booted normally, but no root access), I flashed it. And now I still don't get root access, not from using su (it doesn't say command not found or anything, it just doesn't seem to do anything at all), or adb root. My default.prop file shows the following:

andrew@Andrew-Gentoo ~/Downloads $ adb shell busybox cat default.prop

  1. ADDITIONAL_DEFAULT_PROPERTIES

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=1

persist.sys.strict_op_enable=false

persist.sys.whitelist=/system/etc/whitelist_appops.xml

persist.sys.usb.config=none

andrew@Andrew-Gentoo ~/Downloads $ adb shell

shell@msm8610:/ $ su

1|shell@msm8610:/ $

What did I miss, I thought the only thing I had to do was change ro.secure?

EDIT: I do have root access in recovery mode

I have an alcatel one touch fire e (FFOS version 2.0), and I am trying to root it. I successfully flashed an CWM recovery image to recovery, and attempted to sideload a SuperSu binary (I was following this guide: http://blog.vosnax.ru/2015/04/27/Rooting-an-Alcatel-Fire-E-6015x/ ) After I did that, i still didn't have root access (which according to that guide I should have after running su) I proceeded with pulling the boot.img (and some other img files) from my device, and unpacked the boot.img, changed the default.prop and repacked it, I tested it, and it worked (as in the phone booted normally, but no root access), I flashed it. And now I still don't get root access, not from using su (it doesn't say command not found or anything, it just doesn't seem to do anything at all), or adb root. My default.prop file shows the following: andrew@Andrew-Gentoo ~/Downloads $ adb shell busybox cat default.prop # # ADDITIONAL_DEFAULT_PROPERTIES # ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.sys.strict_op_enable=false persist.sys.whitelist=/system/etc/whitelist_appops.xml persist.sys.usb.config=none andrew@Andrew-Gentoo ~/Downloads $ adb shell shell@msm8610:/ $ su 1|shell@msm8610:/ $ What did I miss, I thought the only thing I had to do was change ro.secure? EDIT: I do have root access in recovery mode

Modified by Andrew Ammerlaan

Additional System Details

Application

  • User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0

More Information

Question owner

I tried adding ro.adb.secure=0 which didn't do anything. And I also tried replacing the adbd binary with the one from the boot image that i got of the above mention website, which resulted in: $ adb root can't run adb as root in production builds or something like that, i didn't save it :( while running adb root with the original adbd binary results in: restarting adbd as root but, running adb shell afterwards results in a non-root shell.

I tried adding ro.adb.secure=0 which didn't do anything. And I also tried replacing the adbd binary with the one from the boot image that i got of the above mention website, which resulted in: $ adb root can't run adb as root in production builds or something like that, i didn't save it :( while running adb root with the original adbd binary results in: restarting adbd as root but, running adb shell afterwards results in a non-root shell.

Modified by Andrew Ammerlaan

guigs 1072 solutions 11697 answers

Hi Andrew , You might get a quicker and more specialized response in this Mozilla mailing list: https://lists.mozilla.org/listinfo/dev-security-policy

Hi Andrew , You might get a quicker and more specialized response in this Mozilla mailing list: https://lists.mozilla.org/listinfo/dev-security-policy