Ok so I have a friend that bought the pixel via verizon, and took it onto Tmobile. Trying to unlock the hotspot tether via build.prop edit.
The Pixel (Was on Android 7.1) has been unlocked via dePixel8 and rooted via Chainfire. Root Checker also verifies this.
However, whenever we try to access the build.prop through Root Explorer, ES File Manager, and the like, SuperSU prompts and gives root access but no way to save an edited build.prop.
I tried mounting /system as R/W via multiple adb commands which were unsuccessful, I think due to the new partition scheme. I don't remember the commands I used, I googled for them and have since closed those tabs.
Thought that maybe the root messed up somehow so re-did the Chainfire root with no change to the system, in fact it even seems like root is even more broken with ES File Manager no longer able to view the root directory.
We are currently downloading the google edition NDE63V Factory Image in hopes of getting rid of any hidden Verizon security "features" that may be causing this issue along with getting rid of the Verizon bootloader.
All OTAs will be sideloaded after we put on NDE63V Image to protect from a Verizon bootloader being placed back onto the phone.
Has anyone else with Verizon Pixel had issues with root features and troubles mounting anything as R/W? Any ideas on a possible fix without needing to flash NDE63V?
There's no Verizon-specific build.prop security feature to my knowledge. The command "mount -o rw,remount /system_root" should work. If it fails, can you post the error you get?
dnbonds said:
Ok so I have a friend that bought the pixel via verizon, and took it onto Tmobile. Trying to unlock the hotspot tether via build.prop edit.
The Pixel (Was on Android 7.1) has been unlocked via dePixel8 and rooted via Chainfire. Root Checker also verifies this.
However, whenever we try to access the build.prop through Root Explorer, ES File Manager, and the like, SuperSU prompts and gives root access but no way to save an edited build.prop.
I tried mounting /system as R/W via multiple adb commands which were unsuccessful, I think due to the new partition scheme. I don't remember the commands I used, I googled for them and have since closed those tabs.
Thought that maybe the root messed up somehow so re-did the Chainfire root with no change to the system, in fact it even seems like root is even more broken with ES File Manager no longer able to view the root directory.
We are currently downloading the google edition NDE63V Factory Image in hopes of getting rid of any hidden Verizon security "features" that may be causing this issue along with getting rid of the Verizon bootloader.
All OTAs will be sideloaded after we put on NDE63V Image to protect from a Verizon bootloader being placed back onto the phone.
Has anyone else with Verizon Pixel had issues with root features and troubles mounting anything as R/W? Any ideas on a possible fix without needing to flash NDE63V?
Click to expand...
Click to collapse
Might as well use the latest factory image. (7.1.1 build NMF260)
I updated to the latest build with a clean install. Installed TWRP. Rooted with SR5. Then did the build.prop edit and it's working fine for me. (Verizon Pixel on Verizon's network)
Related
There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary
I have had my tablet rooted since I got it pre-4.2.1. I was trying to setup TWRP as I finally decided to ROM my device and ran the unlock tool.
However, once I got past that and tried to use goomanager and TWRP manager, I realized apps were not being provided root any longer. However, the old apps that were approved in Superuser continue to get root and think that they have root, such as Titanium Backup, SManager, ES Explorer, etc. They continue to function as expected. However in SuperUser the logs have not updated in quite a while.
I've done several steps and reviewed a few related threads. Changing the prompt settings have not done anything, and I've tried several combinations of setting it to allow, setting it to prompt, rebooting etc. To confirm root is actually working I ran SManager and ran /system/bin/su which does work, and causes SuperUser to show new root access. Along the lines, I've nuked my dalvik cache using SManager and rebooted.
However, nothing else updates the logs, and new apps do not get root. Based on some other thread, I used voodoo OTA rootkeeper to remove root and then ran motochopper. Root came back, but continues to have the same behavior. SuperUser is unable to update itself, although it does show the binary as up to date. When I try to run an update anyway, it fails at the getting root step. SuperSU, rootchecker, android root toolkit all fail.
I am hoping I can figure out how to fix this, even though I unlocked the tablet, I'm traveling and not in a position to flash in TWRP. Since running SU works and previously approved apps also work - I think there is someway to restore full root capabilities. Any suggestions are appreciated.
ASUS Transformer Infinity TF700 - rooted/stock
Motorola ATRIX 4G - Rooted/Currently Stock/No longer in use - anyone need a guinea pig?
Motorola ATRIX2 - vanilla
ASUS Transformer TF101 - now vanilla and given to the wife
Really I swear I've had lots of roms on these devices at other times.
I've got an Nvidia Note and the Shield. I noticed the Note has been mentioning an OTA update which likely means my Shield is due for it also. Since both are rooted, is it okay to update or will I wind up losing root?
I noticed on the front end that updating the shield OTA is playing hell with the SD cards. I don't have one in there yet but does the new OTA force you into having a root priv. file browser like root explorer?
NapalmDawn said:
I've got an Nvidia Note and the Shield. I noticed the Note has been mentioning an OTA update which likely means my Shield is due for it also. Since both are rooted, is it okay to update or will I wind up losing root?
I noticed on the front end that updating the shield OTA is playing hell with the SD cards. I don't have one in there yet but does the new OTA force you into having a root priv. file browser like root explorer?
Click to expand...
Click to collapse
I don't know about the Note, but you will lose root by updating the Shield. I had no problems re-rooting it though (I rooted mine by loading CWM Recovery through fastboot and installing SuperSU from there; I don't know if the insecure boot method still works).
The Shield's latest OTA brings KitKat which restricts write privileges to external SD cards. If I'm understanding it correctly, it lets an app write to its own folder on the card, but no where else. This breaks general access apps like file explorers. To get around that, there's an app on the Google Play store called SDFix which removes these restrictions (requires root since it modifies system files).
redphazon said:
I don't know about the Note, but you will lose root by updating the Shield. I had no problems re-rooting it though (I rooted mine by loading CWM Recovery through fastboot and installing SuperSU from there; I don't know if the insecure boot method still works).
The Shield's latest OTA brings KitKat which restricts write privileges to external SD cards. If I'm understanding it correctly, it lets an app write to its own folder on the card, but no where else. This breaks general access apps like file explorers. To get around that, there's an app on the Google Play store called SDFix which removes these restrictions (requires root since it modifies system files).
Click to expand...
Click to collapse
You did an adb push type thing in recovery or just flashed an su.zip type thing?
I didn't ADB push. I booted CWM recovery through fastboot (didn't flash it, I didn't want to bother removing it for future updates), chose the "choose zip from external sd" option, and installed this from my external SD card. I did have to hit the Play Store and download the SuperSU app from there as well, but it worked.
This post here is pretty much what I did minus the flashing part.
redphazon said:
The Shield's latest OTA brings KitKat which restricts write privileges to external SD cards. If I'm understanding it correctly, it lets an app write to its own folder on the card, but no where else. This breaks general access apps like file explorers. To get around that, there's an app on the Google Play store called SDFix which removes these restrictions (requires root since it modifies system files).
Click to expand...
Click to collapse
I had read about KitKat breaking file explorers but honestly I didn't notice it make any changes to mine, think I'm using File Explorer Pro or something but it still lets me make dirs on SD, move/copy stuff, extract files, etc so not sure exactly what it was supposed to break? I'm not rooted either nor know how to do so yet :/
redphazon said:
I didn't ADB push. I booted CWM recovery through fastboot (didn't flash it, I didn't want to bother removing it for future updates), chose the "choose zip from external sd" option, and installed this from my external SD card. I did have to hit the Play Store and download the SuperSU app from there as well, but it worked.
This post here is pretty much what I did minus the flashing part.
Click to expand...
Click to collapse
Thanks all. I'll pull down the OTA soon and see if I can recover root. I noticed OTA Rootkeeper wasn't thrilled because my shield has SuperSU and not superuser. Even though the app mentions being ok with SuperSU, it doesn't want to move along.
I rooted my Sheild by unlocking bootloader, then pushing the image with adb. I updated to Android 4.4 and root was gone, however bootloader remained unlocked. I pushed the image again and all is well.:laugh: So go ahead and update!
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
Android 10 has this messed up file system that does not allow any writing of the system files. While I have root neither Root Explorer or any other third party apk can force it over. I also cannot install any application with Root Explorer. What's the good of root if we can't actually mod our own system files?
Also, since debloating everything and removing google everything, I can't use instacart anymore. It says I need Google Play Services. This NEVER was an issue on my Moto G7 Power.
At the very least is there a tool where I can unpack Super.Sparsechunk files and then repack them so I can flash them as stock via fastboot. All I want to do is delete the stock ringtones on this phone and replace them with my own .ogg files (as I've done on every Moto I've ever had). Thanks.
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
mingkee said:
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
Click to expand...
Click to collapse
I did all that. It still will not go to R/W. This seems to be an Android 10 issue.
Here you go my friend. Enjoy!
lebigmac said:
Here you go my friend. Enjoy!
Click to expand...
Click to collapse
Your method as of now is not working.
It's working fine on my Xiaomi (which is A slot only device) but you are right. The current version is not as universal yet as I'd like it to be. There seems to be an lpmake error at the very end of the script for those with A/B slot device.
Don't worry I am working very hard on identifying and fixing the error.
Soon your system shall be RW!