Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.
I used the root method from CF-autoroot.
Once it failed I pulled the battery and flashed SuperSU-v2.19zip..
Now I get the binary update notification...
If I can just get some help from anyone that knows what they are doing that would be awesome..
Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing
BTW: I got the 64 su file from root junky...
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
samep said:
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
z31k said:
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
Click to expand...
Click to collapse
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Edit 2: if using custom kernel, don't need liboemcrypto.so
Sent from my SM-N910P using Tapatalk
samep said:
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
pbedard said:
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
The OP says he can flash mods. I'm assuming here and you know the consequences of such, but thought it also possible to mount system and use the TWRP file manager to edit system.
I'm still OB7 but following with interest regarding the root of OG5 and recovery methods.
Edit: If L Speed Mod flashes successfully, default mode should give more freedom if using ADB and it doesn't need root. I think it's all shell scripts. (ADB Insecure required for booted mode adb access.)
Sent from my SM-N910P using Tapatalk
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Ill look into it flashing l speed mods.. maybe that can be a door... I know that Selinux and fix permissions can be applied via TWRP. SU binaries are applied.. they were in the system folders. So su is where its supposed to be. Busybox is where its supposed to be, 2.49 does not work just older builds. Its all a matter of figuring out how to update binaries??
pbedard said:
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I would love to debloat in adb shell, however whenever I make a shell environment the device will not detect in adb shell. regular adb commands is fine, just when I start shell.. Suggestions?
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
z31k said:
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
Click to expand...
Click to collapse
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
samep said:
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
z31k said:
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
Click to expand...
Click to collapse
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
samep said:
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, that's the thing. I need all the help i can get. I posted over here because you guys have development. I have been watching your forum like a hawk, just waiting for you guys to get 5.1.1. Lol....We dont in the sprint note edge forum. But i figure its the same hardware.
So with all that said, i really appreciate your help. Its a great step at a fresh direction.
Related
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back
S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App
wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.
Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App
Will this mod posted at the original inc. work for our phone as well?
http://forum.xda-developers.com/showthread.php?t=1621808
Before I flashed it I figured I would see if anyone tried it out.
It shouldn't hurt anything to try it. Just do a backup in recovery first then flash. If you have any problems you can easily go back that way. Only way to know for sure if it'll help with battery life is to try it. There should be no ill effects with doing so. Worst case scenario would be a bootloop in which case you have your backup. Next worse case... It does nothing for you.
Sent from my ADR6350 using xda premium
Ok Cool. I wasn't sure what negative things could happen if I flashed it. Thanks for clearing that up for me. I'm going to flash it tomorrow and see how it goes.
Just fyi, I went a head and set it up on mine with no issues. Can't say anything for battery life yet, too early to tell.
Sent from my ADR6350 using xda premium
I just flashed it on MIUI no problems, but I don't think it is compatible with this rom.
I ran "grep busybox /init.rc" in terminal and it is giving me permission denied.
I am assuming MIUI is not support "init.d".
Do you know if your cm 7.2 is supported by this?
kubes069 said:
I just flashed it on MIUI no problems, but I don't think it is compatible with this rom.
I ran "grep busybox /init.rc" in terminal and it is giving me permission denied.
I am assuming MIUI is not support "init.d".
Do you know if your cm 7.2 is supported by this?
Click to expand...
Click to collapse
Type su before the command. I believe miui has init.d support though. I've never run it myself though. But I think it does.
Sent from my ADR6350 using xda premium
CondemnedSoul said:
Type su before the command. I believe miui has init.d support though. I've never run it myself though. But I think it does.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Just did the su command and still giving permission denied.
Maybe I need to fix permissions, I'm not too sure.
kubes069 said:
Just did the su command and still giving permission denied.
Maybe I need to fix permissions, I'm not too sure.
Click to expand...
Click to collapse
When you put in the command, did you get a superuser popup or permission granted notification?
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yes, I got the pop up and i granted it access. I was still getting permission denied in some lines when i typed in the codes in the terminal.
It made minimal improvement if any at all for me.
Amphibliam said:
It made minimal improvement if any at all for me.
Click to expand...
Click to collapse
What rom are you running?
And did you run those codes to see if it stuck? I'm just trying to make sure I'm doing this right lol.
kubes069 said:
Yes, I got the pop up and i granted it access. I was still getting permission denied in some lines when i typed in the codes in the terminal.
Click to expand...
Click to collapse
Probably means your ROM doesn't support init.d, the OP in the thread you linked said to use dsixda's kitchen, try finding that with google.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
I'm writing this short little post to give an idea of a good starting point for the HTC One as it stands right now. There are a lot of threads and they get out-of-date quickly (just as this one will). I just picked-up my new HTC One on Tuesday of last week from a Verizon store. This just gives a fresh idea of what can be done to get started on it.
Obviously you're running these instructions at your own risk. I'm not responsible for you bricking or otherwise damaging your phone. Doing these things may (will) void your warranty and may prevent you from being able to return your phone. Run these things at your own risk.
AN IMPORTANT PUBLIC SERVICE MESSAGE: When you get your phone out-of-the-box, it's probably going to offer you an OTA update. I recommend that you do not accept an OTAs as this usually makes this process even harder than it has to be. Verizon hates having us enjoy our devices!
First, let me describe my goals here:
Unlock the bootloader and obtain S-OFF
Install a custom recovery (CWM)
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
Get wireless tether working without jumping through tons of hoops.
I'll go through the list and just describe what I did:
Unlock the bootloader and obtain S-OFF
This was fairly straightforward. Rumrunner has an excellent package that does this very easily. I checked my phone's ROM version and saw that I was running 1.10.605.15. I grabbed the Rumrunner package from here for that level.
In looking over the requirements for Rumrunner, it wanted 32-bit Linux and I run 64-bit. The easiest way to solve this problem for me was to just boot to a Xubuntu 12.10 32-bit ISO that I had on my system. If you have it burned, just boot to it. If you don't (like me), use grub2 (if you have it) and boot the ISO directly. Either way, get yourself into a live environment.
Once the ISO was booted, I got it on the network and installed adb and fastboot from the Ubuntu repositories (after I did apt-get update, of course). Connect the phone via USB and enable USB debugging:
Go to Settings -> About -> Software Information -> More
Tap the Build number field 7 times
Back up to the Settings screen again and you'll now see Developer options
Enable USB Debugging under the developer options
Verify that you can see the device on your system using adb (this should result in a device being listed by serial number):
Code:
sudo adb devices
Follow these instructions for executing Rumrunner. It worked perfectly as described. Once complete, the phone was unlocked and S-OFF with a stock ROM.
Keep the live environment up as it will just make life easier to do the next steps.
Install a custom recovery (CWM)
I pretty much always use CWM if I can. I saw that there were no issues with doing that on this phone (like there are on other phones like the Rezound). I grabbed version 6.0.4.7 of CWM (non-touch) for the HTC One from here. If I recall correctly, the device is booted back into the stock ROM at this point. Make sure your device is still connected USB and has USB debugging enabled.
Reboot into the bootloader from the command prompt:
Code:
sudo adb reboot bootloader
Once the phone comes up, it should be at the Fastboot screen (it should actually show Fastboot USB). Verify that you can see your phone with fastboot (should get your device serial number again):
Code:
sudo fastboot devices
Now you can flash CWM recovery using this command from the directory where you stored the CWM file you downloaded (such as the one I provided a link to):
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.7-m7vzw.img
After the flash is successful, reboot back into the bootloader:
Code:
sudo fastboot reboot-bootloader
Now you can choose BOOTLOADER and then RECOVERY to get access to CWM. If you really want to, you can take a backup of the stock ROM at this point. I did not because I thought it was a waste of space. I just booted back into the stock ROM and disabled USB debugging so I could stick a real ROM on the system.
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
I really wanted to give this HTC Sense 5.0 a run. I've used Sense before and it wasn't awful. This seemed less annoying than previous versions (plus, there are some nice camera features which are important to me). For that reason, I selected the stock 2.10.605.1 rooted, deodexed, debloated ROM from this thread. I also opted to do the firmware upgrade at the same time, so I grabbed the firmware for the 2.10.605.1 as well.
The instructions in this thread are easy to follow so just use those. Just a note though: Flash the firmware and ROM at the same time if you're going to do firmware at all. Instructions are in the second post on that thread.
Once the ROM was up, I did my typical setup of accounts and such. The last thing I needed was Wireless Tether support.
Get wireless tether working without jumping through tons of hoops.
I don't particularly care how I get wireless tethering (infrastructure mode) as long as it works on my phone reliably. I first tried the stock tethering as this sometimes works because the authors of "stock" ROMs sneak hacks into their ROMs. It did not work. I then tried messing around with the WiFi Tether TrevE Mod that I saw recommend a few times but this didn't pan out on the 2.10.605.1 ROM (I temporarily went to 1.10.605.15 and it worked; I went back to 2.10.605.1 when someone recommended the solution below):
http://forum.xda-developers.com/showthread.php?t=2576548
I flashed this package onto my system and, without a problem, built-in wireless tether started working. I've seen no problems.
Getting my one today. I guess I will give this a go tonight. Thanks. Anything else to look for? Thanks.
Sent from my HTC Rezound.
Rumrunner worked perfectly fine for me on Ubuntu 12.1 64 bit both times I ran it. I would try it first before downloading s 32 bit distro if 64 bit is already installed.
Sent from my HTC6500LVW using Tapatalk
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
onthehole said:
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
Click to expand...
Click to collapse
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks.
No problem.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
No problem.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
onthehole said:
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
Click to expand...
Click to collapse
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
onthehole said:
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
Click to expand...
Click to collapse
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
onthehole said:
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
Click to expand...
Click to collapse
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
will do. thanks.
onthehole said:
will do. thanks.
Click to expand...
Click to collapse
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
onthehole said:
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
Click to expand...
Click to collapse
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
disconnecktie said:
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
onthehole said:
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
Click to expand...
Click to collapse
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
disconnecktie said:
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
understood. I will flash fresh if things aren't up to par.
Morning all!
Possibly a silly question but I run 100% stock because of one app that will not work when rooted - Sky Go (a UK video streaming app). There is nothing that has got it to work when rooted so I've not bothered. I don't even need root access these days. BUT I'd like to give CM11 a go and I was wondering if you can turn off the root access in the ROM and then use a stock kernel and it would still boot/run?
If not, not to worry but seeing as CM11S does't have root it'd be nice to see the same available for other phones and not just the OnePlus One
I guess you could run the super su zip in recovery and then full unroot it through the app. Not sure if you'll run into any issues in cm without root, never tried it before
Sent from my HTC One_M8 using XDA Free mobile app
otariq said:
I guess you could run the super su zip in recovery and then full unroot it through the app. Not sure if you'll run into any issues in cm without root, never tried it before
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Kinda what I was thinking, it's the kernel I'm more worried about as that needs to be a secure kernel otherwise the app won't work
Might just have to give it a try...
EddyOS said:
Kinda what I was thinking, it's the kernel I'm more worried about as that needs to be a secure kernel otherwise the app won't work
Might just have to give it a try...
Click to expand...
Click to collapse
I take it root cloak doesn't work?
grentuu said:
I take it root cloak doesn't work?
Click to expand...
Click to collapse
No, otherwise I would've used it
http://repo.xposed.info/module/com.devadvance.rootcloak
App: Sky Go - BSkyB - https://play.google.com/store/apps/details?id=com.bskyb.skygo
Method: Most likely detects root via native library (built with Android NDK). Unsure of exact method, but the Java portion of the app contains "VGDRM_STATUS_DEVICE_IS_ROOTED = -41942891", and based on the library name, it's a safe bet.
Relevant Files: libvgc.so
I think Sky Go looks for more than root doesn't it? I think it looks at kernel and software version also, so if you are running anything "custom" it instantly thinks you are rooted.
I just set up a separate rom on my Nexus 7 (Using multirom) for this exact reason.
Sent from my Amiga 500 using Workbench
Basicly the title explains it ive tried a few apps and the terminal commands. And no matter what always get app not installed used sys app installer and its telling me system cannot be mounted rw
Any screenshots?
Sent from my SM-G930F using Tapatalk
bender_007 said:
Any screenshots?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I was trying the g5 camera flashed it in flashfire and basicly deleted stock camera and wont install new one or orig lg one back. No biggie i got backups. Just figured if i could fix it first
TheMadScientist420 said:
I was trying the g5 camera flashed it in flashfire and basicly deleted stock camera and wont install new one or orig lg one back. No biggie i got backups. Just figured if i could fix it first
Click to expand...
Click to collapse
Try mounting the system as RW via terminal emulator (worked for me)
bender_007 said:
Try mounting the system as RW via terminal emulator (worked for me)
Click to expand...
Click to collapse
Im assuming that itz mountin rw im not getting no errors there. But still doin apk not installed
I had different mounting issues depending on installed kernel or even supersu version
Sent from my SM-G930F using Tapatalk
Are you on systemless root with SuperSu?
jobella said:
Are you on systemless root with SuperSu?
Click to expand...
Click to collapse
I dont believe so i am a ls991 sprint. Have to load a rooted system image with dd commands for root.
i keep it on lolipop for root reasons. I aint done it yet ive been messin with my gs6 and a new rom settin it up and all i gotta do is restore my system through dd commands also as i have no twrp. Its more of a wonder y. ive installed plenty of apps in system. Not a major issue like i said i can restore. But if i can fix without why not.
And as previous post said i do have mount rw.
Im in a limbo on what device i want to use. Ive been a trusted soldier in the g series. Even with all the problems. I may get a g5 in the future even got my g4 a vr set goin and wireless qi charging. But man. I can overclock my s6 hecta core big cores to 2.6 ghtz. And small cores to 1.u ghrts. Figured out the bat drain. Biggest thing is i want knock on my s6. And none have compared to lgs knock on.