as topic - It's only me having problem to turn wifi on on cm12 nightlies? Yes, I know it's nightly, but this is just question
srsly? No answers?
hexen88 said:
srsly? No answers?
Click to expand...
Click to collapse
FWIW, I also don't get a connection. I restored my APs using a titanium backup taken from stock lollipop. All APs appeared to have been restored ok, and I did see the list of available APs in the vicinity including my router, but I just didn't get a connect.
Edit: I've done some more research and it seems that those issues are related to the Fritzboxes AVM, though I have no idea what makes them special. Maybe some detail about the DHCP implementation or so.
in my case i just can't turn it on...
hexen88 said:
in my case i just can't turn it on...
Click to expand...
Click to collapse
SOLVED by repairing permissions, but if any of user have same problem can simply do this:
The solution was to simply change ownership back to system:wifi
$ adb root
$ adb -d shell
# cd /data/misc/wifi
# chown system.wifi wpa_supplicant.conf
# reboot
how to do that?
i have same problem, cant turn on wifi
and I dont understand much that changing permision so could any1 of you post guide for nubs = me?
martinad said:
i have same problem, cant turn on wifi
and I dont understand much that changing permision so could any1 of you post guide for nubs = me?
Click to expand...
Click to collapse
follow all steps from post #5
You need adb on your PC and root access. All guides are available in the sticky threads.
Primokorn said:
follow all steps from post #5
You need adb on your PC and root access. All guides are available in the sticky threads.
Click to expand...
Click to collapse
how is the command for BT please? coz it doesnt work neither
martinad said:
how is the command for BT please? coz it doesnt work neither
Click to expand...
Click to collapse
BT?
Do you have ADB on your PC? Do you have root access on your device?
First off, use the command adb devices to check if the device is correctly connected & recognized.
Primokorn said:
BT?
Do you have ADB on your PC? Do you have root access on your device?
First off, use the command adb devices to check if the device is correctly connected & recognized.
Click to expand...
Click to collapse
i meant Bluetooth, same prob as with wifi. Cant turn it on
martinad said:
i meant Bluetooth, same prob as with wifi. Cant turn it on
Click to expand...
Click to collapse
Flash the factory images but I think you'll have to send it to a repair shop. Several threads have been opened on this topic like this one: http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
Good luck.
hexen88 said:
SOLVED by repairing permissions, but if any of user have same problem can simply do this:
The solution was to simply change ownership back to system:wifi
$ adb root
$ adb -d shell
# cd /data/misc/wifi
# chown system.wifi wpa_supplicant.conf
# reboot
Click to expand...
Click to collapse
I have a rooted One X (Evita) and I can't get the wifi to work pass any cm11 nightly released after June of last year. When I install any of the nigthlies after that date the wifi won't turn on and the problem has transitioned to cm12.
I know it's not a hardware problem because the wifi works with an older cm11 nigthly. Can anyone please tell me what to do because I tried almost everything including the solution posted in this thread.
hexen88 said:
SOLVED by repairing permissions, but if any of user have same problem can simply do this:
The solution was to simply change ownership back to system:wifi
$ adb root
$ adb -d shell
# cd /data/misc/wifi
# chown system.wifi wpa_supplicant.conf
# reboot
Click to expand...
Click to collapse
Hi @hexen88, i tried the above and it worked perfectly for a while now. and since yesterday i am having same problem, and by using the above trick it works for a while then again my wifi stops working. Can any thing else be done?
hexen88 said:
SOLVED by repairing permissions, but if any of user have same problem can simply do this:
The solution was to simply change ownership back to system:wifi
$ adb root
$ adb -d shell
# cd /data/misc/wifi
# chown system.wifi wpa_supplicant.conf
# reboot
Click to expand...
Click to collapse
Hi @hexen88, I've trying your solution but it doesn't work on my nexus5 :s. Actually I don't have any system.wifi file :/. I have tried a lot of things but nothing works.
Related
ADB Shell connects just fine, but I cannot SU into it. I am rooted and have the latest SuperUser installed... In addition, I have USB debugging enabled, the LG drivers, and Root Explorer works perfectly.
RESOLVED:
You must have SuperUser OPEN while trying to SU from ADB. I don't remember this being needed on my Nexus One, but it's working now. I will keep this up for others that might need it....
Sceencast in droid explorer isnt working for me.rooted g2x. Maybe ill reinstall it after i get home from work. Is yours working?
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
momentarylapseofreason said:
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
Click to expand...
Click to collapse
just got home from work. gonna try it now.
nope, no screencast even with super user running. just rebooted. gonna try again. logcat seems to be going nuts though.
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
wewoapsiak said:
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
Click to expand...
Click to collapse
First you need to go to settings developer options and root access and check apps and ADB
Then you might have to do the CHMOD -R 777 /directorynameyouaretryingtoaccess
Guys. I am assuming the su in adb shell is preceded by an adb remount? By default system is ro not rw.
Sent from my LG-P999 using xda app-developers app
What this mod does:
It removes the device ID string check from PortalApp, and enables the webtop option in DockService. Replacing these two apk files effectively allows the webtop to launch without proprietary hardware.
Click to expand...
Click to collapse
What this means to you:
Webtop mode over any HDMI without an expensive dock.
Click to expand...
Click to collapse
Installation:
Method 1: ADB install
Download the package here: http://forum.xda-developers.com/attachment.php?attachmentid=791033&d=1321938181
First Get the files to the device and remount /system as rw:
Code:
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o remount,rw /dev/block/system /system
Backup the original files:
Code:
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
Copy the modded files over fix permissions and reboot:
Code:
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
chmod 644 /system/app/DockService.apk
chmod 644 /system/app/PortalApp.apk
reboot
Click to expand...
Click to collapse
Appreciate my work? Buy Me a Beer:
awesome job!
however, will this effect how the device currently interacts with the motorola docks (webtop, lapdock, car-dock, hd-dock, etc)
The modifications to PortalApp will have no effect on that interaction whatsoever I have just removed the bit that checks to see if your dock is legit when the Webtop Launches. And the modification to DockService simply causes the mIsWebtopAllowed variable to return true.
In short everything will work the same, you'll just always have a webtop option in the Dock Picker Activity no matter what type of HDMI/Dock you have connected.
Excellent WORK!!!
Thanks i appreciate the work you did to make this happen!!! as soon as i get paid im buying you a beer!!!
Used this mod on my OG ATRIX. Works great on it with a Bluetooth keyboard. Again good work.
silly question I'm sure but I have to ask: Does this require root?
Code:
mount -o remount,rw /system
Didn't work for me. Had to use this:
Code:
mount -o remount,rw /dev/block/system /system
voodoomurphy said:
silly question I'm sure but I have to ask: Does this require root?
Click to expand...
Click to collapse
Yes, you'll need root.
Is it just 720p for all or anyone got it going @1080?
Sent from soberstone mobile.
Mod works great Thanks. I just have one question. Is there a way to make the 4G connection work on webtop?
sweet! thanks works great
Does this trick will enabling ethernet network?
Thanks
sobesan said:
Is it just 720p for all or anyone got it going @1080?
Sent from soberstone mobile.
Click to expand...
Click to collapse
i just got it going at 720p, but i haven't played with it to much.
works great. Has anyone tried getting the full ubuntu or installing any .deb packages on i yet?
duke8804 said:
Mod works great Thanks. I just have one question. Is there a way to make the 4G connection work on webtop?
Click to expand...
Click to collapse
Just enable tethering/mobile hotspots. http://forum.xda-developers.com/showthread.php?t=1330438.
Anyway after this turn on your mobile hotspots and and then connect your lapdock. It will run on your mobile broadband without a tethering plan. Now will you get a letter? I dunno.
Well... I've screwed up. I tried this from the Bionic Forum as a test: http://forum.xda-developers.com/showthread.php?t=1281722
and now my Atrix 2 will not load the web top. The M pulses and then nothing happens, the phone goes to sleep. I've tried a factory restore but that did not correct this. Any help would be appreciated.
voodoomurphy said:
Well... I've screwed up. I tried this from the Bionic Forum as a test: http://forum.xda-developers.com/showthread.php?t=1281722
and now my Atrix 2 will not load the web top. The M pulses and then nothing happens, the phone goes to sleep. I've tried a factory restore but that did not correct this. Any help would be appreciated.
Click to expand...
Click to collapse
Were you able to flash the webtop restore through RSD and go back to stock webtop?
I have not tried that yet, I have been a little to afraid to given what happened the first time I tried using Bionic derived tools. I'm a Mac guy, so RSD is out of my reach right now. I will try it tonight at work.
can I flash via recovery?
the same way I did with the first Atrix? Please let me know, and thank you, don't wanna try and brick it.
voodoomurphy said:
I have not tried that yet, I have been a little to afraid to given what happened the first time I tried using Bionic derived tools. I'm a Mac guy, so RSD is out of my reach right now. I will try it tonight at work.
Click to expand...
Click to collapse
The first times a mistake, the second time is a choice.
Hi,
Anyone know how to bypass the Motorola advertise screen on startup screen. Those screen that has the globe and airplane circling around with Motorola logo.
Thanks
dukkha2 said:
Hi,
Anyone know how to bypass the Motorola advertise screen on startup screen. Those screen that has the globe and airplane circling around with Motorola logo.
Thanks
Click to expand...
Click to collapse
In ADB run
su
mount -o remount,rw /system
cd /system/media
mv bootanimation.zip bootanimation.zip.bak
reboot
Kaw202,
Thanks for your help. I'm a newbie. I do not understand your description of the procedure. Would you please describe it in another way for a newbie. Does this means that I have to root the phone
kaw202 said:
In ADB run
su
mount -o remount,rw /system
cd /system/media
mv bootanimation.zip bootanimation.zip.bak
reboot
Click to expand...
Click to collapse
dukkha2 said:
Kaw202,
Thanks for your help. I'm a newbie. I do not understand your description of the procedure. Would you please describe it in another way for a newbie. Does this means that I have to root the phone
Click to expand...
Click to collapse
Sorry you do need root.
Also if you are rooted just download a terminal emulator and type the commands one at a time and hit enter after each one.
kaw202 said:
Sorry you do need root.
Also if you are rooted just download a terminal emulator and type the commands one at a time and hit enter after each one.
Click to expand...
Click to collapse
Thanks. so I do not need to root my phone.
What do you mean "in ADB run" ?
what is "su" ?
what is "mount -o remount,rw /system "?
what is "cd /system/media"
what is mv bootanimation.zip bootanimation.zip.bak ?
dukkha2 said:
Thanks. so I do not need to root my phone.
What do you mean "in ADB run" ?
what is "su" ?
what is "mount -o remount,rw /system "?
what is "cd /system/media"
what is mv bootanimation.zip bootanimation.zip.bak ?
Click to expand...
Click to collapse
If you want to do things with your phone over and above what a 'normal' user can do then you need to do some reading and have at least some understanding of what you are doing. I would advise you don't alter anything if you don't understand the commands above as its very easy to do damage from the command line once rooted.
If you want to go ahead then please do gain more knowledge first so you don't mess up your phone.
I totally agree to that what Scott said.
But i'll help you where you can find some basic material.
Here you have one of a few basic guides on ADB. Also a few linux commands are mentioned. Here you'll find more detailed information on Linux commands.
Instead of installing the whole Android SDK as explained in above mentioned link i would recommend you to use Minimal ADB and Fastboot
If you have problems with the Native Motorla ADB drivers you can use the Universal ADB Drivers
You can also use Terminal Emulator (Play Store) as kaw202 already explained. Then installing Driver and Minimal ADB and fastboot is not necessay. But still i would recommend you to do that.
These are only a few links. There are much more guides here on XDA if you use the search function while typing the keywords into it
mokkami said:
I totally agree to that what Scott said.
But i'll help you where you can find some basic material.
Here you have one of a few basic guides on ADB. Also a few linux commands are mentioned. Here you'll find more detailed information on Linux commands.
Instead of installing the whole Android SDK as explained in above mentioned link i would recommend you to use Minimal ADB and Fastboot
If you have problems with the Native Motorla ADB drivers you can use the Universal ADB Drivers
You can also use Terminal Emulator (Play Store) as kaw202 already explained. Then installing Driver and Minimal ADB and fastboot is not necessay. But still i would recommend you to do that.
These are only a few links. There are much more guides here on XDA if you use the search function while typing the keywords into it
Click to expand...
Click to collapse
Thanks for your response and warning. The info in your message is what I need. I want to learn. Once I understand the process of gaining some control and manipulating the phone, I shall make decision of whether to proceed or not.
dukkha2 said:
Thanks for your response and warning.
Click to expand...
Click to collapse
Did i really sound that strict
Sorry for that^^
Once I understand the process of gaining some control and manipulating the phone, I shall make decision of whether to proceed or not.
Click to expand...
Click to collapse
You should first ask yourself i you really wanna root your device with all its consequences.
mokkami said:
Did i really sound that strict
Sorry for that^^
You should first ask yourself i you really wanna root your device with all its consequences.
Click to expand...
Click to collapse
I thought that just bypassing the advertising screen by performing those steps posted by Kaw202, I do not have to root the phone !.
Thanks
Does this means that I have to root the phone
Click to expand...
Click to collapse
Sorry you do need root.
Click to expand...
Click to collapse
Thanks. so I do not need to root my phone.
Click to expand...
Click to collapse
I thought that just bypassing the advertising screen by performing those steps posted by Kaw202, I do not have to root the phone !
Click to expand...
Click to collapse
????!
mokkami said:
????!
Click to expand...
Click to collapse
Thanks
FIXED It was the old SIM card , just replaced it and everything is working FIXED
Greetings everyone
today my little bro decided to mess with my htc sensation , where he broke my WIFI, not working at all, and lost root which was easy to fix had the zip ready on my sd card , went back to 4ext , wiped everything except sd card , flashed two different ROMS (vipers 5.1 , cm 11 4.4 (ivanich) , WIFI not working , he was messing with SU binaries please see below. (After flashing the roms i flashed: Android_Revolution_HD_Root_and_BusyBox.zip (to gain root and to maybe fix stuff also flashed: Superuser-3.0.6-efgh-signed.zip .
This is the thread where he copy pasted stuff : http://forum.xda-developers.com/showthread.php?t=2272266 (this thread is not even for our phone) , he did only: HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES
.
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su <<<<<< this didn't worked cause file was busy
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
------------
code:
adb install com.koushikdutta.superuser.apk
adb install stericson.busybox.apk
-------------
after reboot WIFI wasnt working . Do i have to go back to stock , installing RUU? I honestly do not know what happened.
Thanks for every reply!
use a ruu.exe if nothing works with custom roms
Bad news!
Even after using RUU and going back to full stock 4.03 Android version my WIFI is not working , i get an WiFi Error . Even Bluetooth is not working.
Normally i would say its an hardware issue but wifi stopped working i think right after the first boot and opening superuser and busybox app.
Would replacing the hardware even help?
rzr86 said:
use a ruu.exe if nothing works with custom roms
Click to expand...
Click to collapse
BliZzArD_420 said:
Even after using RUU and going back to full stock 4.03 Android version my WIFI is not working , i get an WiFi Error . Even Bluetooth is not working.
Normally i would say its an hardware issue but wifi stopped working i think right after the first boot and opening superuser and busybox app.
Would replacing the hardware even help?
Click to expand...
Click to collapse
yeah but using ruu replaces everything back to stock
i would say try to lift up gently the pins from the back cover which are responsible for the wifi
see how it goes
yea i already tried that mate , but wth i took out the sim card (which is old and not really healthy btw) and booted the phone and WIFI WORKING and i am connected ?? like wut? i tried a different newer SIM , and its working so i guess its the unhealthy SIM , im going to replace it today and hope everything works . Thank you for the replies
At least i can now try to go S OFF after the RUU lol . What method do you suggest? I did tried to go ViperS 5.1.0 to use the runrunner method but it didn't worked , its the easiest one , might work now after going RUU , can unlock, root and then flashing ViperS.
rzr86 said:
yeah but using ruu replaces everything back to stock
i would say try to lift up gently the pins from the back cover which are responsible for the wifi
see how it goes
Click to expand...
Click to collapse
1. place the phone in download mode
2. open odin
3.download this file(https://www.dropbox.com/s/l96om7p00owmw0r/boot.tar.md5?dl=0) and place it in the ap section of odin
4.choose start
5.do the steps here http://galaxys7root.com/galaxy-s7-s...-attt-mobilesprintverizon-galaxy-s7s7-edge/3/
I only needed pages 3 and 4 because you need to use the files above instead!
6.Rooted
Please let me know if you have any issues!
activefan01 said:
Please let me know if you have any issues!
Click to expand...
Click to collapse
Is there a specific rom you need to do this on?
Edit: Don't bother the MD5 isn't going to work in Odin anyway as it's been modified and doesn't match.. Besides what makes you think the S7 is anything similar to the 5?
MrMike2182 said:
Is there a specific rom you need to do this on?
Edit: Don't bother the MD5 isn't going to work in Odin anyway as it's been modified and doesn't match.. Besides what makes you think the S7 is anything similar to the 5?
Click to expand...
Click to collapse
it always does that when i rename it idk why they get confusing when i leave them the same but here is the unrenamed file https://www.dropbox.com/s/l96om7p00owmw0r/boot.tar.md5?dl=0
finally i real developer. would this work on s6 edge plus?
warriorpluto said:
finally i real developer. would this work on s6 edge plus?
Click to expand...
Click to collapse
no but i can get it pm me the model number and build number
activefan01 said:
no but i can get it pm me the model number and build number
Click to expand...
Click to collapse
I got that kernel to go after so many tries but when you try to do root.bat it freezes the entire phone however I do have root access via adb shell from command prompt but that's it and when trying to issue the remount command on /system it freezes also.
that kernal should allow you to root what all steps did you do?
activefan01 said:
that kernal should allow you to root what all steps did you do?
Click to expand...
Click to collapse
I did everything you did.. Still freezes right when it tries to adb shell mount -o rw,remount /system and then you can't do nothing but reboot. Went back to stock backup already.
MrMike2182 said:
I did everything you did.. Still freezes right when it tries to adb shell mount -o rw,remount /system and then you can't do nothing but reboot. Went back to stock backup already.
Click to expand...
Click to collapse
How'd you go to stock backup? Does this seem promising?
tylerlawhon said:
How'd you go to stock backup? Does this seem promising?
Click to expand...
Click to collapse
It might be promising however I've been working on this all night and haven't gotten anywhere except for root access within command prompt. As soon as you type root.bat the first thing it does is adb shell mount -o rw,remount /system but the entire phone freezes! I can't seem to get past this freezing crap because you can't do anything with the phone when it freezes it.
MrMike2182 said:
It might be promising however I've been working on this all night and haven't gotten anywhere except for root access within command prompt. As soon as you type root.bat the first thing it does is adb shell mount -o rw,remount /system but the entire phone freezes! I can't seem to get past this freezing crap because you can't do anything with the phone when it freezes it.
Click to expand...
Click to collapse
If it's giving you root access in a terminal, could you not push the root files that way? Or do you have to remount to do that? I honestly don't know is why I ask. Would love to root this beast, but I'm not a lot of help with the more deep down technical stuff.
tylerlawhon said:
If it's giving you root access in a terminal, could you not push the root files that way? Or do you have to remount to do that? I honestly don't know is why I ask. Would love to root this beast, but I'm not a lot of help with the more deep down technical stuff.
Click to expand...
Click to collapse
You have to remount the system as writable otherwise trying to write a file to system doesnt work, and as soon as I issue the command adb shell mount -o rw,remount /system then phone just freezes but I'm looking into an answer for that but no luck so far.
MrMike2182 said:
You have to remount the system as writable otherwise trying to write a file to system doesnt work, and as soon as I issue the command adb shell mount -o rw,remount /system then phone just freezes but I'm looking into an answer for that but no luck so far.
Click to expand...
Click to collapse
What is it supposed to do? Is it supposed to reboot? I might be open to trying on mine.
tylerlawhon said:
What is it supposed to do? Is it supposed to reboot? I might be open to trying on mine.
Click to expand...
Click to collapse
No it's supposed to remount the system as writable because I need to be able to push su into /system/xbin but when I try to it gives me the error system READ only which means I cannot write to it. And if I were you be prepared to lose everything and factory reset in the end otherwise it's not going to hold no WiFi passwords or nothing every time I reboot I need to rein put all the WiFi crap and it's getting annoying.
MrMike2182 said:
No it's supposed to remount the system as writable because I need to be able to push su into /system/xbin but when I try to it gives me the error system READ only which means I cannot write to it. And if I were you be prepared to lose everything and factory reset in the end otherwise it's not going to hold no WiFi passwords or nothing every time I reboot I need to rein put all the WiFi crap and it's getting annoying.
Click to expand...
Click to collapse
I'm pretty much where you are at. I don't think DM-Verify is turned off in the kernel but it is a eng one. If you get tired of it just flash the boot.img below and you will be back to normal. It says PI1 but it should work fine if you are on MM. I flashed it on PL4 no problem.
View attachment 4004361
Misterxtc said:
I'm pretty much where you are at. I don't think DM-Verify is turned off in the kernel but it is a eng one. If you get tired of it just flash the boot.img below and you will be back to normal. It says PI1 but it should work fine if you are on MM. I flashed it on PL4 no problem.
View attachment 4004361
Click to expand...
Click to collapse
Yeah I already flashed back but apparently I'm going to have to factory reset again anyway because after flashing the original kernel it still won't keep my WiFi passwords saved and I have to keep redoing it.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I'm curious as to why the file system would deny me to mv su from my sdcard into /system/xbin when I'm ROOT... But if I so much as try to mount it as re writable it freaks out and freezes. But I can adb shell mount -o rw,remount / and adb shell mount rw,remount rootfs / with no issue but just that /system absolutely will not.
MrMike2182 said:
Yeah I already flashed back but apparently I'm going to have to factory reset again anyway because after flashing the original kernel it still won't keep my WiFi passwords saved and I have to keep redoing it.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I'm curious as to why the file system would deny me to mv su from my sdcard into /system/xbin when I'm ROOT... But if I so much as try to mount it as re writable it freaks out and freezes. But I can adb shell mount -o rw,remount / and adb shell mount rw,remount rootfs / with no issue but just that /system absolutely will not.
Click to expand...
Click to collapse
I feel like it's infuriating because root is right there but just out of reach. I've been using my m8 because I have root and my screen is peeling on my note, so if someone wants to shoot me some instructions, I can see what I get.
tylerlawhon said:
I feel like it's infuriating because root is right there but just out of reach. I've been using my m8 because I have root and my screen is peeling on my note, so if someone wants to shoot me some instructions, I can see what I get.
Click to expand...
Click to collapse
I really don't think you should try right now considering that both myself and @Misterxtc know what we're doing already and there really isn't much point in trying to give instructions out just to end up in the same exact situation we are.
And by the way, there is root. It's just in the console that's it!
By the way you can adb pull the /efs/carrier/HiddenMenu from the phone to your computer and change it and then push it back and then viola secret codes in the phone dialer work such as *#0*# and many others! If you do change it reboot before it'll take effect. Also it will remain this way even with doing a factory reset.
Misterxtc said:
I'm pretty much where you are at. I don't think DM-Verify is turned off in the kernel but it is a eng one. If you get tired of it just flash the boot.img below and you will be back to normal. It says PI1 but it should work fine if you are on MM. I flashed it on PL4 no problem.
View attachment 4004361
Click to expand...
Click to collapse
I tried doing adb shell mount -o rw,remount /system /system and I get permission denied as root.. wth?