I have my Nexus Player with TWRP and AOSP kernel installed, and it is rooted.
So, I was so annoyed with the monthly forced OTA updates. I had been trying so many things, and finally it worked!!
I simply added the following lines in the script which runs when booting;
su -c am force-stop com.google.android.gms/.update.SystemUpdateGcmTaskService
su -c am force-stop com.google.android.gms/.update.SystemUpdateService
su -c am force-stop com.google.android.gms/.update.SystemUpdateActivity
su -c am force-stop com.google.android.gsf/.update.SystemUpdateActivity
su -c am force-stop com.google.android.gsf/.update.SystemUpdatePanoActivity
su -c am force-stop com.google.android.gsf/.update.SystemUpdateService
su -c pm disable com.google.android.gms/.update.SystemUpdateActivity
su -c pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
su -c pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
su -c pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
su -c pm disable com.google.android.gsf/.update.SystemUpdateActivity
su -c pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
su -c pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
su -c pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
I'm not sure if the former part and the latter are both necessary because I didn't wanna get bothered to wait for daily OTA update reboot to check.
Hope this helps others.
Does this prevent the ability to update from play store? Also how exactly did u make/add this script to the nexus player? Thanks!
*edit* I emulated init.d with kerneladuiter and pasted your scrips to a profile I made called 99user. Run script before hand and showed all of them as disabled and great to see I can still download and update apps via play store...... Now to give it few days and see if any update tries to happen. Thanks bud! Was on newest 7.1.2 so will c what happens.... Don't want Oreo on np
Hello,
I would like to know exactly where do I put this script at.
Thanks,
k-bull said:
Hello,
I would like to know exactly where do I put this script at.
Thanks,
Click to expand...
Click to collapse
In kernelauditer, which you can dl from playstore, you select emulate init.d than also in the menu you can make a script, paste the above commands and name the script..... Think tho i still had my np booting into twrp, not booting automatically now that i uninstalled playservices updates, which also fixed the control from not working properly
Hi All,
On 7.1 - automatically downloading Oreo so trying the above.
downloaded kernelauditer. Added the script. emulated init.d
Does this stop an existing download from completing or do I need to do something additional? Once saving the script, is anything else required?
I just did it slightly different and so far so good... I flashed the factory 7.1.2 image, TWRP and Magisk. I started up, registered and immediately disabled Wifi before it could update to Oreo. I then opened ADB shell and just hid the update app.
su -c pm hide com.google.android.gms/.update
su -c pm hide com.google.android.gsf/.update
Nevermind... Just did it anyhow.
Hey all, thanks a million for the hard work and the script provided. Great tip great job. On my LG Aristo 2 through Metro PCS, I've found in the Developer Options the ability to uncheck "Automatic System Updates" which can potentially save a ton of headache should the update download and store into my phone cache anyway (merely a system update, 'security patch' to botch phone modders I'd assume :/ ) Anyway, I have TWRP installed and don't want to use LG Bridge for the 3rd time just because that stupid update decided to force itself into my life lol. Great job again and a much thanks!
PS has anyone had any luck with putting the old "FOTAkill.apk" into the /system/app folder, or is that a dated method?
Related
Built a version of Superuser.apk from the github source to make preferences work. All I've done is remove the code that checks for a new version. It works perfectly now.
http://dl.dropbox.com/u/19946299/Superuser.apk
Directions:
1. Uninstall your current version of Superuser with:
adb remount /system
adb shell rm -f /system/app/Superuser.apk
2. Install new one using adb
adb install Superuser.apk
Or
adb push Superuser.apk /system/app/Superuser.apk
Alternatively you can remove your current Superuser.apk with a root system file manager and install the new one the same way.
I've also put in the issue with ChainsDD on his issues list and where I found it, seems to be to do with the waiting thread when it requests the current su binary version.
Thanks for the post. I'm wondering, and yes I've searched plenty on XDA and RootzWiki, will this fix su issues all around? For example, using TB 4.0.2 sends my CM9 TP into a reboot. I've read this may be an issue with Busybox.
Any insight anyone?
I don't think it's busybox and the exact point that Superusers waits for the su binary to return the version number. The actual command works 100% OK, you can do the exact same commands in shell and it's fine. It seems to be something to do with the actual java exec thread. TB has the same issue, where as other backup apps (ultimate backup) do not, and they still call su binary. I'm still trying to figure it out.
GavChap said:
adb shell rm -f /system/Superuser.apk
Click to expand...
Click to collapse
change to:
Code:
adb shell rm -f /system[COLOR="Red"]/app[/COLOR]/Superuser.apk
thanks
edit: and i had to push the su app instead of install
Good job...works nice. Did you commit ur change to source so future builds will be free from this bug? If not, commit to either evervolv or cm...or detail the change in source and I can.
Thanks
Sent from classicnerd ICS Touchpad
Thanks....this did not fix the crash/Reddit issue with TiBU current version...installed and launched TiBU, and it froze and then rebooted my TO, tried it two times.
Working now. Reset it and installed good to go
Redflea said:
Thanks....this did not fix the crash/Reddit issue with TiBU current version...installed and launched TiBU, and it froze and then rebooted my TO, tried it two times.
Click to expand...
Click to collapse
This is a workaround rather than a fix. The su binary is fine. There is a kernel issue that causes the crash. The logs I have state it's with the msm ioctl code.
There are other root using apps that don't crash at all.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
TMan459 said:
Thanks for the post. I'm wondering, and yes I've searched plenty on XDA and RootzWiki, will this fix su issues all around? For example, using TB 4.0.2 sends my CM9 TP into a reboot. I've read this may be an issue with Busybox.
Any insight anyone?
Click to expand...
Click to collapse
This doesn't fix the SU problems, just the Superuser front end.
Thanks for the tips.
I replaced my Superuser.apk with yours and now I can get into the settings without FC.
I used root explorer to replace the files but I also had to changed the permissions of your version of the superuser.apk to match the other files (rw-r--r--) to work properly.
One thing I noticed that even though I can get in to settings in SU, I still cannot update the binaries. If scans for updates but when I ask it to actually update the binary, it reboots the TP.
Thanks anyways...
There is a bugfix kernel coming from the CM team soon that'll fix these issues, I've tested the fix on my kernel and it's working fine.
So I just updated my kernel (bricked-kernel 2.6.35) to fix the TIBU issues and as a side benefit, my SU no longer reboots the TP when I try to update the binaries. It finds the update and tries to apply the update. It returns an "update failed" message, but it no longer hard reboots my TP.
I think it's getting closer to being perfect... ^_^
You can try my kernel if you like
http://dl.dropbox.com/u/19946299/uImage.CyanogenMod
download onto your computer, boot into ClockworkMod
Then do the following using adb on the computer
adb mount /boot
(optional) adb shell mv /boot/uImage.CyanogenMod /boot/uImage.CyanogenMod.old
adb push uImage.CyanogenMod /boot/uImage.CyanogenMod
adb umount /boot
adb reboot
GavChap said:
You can try my kernel if you like
http://dl.dropbox.com/u/19946299/uImage.CyanogenMod
download onto your computer, boot into ClockworkMod
Then do the following using adb on the computer
adb mount /boot
(optional) adb shell mv /boot/uImage.CyanogenMod /boot/uImage.CyanogenMod.old
adb push uImage.CyanogenMod /boot/uImage.CyanogenMod
adb umount /boot
adb reboot
Click to expand...
Click to collapse
Is this based off just the CM team or do you also use the commit's from Bricked-Kernel?
I had to re-copy the superuser.apk after the alpha 0.5 update. I will say with the 0.5 update and this adjustment, all is well. Couldn't be happier.
Best thing to do about Superuser if you get force close on setting in CM9A0.5 is to remove the Superuser app using Titanium Backup or root explorer. Then install the one from the Android Market, settings works 100% now. I think the one in CM90.5 is an older version.
Good tip! Worked for me on .5 and can now use TB from market. Thanks.
hey guys I removed some systemapps and now I cant install the new row update. can some one please upload a titanium backup
thanks
titanium backup won't work for system apps. you will need a system dump. which apps do you need? i have a dump but i won't upload the whole dump cause its about 1 gb.
ok. thanks for the quick reply. im not sure but it sholud only be the music app. it would be great if you could upload it.
just unpack it and copy both files into the /system/app folder with i.e. rootexplorer etc.
here i uploaded nearly the whole dump:
System Dump
i am the same don't know how to do now.
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
@bananenlarry
I delete some app after root,then I unroot for some reason.
I can't not get root again,and also can not update OTA2 because missing APP.
waht can I do now?
@feskey
how did you unroot? did you delete superuser.apk from /system/app? then download Superuser from market again. because the su file from /system/xbin/ should still be there.
@bananenlarry
Unroot by following command.Su was clean up.
Instructions
1. Follow instructions to set up ADB.
2-Run "adb shell" from a command prompt.
3-In the ADB shell, type the following commands:
su
(this will cause a prompt to come up on the phone asking you to grant root permissions, accept this)
Then, back in ADB shell:
mount -o rw,remount /dev/block/system /system
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/bin/su
omg you really unrooted your device thought you just deleted the superuser.apk. i don't know exactly how the root exploit works but as i know it uses a lenovo app to do so. if you also deleted that app, root isn't possible in your case. you will have to wait until there will be another method for rooting.
This did not go exactly as I had planned but it ended up ok anyway and I learned some.
I am using a rooted stock rom. First, my idea was to prevent the auto update to 6.3. Second, I wanted to see if it was possible to somehow preserve root so that I wouldn't have to re-root after the update, because I am not really thrilled by the idea of installing a new boot loader and so on; I would prefer to make the minimum modifications necessary to do what I need.
The first goal appeared to be well-served by using droidwall. I used whitelist mode and blocked everything that I couldn't tell had an obvious need to access the net. I posted more detail here. From the time the update started going out until today when I had time to actually try my update, I did not receive the update automatically. So that appeared to work.
Next, my idea was to simply make a copy of /system/xbin/su to a place that wouldn't get overwritten by the update.
# mkdir /data/lunchmeat
# cat /system/xbin/su > /data/lunchmeat/salami
# chmod 6755 /data/lunchmeat/salami
The idea being that since it's still setuid root, I'd be able to execute it and become root after the update. (I just picked a silly name in case something looked for su and blew it away).
So, I turned off wifi, disabled droidwall, manually updated (copied the updates into kindleupdates and so on) and after it rebooted, I opened the terminal app and tried to execute my salami binary. I got permission denied, and the superuser app said that superuser permission was denied on the terminal app. Hmmm....
Couldn't figure out why it was behaving that way so I thought I'd try adb root, and whadya know, I had a root shell.
remounted /system read-write, copied su back into /system/xbin, renamed /system/bin/check_rooted to /system/bin/check_rootedx, created an empty executable /system/bin/check_rooted, and rebooted...
...and everything is (rooted) as it was before. I re-enabled droidwall. google play seems to be working.
Why did 'adb root' work for me after the update? That might be a good question to answer, since it could make the re-rooting process much simpler for people! 2 or 3 commands and you're done.
edit: ohhhhh, stupid me! /data is mounted nosuid. / seems to get blown away on every reboot, so even if I remount it read/write and put su there, it gets lost.
And, also, I just remembered that I did what jcase said in this post which is what allowed me to keep adb root working.
So, so far this idea is going nowhere.
This Method disable ota services.
steps:
-Decompress the attached file
-Execute the following commands:
<important>Please look the screen for superuser permission grant.
Code:
adb push disable_ota_for_kindle.sh /data/local/tmp/
adb shell "su -c 'chmod 777 /data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "su -c '/data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "rm /data/local/tmp/disable_ota_for_kindle.sh"
Tested in a Kindle Fire 2 (10.2.3_user_2313820
julionadal said:
This Method disable ota services.
steps:
-Decompress the attached file
-Execute the following commands:
<important>Please look the screen for superuser permission grant.
Code:
adb push disable_ota_for_kindle.sh /data/local/tmp/
adb shell "su -c 'chmod 777 /data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "su -c '/data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "rm /data/local/tmp/disable_ota_for_kindle.sh"
Tested in a Kindle Fire 2 (10.2.3_user_2313820
Click to expand...
Click to collapse
Guessing this can only be confirmed at the time of the next update for me. Currently running 7.2.2 on KFHD.
Will download and give it a go.
Thanks.
Droidwall is a good solution for this too. You can block all Apps for using the Internet connection to call "home"
This script looks to disable all OTA services. Would that not included whispersync, the personal documents service etc? it is possible that blocking all of these services may have undesired consequences to folks who value those services. That said, thanks for developing this script.
Can you provide more details on how to disable OTAs using Droidwall? I downloaded the application but I am not sure which applications I need to block or how to configure.
Sent from my KFTT using xda premium
Should I disable the system app in the center of the screenshot? Will it lock up the device if I do so?
Sent from my KFTT using xda premium
ameswilliam said:
Should I disable the system app in the center of the screenshot? Will it lock up the device if I do so?
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
I installed DroidWall and blacklist all amazon apps, but it still update to 7.2.2 version. I doubt DroidWall can off OTA update
Did you blacklist the 10000. System file seen in the attachment?
Sent from my SPH-L710 using xda premium
Ok, so I used the OP's .SH file, and then read a bit further on this thread and realized his code would disable whispersync too.
Is there any way to reverse his code? I tried to go into his code and change the word "disable" to "enable" but the file would not execute anymore. I have no idea why. I did not change the file name, but ADB keeps telling me "no such file or directory"
Can anyone please help? I'm using Fire HD 8.9 ver. 8.1.3
After i reverse the code, I will just use droidwall
Thanks for your help.
pullmyfinger123 said:
Ok, so I used the OP's .SH file, and then read a bit further on this thread and realized his code would disable whispersync too.
Is there any way to reverse his code? I tried to go into his code and change the word "disable" to "enable" but the file would not execute anymore. I have no idea why. I did not change the file name, but ADB keeps telling me "no such file or directory"
Can anyone please help? I'm using Fire HD 8.9 ver. 8.1.3
After i reverse the code, I will just use droidwall
Thanks for your help.
Click to expand...
Click to collapse
Try running each command with ADB.
I'm not familiar with the disable 'pm' command but know that services can be enabled/disabled via titanium backup. Dont know if this is the same function but you could install it and give it a go.
bryanchapman9999 said:
Try running each command with ADB.
I'm not familiar with the disable 'pm' command but know that services can be enabled/disabled via titanium backup. Dont know if this is the same function but you could install it and give it a go.
Click to expand...
Click to collapse
Yea I dont see any service that's already frozen using Titanium Backup. Can anyone else who knows what this guy's code did help me reverse it? Thanks.
This is his code:
#!/system/bin/sh
pm disable "com.amazon.dcp/.ota.OTAUpdateMessageHandler"
pm disable "com.amazon.dcp/.ota.InventoryUploadService"
pm disable "com.amazon.dcp/.ota.UpdatesLookupService"
pm disable "com.amazon.dcp/.ota.OTAService"
pm disable "com.amazon.dcp/.ota.AppStateMonitorService"
pm disable "com.amazon.dcp/.ota.CheckForOTAUpdatesService"
pm disable "com.amazon.dcp/.ota.ViewUpdateActivity"
pm disable "com.amazon.dcp/.ota.OTAStatusActivity"
pm disable "com.amazon.dcp/.ota.ResetOTAMessageHandler"
pm disable "com.amazon.dcp/.ota.InventoryUploadService$InventoryUploadReceiver"
pm disable "com.amazon.dcp/.ota.UpdatesLookupService$MountStatusChangedReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTAWakeupReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTADedupeReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTAInstallNowReceiver"
Disable OTA Updates - Kindle Fire 7" HD
Very well thought out script.
On my Kindle Fire 7" HD all I did was moved /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
So far no updates, still on 7.2.2
Thanks!
thanks Bro for sharing.just wanted to feedback after doing these procedures.my kindle fire HD 7" is not updating anymore.i give it two thumbsup!now i still have the same build 7.2.2 for almost more than a month even if Amazon has the newest build 7.2.3 thanks alot.it really helps
Thanks for the script. Looks like it worked ok for me...Just wondering about the whisper sync deal? Does it still work"
Whisper Sync Disabled
ninjabeaver said:
Thanks for the script. Looks like it worked ok for me...Just wondering about the whisper sync deal? Does it still work"
Click to expand...
Click to collapse
ninjabeaver,
This script does disable Whisper Sync which is why we had our developers redesign a scipt to remove the OTA Services
only. Here is the less aggressive version:
http://forum.xda-developers.com/showthread.php?t=2086450
when we developed the attached script we were very careful to only effect OTA and no other services. We also wrote
an enable script for the people who need to send back there Kindles for repair.
Right on thanks..I hadn't seen that thread before.
Sent from my KFTT using Tapatalk HD
prokennexusa said:
Very well thought out script.
On my Kindle Fire 7" HD all I did was moved /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
So far no updates, still on 7.2.2
Click to expand...
Click to collapse
Hows it going, did you just move otacerts.zip and not block it tru droidwall?
prokennexusa said:
ninjabeaver,
This script does disable Whisper Sync which is why we had our developers redesign a scipt to remove the OTA Services
only. Here is the less aggressive version:
http://forum.xda-developers.com/showthread.php?t=2086450
when we developed the attached script we were very careful to only effect OTA and no other services. We also wrote
an enable script for the people who need to send back there Kindles for repair.
Click to expand...
Click to collapse
If I had used this script on my KF2 but now have installed TWRP and installed new ROM, would I need to run this again ?
Does this script prevent syncing with google play?
I rooted my kindle fire 2 and I ran this script. I uploaded songs onto google play music, but i'm unable to find songs I'd uploaded to the site.
Is it because of this script that google play is unable to sync with my kindle?
Thanks
julionadal said:
This Method disable ota services.
steps:
-Decompress the attached file
-Execute the following commands:
<important>Please look the screen for superuser permission grant.
Code:
adb push disable_ota_for_kindle.sh /data/local/tmp/
adb shell "su -c 'chmod 777 /data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "su -c '/data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "rm /data/local/tmp/disable_ota_for_kindle.sh"
Tested in a Kindle Fire 2 (10.2.3_user_2313820
Click to expand...
Click to collapse
Good afternoon:
Is it possible to provide this service in an APK?
This would allow the user to simply install the APK and then select enable or disable OTA as required?
The User would not have to know anything about ADB and related commands.
If I knew how to create APK apps I would give it a try.
Regards
So I'll update randomly...
boot.img and recovery.img -> https://drive.google.com/file/d/0B5QYBzdG6RuyZy1TSHc2VDVhY2M/view?usp=sharing
temp root:
Code:
adb push root /data/local/tmp
adb push wpoff /data/local/tmp
adb push fbunlock /data/local/tmp
adb push recovery.img /data/local/tmp
adb push boot.img /data/local/tmp
adb shell
$ [COLOR="Red"]chmod 755 /data/local/tmp/root[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/wpoff[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/fbunlock[/COLOR]
$ /data/local/tmp/root
...
#
defeat WP:
Code:
# /data/local/tmp/wpoff --unprotect-all
check WP status(optional):
Code:
# /data/local/tmp/wpoff --dump
If you see it's all zeroes there it means good, or if there are many 5555 it means NG.
unlock bootloader:
Code:
# /data/local/tmp/fbunlock
install TWRP and patched boot:
Code:
# dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# dd if=/data/local/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
install SuperSU:
Code:
FLASH SUPERSU LIKE OLD DAYS
Why patch boot?
Cos MIYABI stops ptrace, some apps depends on it won't work properly.
Chinese here:
禁止转载到国内论坛，禁止用于商业用途。日版不会有的。
Note:
a. Remember to rename recovery.00X.zip to recovery.zip.00X before unzipping!
b. If you don't flash boot.img before install SuperSU, you will end up in boot loop. To restore, delete /system/xbin/daemonsu.
Attachments will be uploaded soon.
Hi tewilove, many thanks for publishing this. Amazing work! And a big time saver
tewilove tnx allot !!
hey some one know how can i put su inside in system and then to use SuperSU ?
thank you a lot
thanks but i can not use root app and super su can not install bin su
thank you for your help
tewilove said:
Tested with a 306SH with SW version S4081.
How to:
https://youtu.be/UJs7ruckGgc
This is v1, since the shell code has to be improved yet(WIP).
It only obtains temp root with kernel context. The left things are changing to init context, disable mmc_protect_part, disable miyabi LSM.
There might be v2, which solves all above, if I have time.
And it also works with many other devices.
For example, 305SH, MI4C, SH-01G.
If it keeps crashing, it should be my hard coded offsets.
PS: Please don't reshare this thread.
PS: Chinese: 请不要转载到贴吧，论坛，谢谢。
Click to expand...
Click to collapse
thank you for your help 谢谢某因幡分享
Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app
salmanaman said:
Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app
Click to expand...
Click to collapse
you can watch the video that tewilove make for us .. but we need to wait when some one unlock protect bcs after you restart phone root will disappear..
tewilove said:
Tested with a 306SH with SW version S4081.
Click to expand...
Click to collapse
How can I know that I got the temporary root? Is this step in the input ID?
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that @tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?
ok so for the moment is useless ?
soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
me too?maybe just kernel root??
---------- Post added at 12:48 PM ---------- Previous post was at 12:31 PM ----------
loonbg said:
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?
Click to expand...
Click to collapse
yea?rootxplore and xposed said no root?
I don't think that folks are understanding what "temp" root means. This solution allows you to achieve root for the current shell session. This does not install the additional binaries to allow other applications to use root access.
With that being said, I am wondering if we can use this temporary elevated access to correct the vulnerability outlined in CVE-2015-1474 affecting /system/lib/libui.so that Sharp has neglected to address in previous OTA updates. The only "corrected" libui.so that I have been able to locate was compiled for v5.0.1 so I am afraid that file would not be compatible with this earlier version of Android on the 306SH. I am not really savvy with in depth programming to be able to fully investigate this and develop a viable solution... anyone who would be able to point me in the right direction would receive many thanks. :banghead:
My apologies if this should have been posted in a separate thread.
awesom! it worked in my 306sh with root permission acquired in shell.
can you use root app and install super su ?
Write protection is keeping us from remounting /system as rw. This prevents us from doing anything that would have any type of impact on the current situation. I want to experiment with attempting to mount partitions with the device powered off... but my device is encrypted so I am unable to access the shell with device off until I perform a factory reset. I am planning on doing that tonight so hopefully I will be able to report back with more information soon.
Sent from my 306SH
soudara said:
can you use root app and install super su ?
Click to expand...
Click to collapse
No. We are working on it though.
On another note, I can't get this temp root to work.
Video of what happens is linked. (too large to attach)
https://mega.co.nz/#!blNTjbhS!p2ljioY_43xlWkpu3EWpj8LvfMVP5eushZT23KLPASk
TechInMD said:
Write protection is keeping us from remounting /system as rw.
Click to expand...
Click to collapse
So I assume, from the quoted text, you have tried mounting /system as rw while in the temp root shell session?
Yes. I tried using the mount command both directly from the root shell prompt plus I tried using busybox to mount also. There seem to be slight variations between them. Also, not sure if it is relevant but I attempted it both through adb and in terminal on the device. I can get to the root prompt but not further.
Sent from my 306SH