Related
Hello XDA,
So I was following a youtube guide that shows how to root nexus s. (http://www.youtube.com/watch?v=GSD92Qjt5Og). This is one click verison. So after unlocking the bootloader, when its time to select flash CWM, the CMD window would just close. I guess the file i was using were bad. So then i switched over to another youtube video (http://www.youtube.com/watch?v=EA6DlAqYUeo). In this video, (using the files in video's description), I mananged to flash CWM (but i used the latest verison of CWM 5023-cyan.img). Then pretty much followed the video and got superuser installed on my nexus. Now when i tried to boot into recovery, it will not boot into CWM. it shows the android with exclamation mark and there when i press volume up and power, i am taken to the stock recovery i guess.. So now I am confused if my phone is rooted. I do have superuser installed on my phone right now (version that was included in the 2nd youtube video) but I don't have CWM. I am interested in flashing other ROMS. How and what should i do? Sorry for the long explanation. Thanks for your help
Use root explorer or similar program to rename the file "/system/etc/install-recovery.sh" to anything you like (e.g. install-recovery.sh.bak), as this script is run on boot and replaces a custom bootloader if it is installed. After this just flash CWM again and you can be free
You'll have to do this anytime you install a Google Stock ROM.
Harbb said:
Use root explorer or similar program to rename the file "/system/etc/install-recovery.sh" to anything you like (e.g. install-recovery.sh.bak), as this script is run on boot and replaces a custom bootloader if it is installed. After this just flash CWM again and you can be free
You'll have to do this anytime you install a Google Stock ROM.
Click to expand...
Click to collapse
I installed ES File Explorer and I cannot locate any folder called system.. the only 3 folders I see are "android", "clockworkmod", "Lost.DIR". root explorer is paid app. do you know any other free app. I don't know if this ES File explorer allows me to see system files. Its only showing whats on SD card...
NVM... i managed to get another app.. that allowed me to change the file name as you suggested.. then i installed ROM manager.. Flashed CWM from there.. and rebooted into recovery.. and GUESS WHAT.. I GOT CWM.. .. thanks buddy..
No worries mate. BTW, for ES, you need to go to options and tick the two options all the way at the bottom (enable root, mount /system).
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.
I just wanted to clarify that with S-OFF this module is useless
migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk
For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.
I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).
blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.
This is an updated guide for the Samsung S8+ (G955F) version for the new beta 3.
I thought I would put this guide out there as this was the easiest I found and the bonus is that you keep your data and just upgrade over the top.
All credit to jaron vdb from Telegram. This is his backup and he has given me permission to use it. He is the brains – I am just good at writing easy to use guides!
Pre-requisite:
-you need to have a working TWRP
-you need an external sd card
Steps:
1. Get into TWRP and backup your current rom to your external SD card. We will need this later to restore the data and importantly: if things go wrong you can always restore back again to what you have now.
Once it has been backed up you will have a folder on your external sd card that looks something like this:
Name of your External SD card/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just backed up in step 1]
2. Download this file and save it to your External SD CARD:
https://drive.google.com/open?id=1wOl1fPK_9ffSxOcGg6IHvytCrHZ7yL-X
This is your TWRP restore file kindly provided by jaron vdb.
3. Once you have downloaded that file then you will need to unzip this file. Use something like 7zip from Playstore and extract that file you downloaded to this location you just created with Step 1 – something like:
External SD CARD/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just unzipped]
This is a very important step – you must extract the file you downloaded to this EXACT location.
4. Go here and download supersu 2.82SR5 to your external SD Card:
https://androidfilebox.com/app/supersu-root/
This is the only root version working at the moment – magisk does not work as of now. It is Supersu which works perfectly. It also has dm-verity on it so will allow you access to data in TWRP.
5. Ok we are ready to flash the Beta 2! Get into TWRP again
6. Hit the restore button and then go to your external SD Card and restore the file that you downloaded and had to extract. You will also see your other restore in there. Don’t touch that just yet.
7. Stay in TWRP and now go to Wipe and then go to Format Data and then type in yes
8. Stay in TWRP and now go to Restore and choose the first file you backed up in Step 1 – your original backed up ROM. Choose this file and then ONLY TICK data to install. Restore data.
9. Stay in TWRP and flash the supersu file you downloaded.
10. Reboot!
11. You now should be rebooted back into your original rom with the very smooth Beta 3 installed!
12. Now you have to make the fix so you don’t get a buttload of random reboots and Knox nonsense. Download Root Explorer or any build prop editor program from Playstore and change:
ro.config.tima=1 to ro.config.tima=0
and change Knox thingo to v30 like this:
ro.config.knox=v30
Mine was already on v30 but YMMV
13. Have a cup of tea.
Can confirm working on G955F
Did exactly as instructed and all is well so far
Thank you
Will these steps work if I'm on 7.0
Or are these only for people who have already upgraded to oreo b1 / b2?
Thanks in advance.
One more question, can I use it on G955FD?
wkdurrani said:
Will these steps work if I'm on 7.0
Or are these only for people who have already upgraded to oreo b1 / b2?
Thanks in advance.
One more question, can I use it on G955FD?
Click to expand...
Click to collapse
yes this will work if you come from 7.0 too yes
i didnt testet it on g955F cuz i dont have one
greeetings
wkdurrani said:
Will these steps work if I'm on 7.0
Or are these only for people who have already upgraded to oreo b1 / b2?
Thanks in advance.
One more question, can I use it on G955FD?
Click to expand...
Click to collapse
Yes works if coming from 7.0
poczynek said:
Yes works if coming from 7.0
Click to expand...
Click to collapse
Thanks. What about G955FD? Will it work on FD? Or do I have to test it myself?
wkdurrani said:
Thanks. What about G955FD? Will it work on FD? Or do I have to test it myself?
Click to expand...
Click to collapse
Not sure. Just back up in twrp and try.
Not for the 955U???
matthewd769 said:
Not for the 955U???
Click to expand...
Click to collapse
Same as above. As long as you have a TWRP backup on the external sd then give it a try.
poczynek said:
Same as above. As long as you have a TWRP backup on the external sd then give it a try.
Click to expand...
Click to collapse
We currently cant use TWRP ... we only have flashify.
matthewd769 said:
We currently cant use TWRP ... we only have flashify.
Click to expand...
Click to collapse
Ah tricky. You'd need a back up to be safe. Doesn't flashify have a backup option?
Yes.... who cares if i have to re root then beta 2 oreo
I tried with 955U, flashfire cant find the backup file for oreo beta. Only shows my own backup
253simon said:
I tried with 955U, flashfire cant find the backup file for oreo beta. Only shows my own backup
Click to expand...
Click to collapse
Pretty sure you'll need twrp.
Confirm working on G955FD.
Toggle Network Type was not working but is OK after reboot.
However, AdAway is unable to download host files. Searching for solutions, will update if am successful in resolving the problem.
All other root apps I have are working perfectly.
wkdurrani said:
Confirm working on G955FD.
Toggle Network Type was not working but is OK after reboot.
However, AdAway is unable to download host files. Searching for solutions, will update if am successful in resolving the problem.
All other root apps I have are working perfectly.
Click to expand...
Click to collapse
change adaway hosts location to data\ and download and symlink it
SOGKush420 said:
change adaway hosts location to data\ and download and symlink it
Click to expand...
Click to collapse
Thanks for the suggestion.
hosts file location is still system/etc
Just needed to change hosts file permissions to rw-rw-rw- in root explorer and now its working fine.
What about beta 3 for the s8 (not plus)?
Will this trip the knox counter?
azcamm27 said:
Will this trip the knox counter?
Click to expand...
Click to collapse
Installing TWRP will trip it
This is an updated guide for the Samsung S8+ (G955F) version for the new beta 4 released a few hours ago. It was a hotfix release for issues with apps closing.
I thought I would put this guide out there as this was the easiest I found and the bonus is that you keep your data and just upgrade over the top.
All credit to jaron vdb from Telegram. This is his backup and he has given me permission to use it. He is the brains – I am just good at writing easy to use guides!
Pre-requisite:
-you need to have a working TWRP
-you need an external sd card
Steps:
1. Get into TWRP and backup your current rom to your external SD card. We will need this later to restore the data and importantly: if things go wrong you can always restore back again to what you have now.
Once it has been backed up you will have a folder on your external sd card that looks something like this:
Name of your External SD card/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just backed up in step 1]
2. Download this file and save it to your External SD CARD:
https://drive.google.com/file/d/1MrLynlCYCtnkAFk7GMeDnigXSmA2-8hC/view
This is your TWRP restore file kindly provided by jaron vdb.
3. Once you have downloaded that file then you will need to unzip this file. Use something like 7zip from Playstore and extract that file you downloaded to this location you just created with Step 1 – something like:
External SD CARD/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just unzipped]
This is a very important step – you must extract the file you downloaded to this EXACT location.
4. Go here and download supersu 2.82SR5 to your external SD Card:
https://androidfilebox.com/app/supersu-root/
This is the only root version working at the moment – magisk does not work as of now. It is Supersu which works perfectly. It also has dm-verity on it so will allow you access to data in TWRP.
5. Ok we are ready to flash the Beta 2! Get into TWRP again
6. Hit the restore button and then go to your external SD Card and restore the file that you downloaded and had to extract. You will also see your other restore in there. Don’t touch that just yet.
7. Stay in TWRP and now go to Wipe and then go to Format Data and then type in yes
8. Stay in TWRP and now go to Restore and choose the first file you backed up in Step 1 – your original backed up ROM. Choose this file and then ONLY TICK data to install. Restore data.
9. Stay in TWRP and flash the supersu file you downloaded.
10. Reboot!
11. You now should be rebooted back into your original rom with the very smooth Beta 3 installed!
12. Now you have to make the fix so you don’t get a buttload of random reboots and Knox nonsense. Download Root Explorer or any build prop editor program from Playstore and change:
ro.config.tima=1 to ro.config.tima=0
and change Knox thingo to v30 like this:
ro.config.knox=v30
Mine was already on v30 but YMMV
13. Have a cup of tea.
Confirm working on G955FD
Can you please share b4 change log? I tried to search it but could not find it. I found change log for b3 but not b4.
See attached
poczynek said:
This is an updated guide for the Samsung S8+ (G955F) version for the new beta 4 released a few hours ago. It was a hotfix release for issues with apps closing.
I thought I would put this guide out there as this was the easiest I found and the bonus is that you keep your data and just upgrade over the top.
All credit to jaron vdb from Telegram. This is his backup and he has given me permission to use it. He is the brains – I am just good at writing easy to use guides!
Pre-requisite:
-you need to have a working TWRP
-you need an external sd card
Steps:
1. Get into TWRP and backup your current rom to your external SD card. We will need this later to restore the data and importantly: if things go wrong you can always restore back again to what you have now.
Once it has been backed up you will have a folder on your external sd card that looks something like this:
Name of your External SD card/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just backed up in step 1]
2. Download this file and save it to your External SD CARD:
https://drive.google.com/file/d/1MrLynlCYCtnkAFk7GMeDnigXSmA2-8hC/view
This is your TWRP restore file kindly provided by jaron vdb.
3. Once you have downloaded that file then you will need to unzip this file. Use something like 7zip from Playstore and extract that file you downloaded to this location you just created with Step 1 – something like:
External SD CARD/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just unzipped]
This is a very important step – you must extract the file you downloaded to this EXACT location.
4. Go here and download supersu 2.82SR5 to your external SD Card:
https://androidfilebox.com/app/supersu-root/
This is the only root version working at the moment – magisk does not work as of now. It is Supersu which works perfectly. It also has dm-verity on it so will allow you access to data in TWRP.
5. Ok we are ready to flash the Beta 2! Get into TWRP again
6. Hit the restore button and then go to your external SD Card and restore the file that you downloaded and had to extract. You will also see your other restore in there. Don’t touch that just yet.
7. Stay in TWRP and now go to Wipe and then go to Format Data and then type in yes
8. Stay in TWRP and now go to Restore and choose the first file you backed up in Step 1 – your original backed up ROM. Choose this file and then ONLY TICK data to install. Restore data.
9. Stay in TWRP and flash the supersu file you downloaded.
10. Reboot!
11. You now should be rebooted back into your original rom with the very smooth Beta 3 installed!
12. Now you have to make the fix so you don’t get a buttload of random reboots and Knox nonsense. Download Root Explorer or any build prop editor program from Playstore and change:
ro.config.tima=1 to ro.config.tima=0
and change Knox thingo to v30 like this:
ro.config.knox=v30
Mine was already on v30 but YMMV
13. Have a cup of tea.
Click to expand...
Click to collapse
So we can have the Beta 4 should my galaxy s8+ be rooted before ? i'm in stock i just need to know to avoid any issues later.
SoufYann said:
So we can have the Beta 4 should my galaxy s8+ be rooted before ? i'm in stock i just need to know to avoid any issues later.
Click to expand...
Click to collapse
No you don't need to be rooted but you need twrp.
Hello, I follow you since the first one(night), openly(frankly) his(her,its) work perfectly, stable, economique, anything has to say.
Only small problem, how deprive the beta(stupid) notification of the starting up.
Continue as his(her,its) haste of even the continuation(suite) of the beta(stupid) or official.
GISN-FRANCE said:
Hello, I follow you since the first one(night), openly(frankly) his(her,its) work perfectly, stable, economique, anything has to say.
Only small problem, how deprive the beta(stupid) notification of the starting up.
Continue as his(her,its) haste of even the continuation(suite) of the beta(stupid) or official.
Click to expand...
Click to collapse
Freeze it with Titanium backup.
Quelle fichier prendre ?
Pour le congeler .
Followed this guide exactly but its stuck on the boot logo that says "Samsung Galaxy S8+ powered by android"
i can get back in twrp and flash my backup but when i flash the oreo file it gets stuck on the boot screen. Please help
I also had Magisk installed previously, if that helps.
How to remove this Beta notification has every starting up of my S8 +
GISN-FRANCE said:
How to remove this Beta notification has every starting up of my S8 +
Click to expand...
Click to collapse
Freeze in titanium backup.
OK? But what file is has to freeze?
GISN-FRANCE said:
OK? But what file is has to freeze?
Click to expand...
Click to collapse
Just search for 'beta' - i think it is something like 'Samsung beta'.
Ol, thank you my friends Fichier find and freeze, his work completes thank you
Link is no longer availible??
BETA ZQL8
links are dead
cookiiee94 said:
links are dead
Click to expand...
Click to collapse
Oreo isn't even beta anymore
G955U Odin BQL1
https://drive.google.com/open?id=1-ikUEBd_uZevIGA3jgaVFu04p5PLk6ze
BQL1 to CRA9
https://samsung.firmware.science/download?url=48926/1488/SS-G955USQS2BQL1-to-U2CRA9-UP
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
Just forget to change hosts file manualy, use the better Adbloacker Rootless, Blokada
medo159 said:
QUOTE
Click to expand...
Click to collapse
Hi Mate,
Ensure to give proper permissions as follows: rw-r--r-- (0644) to the file. If it is a folder, the permissions are: rwxr-xr-x (0755)
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
You can't mount the system partition as rw directly in Android 10. Here's a thread by topjohnwu (slightly technical, but give it a read) on why: https://twitter.com/topjohnwu/status/1259039809361739776