I've unlocked my bootloader and rooted the phone, but every time I try to use Adaway after Supersu gives permissions, it states "Copying of hosts file failed!"
Tried switching the target hosts file, but it doesn't work.
I have encountered the same message,I dirty flashed the rom again,and then adaway is working.
（I encountered the message,when I recoveryed rom using twrp. ）
I also tryed to reinstalled adaway, but doesn't work.
Try a different build of adaway
Sent from my SM-N910C using Tapatalk
I just took an up to date hosts file from another device and replaced the original hosts file in /system/etc. Worked like a charm.
Still not working, but it might be because I can't install busybox. I get an error everyone I try.
riceknight said:
I've unlocked my bootloader and rooted the phone, but every time I try to use Adaway after Supersu gives permissions, it states "Copying of hosts file failed!"
Tried switching the target hosts file, but it doesn't work.
Click to expand...
Click to collapse
I had the same issue when I was using wugfresh for rooting the device. Then I start over, and manual input the command line-by-line following this threat (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930), everything goes good.
I think wugfresh maybe used a wrong rooted boot.img file. This bug has been reported in wugfresh's website.
mine works fine with Chainfire's systemless root. (SuperSu v2.56)
yaoppp said:
I had the same issue when I was using wugfresh for rooting the device. Then I start over, and manual input the command line-by-line following this threat (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930), everything goes good.
I think wugfresh maybe used a wrong rooted boot.img file. This bug has been reported in wugfresh's website.
Click to expand...
Click to collapse
Thanks, will try it!
I haven't unlocked and rooted my 5X yet, but on my M8 running an MM GPE rom, I had this same problem. I just installed busybox from the Play Store (the one made by meefik) and it worked perfectly after that. It also made Root Explorer work for deleting system files.
Hope this helps...
riceknight said:
I've unlocked my bootloader and rooted the phone, but every time I try to use Adaway after Supersu gives permissions, it states "Copying of hosts file failed!"
Tried switching the target hosts file, but it doesn't work.
Click to expand...
Click to collapse
I'm using it without issue. Worked just like always. Make sure you're using the latest Adaway.
I was having this same issue on the stock ROM, but after flashing Pure Nexus I don't have the issue anymore
Sent from my Nexus 5X using Tapatalk
Related
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Step one : Go to the right forum.
Wrong subforum, but basically it's because you're rooted. The easiest solution is to just flash the system.img file from the factory image via fastboot and you should be good to go :good:
Thread moved to the right sub-forum and to the right section...
arviverona said:
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Click to expand...
Click to collapse
ota updates only work on devices that are not modified i.e. patched but you can still be rooted (aosp browser, mods to system will bork any ota). if you do not know how to reverse the patch/mod you applied to you device you need to reflash a stock version of the system (search for stock images) then apply the ota.
OP: Uninstall stickmount (doing so will copy back the stock debuggerd), and try the OTA again.
Thanks guys!
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
arviverona said:
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
Click to expand...
Click to collapse
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
mdamaged said:
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
Click to expand...
Click to collapse
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Duffmantp said:
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Click to expand...
Click to collapse
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
mdamaged said:
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
Click to expand...
Click to collapse
Actually I dont have stickmount installed, if that makes a difference.
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Well then your debuggerd should be stock, and this is all just academic. If the update fails, it won't be due to the debuggerd (unless there is some other app I do not know about that messes with debuggerd and you have that installed).
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
wantabe said:
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
Click to expand...
Click to collapse
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
mdamaged said:
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
Click to expand...
Click to collapse
That's it!
Hello,
I just upgraded my N7 to Android 5. Clockworkmod's Superuser is not working. I sideloaded the superuser.zip but the su binary seem wrong:
Code:
1|[email protected]:/ $ su
error: only position independent executables (PIE) are supported.
Any idea how to fix this?
Thanks.
I use TWRP with SuperSU so not sure but maybe the PIE fix will work for you. Search the forum.
Same problem with Chainfire's SuperSU
I encountered the same problem with Chainfire's SuperSU today after manually flashing the 5.0 factory image. Any suggestions? I searched the forums for the "PIE fix" and came up empty-handed.
Try downloading a custom kernel, then reflashing SuperSU. Of you're not into custom kernels, that's fine. You can still use the options available in AROMA to make it as close to stock as possible
ohmer said:
Hello,
I just upgraded my N7 to Android 5. Clockworkmod's Superuser is not working. I sideloaded the superuser.zip but the su binary seem wrong:
Code:
1|[email protected]:/ $ su
error: only position independent executables (PIE) are supported.
Any idea how to fix this?
Thanks.
Click to expand...
Click to collapse
Use chain fires autoroot
Sent from my Nexus 7 using Tapatalk
NPOA556 said:
I encountered the same problem with Chainfire's SuperSU today after manually flashing the 5.0 factory image. Any suggestions? I searched the forums for the "PIE fix" and came up empty-handed.
Click to expand...
Click to collapse
Post #13
I needed this in addition to autoroot. It says for N5 but it's what I flashed on N7 FLO.
ritchea said:
Post #13
I needed this in addition to autoroot. It says for N5 but it's what I flashed on N7 FLO.
Click to expand...
Click to collapse
Well, I don't know if the PIE patch was what I needed, since I tried if first without success. But when I tried CF-Auto-Root, that worked. Don't know if it would have worked had I not already tried the PIE patch, but it works now, so I'm happy. Thanks!
I encountered exactly the same error, solved it by using Chainfire Autoroot AFTER reflashing the recovery.
Don´t ask me why, after I flashed Lollipop, my CR was gone (yea, I know how to do that without losing CR...actually ....I thought) and CA got stuck. Reflashed CR via Fastboot, ran CA, stuff hs been working excellently for two days now....so I guess it worked.
The reason why superuser doesn't work is because of changes in Lollipop. Those changes make you flash a custom kernel/boot image.
CF-Auto-Root works because it flashes a custom boot image.
1 - chainfire autoroot
http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip
2 - latest Supersu
http://download.chainfire.eu/624/SuperSU/BETA-SuperSU-v2.23.zip
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
smac7 said:
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
Click to expand...
Click to collapse
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked in /system and it's not there. I did however folder called ADDON.D that has Update_SuperSU within it. If i understand correctly, this would set-off the trigger to see system as modified. Is it possible the unSU zip i used (to try to unroot pure nexus) didn't work correctly?
So, apparently i was supposed to go to terminal and enter
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
If you can add a card you pass the safetynet. You should be ready to use it. Just remember if you do anything else that you can still cause your phone to fail the safetynet and prevent payment even after your cards are added.
I've posted in a Nexus 6P thread, might be helpful though, but I had to disable SuperSU (not Full unroot) in order to get AndroidPay/CapOneWallet/Safetynet to work. And that's after editing build.prop, removing /su/xbin_bind, and installing EX Kernel, using Stock 6.0.1 and SuperSU 2.66 with systemless root.
The folder is located under /su not /system
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
bdivs11 said:
The folder is located under /su not /system
Click to expand...
Click to collapse
You're right. I thought it was under /system but it is under /su
Sent from my Nexus 5X using Tapatalk
smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
2x4 said:
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Android Pay is not working on my 5x. I used the MSkip Toolkit's systemless root option, as well as used that Toolkit to unlock, de-encrypt, ect. That was done with I think a temp flash of TWRP so I keep stock recovery?
The only other thing I did to my phone was the build prop edit to enable tethering on Verizon which in the thread people said doesn't break their Android Pay.
Android Pay says cannot verify yadda yadda. I disabled SU in the app, rebooted and AP still doesn't work. Now when I try to re/enable SU fails installing/fails updating binary.
Anyone have any advice? Does some file need to be deleted or a fresh install?
greves1 said:
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Click to expand...
Click to collapse
Chainfire (SuperSU dev) is not developing systemless root to be compatible with Android Pay. That was never his aim. Anything he adds is for the purpose of not using /system for root. If you would like to read on changes to SuperSU, I suggest reading the brief changelogs or following his SuperSU beta thread to keep up to date on changes in SuperSu (systemless or otherwise).
Btw, you can flash whichever version of SuperSu you desire. If it is easier to get Android Pay working for you, cool.
I just use 2.61 and it just works with Android pay. No terminal commands or anything
stu5797 said:
I just use 2.61 and it just works with Android pay. No terminal commands or anything
Click to expand...
Click to collapse
Same here. I can't see any reason to "upgrade" since the later versions seem to require additional steps, and for the user I don't seem to get any added value from the later versions.
greves1 said:
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
Click to expand...
Click to collapse
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
tallgrasshawk said:
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
Click to expand...
Click to collapse
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
greves1 said:
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
Click to expand...
Click to collapse
I've done it both ways and it definitely works when you run the terminal commands prior to flashing. I did it wrong (without terminal commands) first, so i had to do "full unroot" from the app itself, then in recovery ran the terminal commands and flashed 2.66 again and now it works fine for me.
You also have to avoid modifying the /system partition after the fact otherwise that will also break android pay, even if you already have a card added.
you can check with this app if android pay will work:
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground&hl=en
for example, the aggressive doze option on the new greenify beta will break safetynet, as will Adaway (unless you flash the systemless hosts zip first)
newb question
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Phssthpok said:
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Click to expand...
Click to collapse
Months later but adb/fastboot is the key to for terminal commands to your mobile. Likely you've solved by now but if not, theres an easy way to get adb going: http://www.androidbeat.com/2015/11/how-to-set-up-adb-and-fastboot-on-mac/
Stock rom downloaded from oneplus. net cannot be rooted.
Super su cannot be pushed via Twrp. Zip file fails. Any way to root the pure stock....?
sibikallikkat said:
Stock rom downloaded from oneplus. net cannot be rooted.
Super su cannot be pushed via Twrp. Zip file fails. Any way to root the pure stock....?
Click to expand...
Click to collapse
either try a different zip file or simply flash a rooted stock rom. More than likely there is something going on your end.
In these situations you have to search and also ask yourself am I the only one with this problem and if so then what am I doing differently. Then start from scratch and work it out. There are multiple TWRP's different zip files check md5, I mean its more than just posting a question on xda.
I used this tool without any problem
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
You managed to have twrp so it may be supersu files. Supersu is included in the tool.
Le_Zouave said:
I used this tool without any problem
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
You managed to have twrp so it may be supersu files. Supersu is included in the tool.
Click to expand...
Click to collapse
This tool I tried.It says SuperSu is pushed and turns green...But after I boot the phone no supersu is found in app drawer...
This problem is with the latest stock 3.2.1 downloaded from oneplus.net
playya said:
either try a different zip file or simply flash a rooted stock rom. More than likely there is something going on your end.
In these situations you have to search and also ask yourself am I the only one with this problem and if so then what am I doing differently. Then start from scratch and work it out. There are multiple TWRP's different zip files check md5, I mean its more than just posting a question on xda.
Click to expand...
Click to collapse
Sorry sir,
Tried different zips of Supersu including the latest 2.76 stable...But no success. I switched to Freedom Os ,the rooted rom.
But many prefer to use the pure stock rooted...Thats 3.2.1 from oneplus.net. This is stubborn and prevents rooting.SuperSu can be flashed via TWRP but no SuperSU icon found in APP drawer..Also the system stands unrooted...
After the tool says the zip is pushed to the phone, you need to go in twrp and flash the zip. I have the latest stock too and the supersu included in this tool worked just fine in twrp.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yeah it has to be a step your missing your not telling us about. Hopefully you sort it out but if not start from scratch and follow directions exactly and let us know