Related
In Blayo 0.7 rom written
kernel modules
Loading kernel modules is done by editing /data/local/modules file. If you want to enable for example ipv6 support, you have to edit this file adding "ipv6" (without absolute path and any suffixes) to it. The same goes for other modules too. Modules are added separated by spaces.
Click to expand...
Click to collapse
So how I edit this files?or how I can find their location?
Has this forum some information about editing Android system?
Using some file manager (astro, open intents, root explorer.. whatever you have installed), navigate to that modules file and open it in a text editor, then literally just type in 'ipv6' without the quotations, then save and exit. Reboot your phone and you're good to go.
If you feel intensely nerdy you could echo it in:
Code:
adb shell
echo "ipv6" >> /data/local/modules
reboot
el.dizzee said:
Using some file manager (astro, open intents, root explorer.. whatever you have installed), navigate to that modules file and open it in a text editor, then literally just type in 'ipv6' without the quotations, then save and exit. Reboot your phone and you're good to go.
Click to expand...
Click to collapse
I opened in a text editor but it doesn't show me nothing
I use root explorer
TheGrammarFreak said:
If you feel intensely nerdy you could echo it in:
Code:
adb shell
echo "ipv6" >> /data/local/modules
reboot
Click to expand...
Click to collapse
write "ipv6" quotes or not?
With quotes, I think. To check what you added to the file you'd just echo or cat the file back. If it's go quotes then you can overwrite the whole file by using a > instead of >>
TheGrammarFreak said:
With quotes, I think. To check what you added to the file you'd just echo or cat the file back. If it's go quotes then you can overwrite the whole file by using a > instead of >>
Click to expand...
Click to collapse
Sorry for this silly question but what the difference between echo or cat?
I think I will be on the first way because I don't really know how to use ADB right?
virus54 said:
Sorry for this silly question but what the difference between echo or cat?
I think I will be on the first way because I don't really know how to use ADB right?
Click to expand...
Click to collapse
Lol. Cat would be better in this case. And I did suggest this method with the preface "If you feel intensely nerdy you could ..."
ADB is easy though
Can you plz give me a guide with ADB?
I will try your way but there is may be something bad with my phone?
Download this (it's the ADB tools) to a known location. Then extract the zip to a known location. Open a command window in that location (for the sake of this guide: C:\ADB) So open CMD (start, run, type CMD, hit enter) In CMD type "cd C:\ADB". Plug your phone into the computer (make sure you're using CM). Debugging mode should be on (you'll get a notification in the status bar of your phone). Type "adb shell". You'll end up with a "#" and nothing else (if you get a "$" just type "su" and hit enter, and on the phone's screen accept the Superuser request).
Execute your comands
TheGrammarFreak said:
Download this (it's the ADB tools) to a known location. Then extract the zip to a known location. Open a command window in that location (for the sake of this guide: C:\ADB) So open CMD (start, run, type CMD, hit enter) In CMD type "cd C:\ADB". Plug your phone into the computer (make sure you're using CM). Debugging mode should be on (you'll get a notification in the status bar of your phone). Type "adb shell". You'll end up with a "#" and nothing else (if you get a "$" just type "su" and hit enter, and on the phone's screen accept the Superuser request).
Execute your comands
Click to expand...
Click to collapse
Thank you.
I succeed
what else I can do with ADB?
virus54 said:
Thank you.
I succeed
what else I can do with ADB?
Click to expand...
Click to collapse
Loads
10chars
thank you with your help i did it
virus54 said:
thank you with your help i did it
Click to expand...
Click to collapse
Sweet.
twitter.com/TheGrammarFreak
virus54 said:
I opened in a text editor but it doesn't show me nothing
I use root explorer
write "ipv6" quotes or not?
Click to expand...
Click to collapse
I guess I'm kinda late on the response, but yeah, it's supposed to be blank. And then all you have to to is add in "ipv6", WITHOUT the quotes, and then save and exit. But TGF's method works well too, didn't know to do that.
No problem I will look and learn too
better that i will enter as a 'Hex editor'?
because on "text editor" I cannot edit
after ROOTING Nougat 32.3.A.0.376 (E6833 E6853 E6883) (E6633 E6653 E6683 ), we will still face ERROR while removing system apps, because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in #terminal
Code:
su
mount -o rw,remount /system
ORRR
Code:
su
busybox mount -o rw,remount,rw /system
-----------
What???
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
Mee too unable to write on system
download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
Credits: https://forum.xda-developers.com/showpost.php?p=70677335&postcount=92
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Can any of you share here your perfectly rooted working kernel for Z5 E6683 DSDS ????
chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
i found a workaround and it goes
installing busybox
installing terminal
and writing following codes
Code:
su
'to give terminal root access
busybox mount -o rw,remount /system
later using ROOT APP REMOVER i manage to remove all bloatware!
toncheee said:
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Click to expand...
Click to collapse
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
YasuHamed said:
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
Click to expand...
Click to collapse
I also think the issue is not the RIC but something to do with the Nougat filesystem itself.
I can delete all the files and folders with any file managers I like but like after 1 sec they all reappear as nothing ever happened to them !!!
How strange is that ??
It shows file sizes when I delete them and take times to delete the folders with , say for 500MB
but they still reappear after just 1 refresh or 1 sec.
I cant figure it out at all for the sake of my sanity --- why the hell this is happening ????
https://www.dropbox.com/sh/2kf8wg3g13pv869/AACB3l8iPJHJnBlpnGorRqrha?dl=0
@bungadudu @chinmoy32
I followed bungadudu-s steps and it worked i can change permissions and prove it with link i provided.
And chenges, yes they stick after reboot and i can rename files allso, but:
after reboot i have to repeat this steps if i want to change something elsewhere, old changes do stick aroind though
I deletet phone to 0 mb in twrp, flashed AU nougat .372 with flashtool, rebooted into twrp, flashed zip file provided in link, then flashed supersu in link and rebooted, no custom kernel used
Next i will try to copy modified thermal files now and see if they stick after reboot and if kernel aduitor uses them, see you later
Observations:
-i changed permissions from file /system/build.prop and changed lcd density to 320 and i have bootloop
working on how to boot it up...
YasuHamed said:
after ROOTING Nougat 32.3.A.0.372 (e6833 e6853 e6883) (E6633 E6653 E6683 ), we will still face ERROR because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in terminal
Code:
su
busybox mount -o rw,remount /system
-----------
Click to expand...
Click to collapse
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
I install both of them via play.google.com
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
&
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
later i opened terminal and ran those commands
later i installed System App remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
granted it SU rights and removed HANGOUTS and GOOGLE MOVIES etc
It seems to work to some extend but if you want to go tweak it up, kablaaam
i did not managed to boot it up after bootloop sadly, i need my phone so this is it for me this week
stipi69 said:
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
Click to expand...
Click to collapse
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "cd /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
stipi69 said:
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "md /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
Click to expand...
Click to collapse
I just managed to restart my phone successfully after changing the LCD density to 320 [I also use this value since always ]
But then I carefully just deleted 1 single app and booom--- boot loop
PS. i used root explorer to just click mount as R/W and then do anything to system partition --
Great you magaged it, and yes 320 seems so right.
And i asume there is no way to break bootloop?...other than reflashing?
I had trouble afterwards on downgrading to.253, 3x times error on start, even after reseting " power & + " and couple of full wipes in twrp.
I had to flash lineage from twrp and boot it up and only then flashtool succeeded pushing. 253.
This nougat will be fun i see
If there is something to try tell me i will flash it once more tonight, otherways i can do it on weekends
Oh i did not tell, i managed to copy modified thermal files with no error and then changed lcd density so i can not 100% tell which caused bootlop, since i did not reboot in between...
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
there is another way which i did not try because the busybox commands worked for me
its about flashsing updater script
delete_recursive(
"/system/app/GoogleAnalyticsProxy",
"/system/priv-app/GoogleBackupTransport",
"/system/priv-app/textinput-chn-xxhdpi",
);
https://forum.xda-developers.com/showpost.php?p=70920831&postcount=2015
Everyone please share your modified stock kernel for your Z5 series models with specifics here ...........
- Model
- ROOT working
- TWRP
- SuperSU
- Busybox
and so on....
As there is way to much ambiguous information out there right now for perfectly rooting the nougat on Z5 series and even one can achieve root with DRM fix there seems to be no R/W permission on SYSTEM partition !!!!
So please the people here who have successfully achieve ROOT with W/R SYSTEM, SU , DRM and other capabilities and are happy with them , please do upload your kernels here mentioning proper model and other things mentioned above.
Its for general good
try using this
https://forum.xda-developers.com/xperia-z5/general/ub-drm-fix-dm-verity-off-root-t3539999
I successfuly rooted my phone and have /system R/W permission, just make sure to flash SR5 SuperSu 2.78. PM me with results.
L33Tgod said:
try using this
https://forum.xda-developers.com/xperia-z5/general/ub-drm-fix-dm-verity-off-root-t3539999
I successfuly rooted my phone and have /system R/W permission, just make sure to flash SR5 SuperSu 2.78. PM me with results.
Click to expand...
Click to collapse
I did try that.
And all the other methods currently available to this point.
Created / patched several kernels and the best I could achieve is a fully rooted kernel with DRM and SU.
The only problem is when I delete some thing inside the system folder, it comes back after 1 sec like nothing ever happened to it in the first place.
Searched for the issue a bit more , find 2 possible cures and tried them too but no luck---- so I am now asking people to upload their kernel here so that I can find out which is which and so on............
I'm on the Au firmware on E6653. Used rootkernel and answered yes to all questions except for Su and xposed. Then I installed phh's superuser from recovery and the app from the play store. Everything is working fine.
I shared weeks ago..
download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
@sceryavuz
My Phone
6653, flashed 32.3.A.0.372 AU, TWRP 3.0.2 and AndroPlusKernel v41. Root Checked.
Cannot get access to system obviously because of sony_ric....
ive tried following your steps on terminal but each time i try the code line " echo 0 > /sys/kernel/security/sony_ric/enable" it keeps saying cannot find that...
on terminal i typed :
SU Command ( which shows E6653:/data/data/com.termux/files/home #)
then i tried typing
echo 0 > /sys/kernel/security/sony_ric/enable (which shows sush: Echo: not found)
what am i doing wrong?
Gezzaman8 said:
@sceryavuz
My Phone
6653, flashed 32.3.A.0.372 AU, TWRP 3.0.2 and AndroPlusKernel v41. Root Checked.
Cannot get access to system obviously because of sony_ric....
ive tried following your steps on terminal but each time i try the code line " echo 0 > /sys/kernel/security/sony_ric/enable" it keeps saying cannot find that...
on terminal i typed :
SU Command ( which shows E6653:/data/data/com.termux/files/home #)
then i tried typing
echo 0 > /sys/kernel/security/sony_ric/enable (which shows sush: Echo: not found)
what am i doing wrong?
Click to expand...
Click to collapse
If you use AndroPlusKernel kernel, then you are not in stock.
Check a root browser "/sys/kernel/security/sony_ric/" folder is exist or not?
Hey S7 Users!
I don't know how many of you have experienced the problems that I have encountered while trying to run AOSP (Specifically Resurrection Remix 6.2.0) on the S7 such as passing integrity check or getting the gear app to work but they have been an issue for me. I'll be putting here what I did to get these things to work that I figured out over time and hopefully will save some people time. And sorry if the format is weird it's my first time making a guide and posting.
The problems that I'm going to address specifically are:
- Passing CTS Integrity
- Getting the Gear App to Work
First off, the CTS integrity. When you first install the ROM, you might find that you cannot download certain apps or that apps don't work correctly. Thats because the CTS integrity is tripped. This is because the Phone does not have a proper build fingerprint since it is a Custom ROM.
To fix this you're going to need Magisk (Link) and Magisk Manager and also Terminal Emulator (Link). Follow the instructions and once installed go into Magisk Manager and you can check that your CTS Integrity is False.
Next go to the download modules section
Screenshot
Then search for Magisk Hide Props Config, install it and then reboot.
Once rebooted open terminal emulator, grant it SU access and type "props"
A menu should appear: Screenshot
Now type 1 and press enter and this should pop up: Screenshot
Next type f then this will pop up: Screenshot
From there select the number that corresponds to Samsung or whatever phone you want although I haven't checked this to see if it works but I don't see why not. Then look and find the one labeled "Samsung Galaxy S7 (8.0.0)" should be 16.
Once you have selected 16(or what ever one you picked) type y and press enter to change the fingerprint: Screenshot
After it is finished it will ask you to reboot. Once rebooted go into Magisk Manager and check that CTS Integrity is now true. Also, go and clear the data and cache of the Play Store and the Play Services. Now you can download apps and use Google Pay
Now for the real challenge the Gear app. This one stumped me for a long time and made me want to just go back to stock. But I kept going and eventually figured it out.
Setting the fingerprint was only the first step because before you could not install it. Now when you open it it'll tell you that you've made unauthorized changes etc. because it thinks that the S7 is on stock firmware but when it checks it sees that it isn't. So what we are going to need to do is change the build.prop to make it look like a different phone. I'll link mine down below if you want it but it is a herolte (S7 Exenos) so keep that in mind as it might brick your system. This will involve some Linux skills.
For this one it is easier if you do it from a computer and then do adb shell. Enable Debugging in the Developer settings and then adb into the device with:
Code:
adb shell
Then
HTML:
su
(Allow it the Super User Access)
Next you have to set the /system to R/W so do that with the command:
Code:
mount -o rw,remount /system
After you have done that type:
Code:
cd /system
And then set permissions on the build.prop:
Code:
chmod 644 build.prop
At this point what you want to do is exit out of the shell (so type exit twice). Now type:
Code:
adb pull /system/build.prop
This will pull the build prop but it goes to different places. I suggest you look up where it stores it as it will vary where it drops it depending on operating systems. For me in Windows it is the following:
Code:
C:\Users\<account_name>\AppData\Local\VirtualStore\Program Files (x86)\MyCustomADBInstallLocation\
Now that you have it simply open it in a text editor and edit the following lines:
Code:
ro.product.brand=htc (change from samsung to htc)
ro.product.manufacturer=htc (also change from samsung to htc)
After that save the file and then go back to the terminal and type(Assuming you haven't moved the file):
Code:
adb push build.prop /sdcard
This will move it to the internal storage since at least for me i could not push it directly to /system
Now do another adb shell and su then type these commands to delete the old one, copy the new one in and then change the system back to read only(This is very important to avoid bootloops!):
Code:
rm /system/build.prop
cp /sdcard/build.prop /system
mount -o ro,remount /system
And then exit out of the adb then reboot the phone. If all goes well then it should reboot and the gear app should work now. Woohoo! That was pretty involved and I'm sure there is a more efficient way to do that (feel free to comment and suggest one) but I can guarantee that it works. Also feel free to ask questions and I can try to answer them. Anyways guys if this helped please hit the thanks button. This took many hours for me to figure out and I hope it all works out for you. Cheers!
Hi Guys,
I am no developer but I need to edit the libnfc-nxp.conf in /system/vendor/etc to use nfc-sim.
I guess I need to unlock bootloader, flash the working twrp, get root and just use root explorer to edit the file?
Will it reset back to original file bcos of A/B partition thing when reboot?
Thanks if any android expert can let me know.
laocheebye said:
Hi Guys,
I am no developer but I need to edit the libnfc-nxp.conf in /system/vendor/etc to use nfc-sim.
I guess I need to unlock bootloader, flash the working twrp, get root and just use root explorer to edit the file?
Will it reset back to original file bcos of A/B partition thing when reboot?
Thanks if any android expert can let me know.
Click to expand...
Click to collapse
Yes, you need to be rooted.
It will not alter the file on reboot.
I tried to edit libnfc-nxp.conf in /system/vendor/etc, but it resset to default after phone reboot.
Also, i can's repair my gpay with free bootloader and magisk intalled. So i deside to return device to closed one.
Well if you still have a locked Bootloader and unrooted, why would you need to edit that file for? If Google Pay, there is no reason why it wouldn't work. Those that are unlocked and rooted a little research the latest Magisk Canary(18.2) fixes Google Pay not working.
acuma14 said:
I tried to edit libnfc-nxp.conf in /system/vendor/etc, but it resset to default after phone reboot.
Also, i can's repair my gpay with free bootloader and magisk intalled. So i deside to return device to closed one.
Click to expand...
Click to collapse
You will need to mount "/" as read-write, in a terminal emulator (or adb shell):
Code:
$ su
# mount -o rw,remount /system
**NOTE: The above syntax might be different depending on ROM is use. Please use at your own risk.
sandix said:
You will need to mount "/" as read-write, in a terminal emulator (or adb shell):
Code:
$ su
# mount -o rw,remount /system
**NOTE: The above syntax might be different depending on ROM is use. Please use at your own risk.
Click to expand...
Click to collapse
Root explorer offer me to mount directory aftomatically, and successfully save my config, but after reboot it returns to default values. I found information about to create a magisk patch for usefully edit config at all, but not sure it's the simpliest solution for me, and i can find step-by-step instruction...
I need this to use my nfc-transport sim card, here's the discussion https://forum.xda-developers.com/oneplus-5/themes/mod-nfc-swp-sim-enabler-oneplus-3-3t-t3650482
Do i need to set NXP_DEFAULT_SE as 0x02 instead 0x07 (should 07 implement UICC correctly)?
Idk how, but after reinstall magisk gpay starts working fine