Database Info

Android symlink errors system/xbin/su PLEASE HELP

I have been trying to for over a week in the captivate forum to get ANYONE to try and help me and so far no one will. So i'm really hoping someone will take the time, i will PAY YOU UP FRONT over paypal to help me. I am DEAD SERIOUS.
Have a captivate, but this problem is not exclusive to this phone. This error has happened on just about any/every android phone there is.
Phone was working fine, have been putting any and all custom roms on that i wanted, but went to install a new custom rom (cog4), and it fails every single time at system/xbin/su. Now ANY rom i install (custom), gives me that same error. NO CUSTOM ROM WILL INSTALL. THEY ALL FAIL. I have flashed back to stock a million times, wiped, re-partitioned the sd card, master cleared, and done all of those in every combination possible. The ONLY rom i can put on here is the one i had RIGHT before this problem started (cog3.04). Only roms that can be flashed via odin will go on my phone now. All zip files fail.
I am not a noob and know my way around a computer. I promise if someone tries to help me i will be very prompt in my responses and will try ANYTHING that you ask me to. I have been googling for over a week hours a day, i am never gonna resolve this issue unless someone with the know-how helps me Every time this topic is brought up on any forum on the internet, the problem never gets solved and it fades away....there is no answers out there. Someone who knows this stuff is my only hope
I will pay you to help me even if your troubleshooting does not work

Just out of curiosity, did you open Rom Manager once you installed it to grant it superuser rights? Also, make sure you Click the top link in Rom Manger and choose your phone. "Flash ClockworkMod Recovery"

Yes tim i have done that.

I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.

http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?

JoelParke said:
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
Click to expand...
Click to collapse
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.

xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?

timbrendelaz said:
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
Click to expand...
Click to collapse
Yes i do 10char

xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
Not sure as this looks like a patch and specifically asks for no wipe. Also my knowledge is limited as to what harm you can do that will make the phone unusable -- BUT you are already into that realm . Perhaps someone with deeper specific experience can answer this????

Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x

timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
K will report back.

Also it looks like the update.zip file is long gone....

JoelParke said:
Also it looks like the update.zip file is long gone....
Click to expand...
Click to collapse
??? 10 chars

xsteven77x said:
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
Click to expand...
Click to collapse
using adb remount will set the /system partition as read/write. This may help.

xsteven77x said:
??? 10 chars
Click to expand...
Click to collapse
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.

JoelParke said:
using adb remount will set the /system partition as read/write. This may help.
Click to expand...
Click to collapse
I have been doing that within sgs tools, not the same thing?

timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!

JoelParke said:
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
Click to expand...
Click to collapse
Oh ok sorry i didnt understand. Ty for trying regardless though.

xsteven77x said:
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
Click to expand...
Click to collapse
LOL, of course......
If it doesn't install, try installing Terminal Emulator from the Market

Ok so inside of the system folder they both have the permissions set to what you wrote.... .
There is only a bin in the folder right before the system folder...should there be an xbin there too?

2.3.4: CWM 3.0.0.5 problems

So, I updated to 2.3.4 today, and after a rebbot into recovery, CWM was gone.
No problem, I tought, and used fastboot to flash it back.
fastboot went OK, but when I tried to use CWM from recovery, I got stucked at the "stock" recovery (android with a exclamation mark). Is anyone else facing this?
Click to expand...
Click to collapse
NVM this first part, solved that.
Also, I can´t get adb to work, tried pushing some files and got permission denied; abd remount gave me a "remount failed: Operation not permitted" error.

Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going

du5t3r said:
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
Click to expand...
Click to collapse
Thanks, I spent a long time yesterday trying to solve this.
Finally, I gave up and installed Root Explorer. Let me know if you have any progress with this.

Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.

kaizxclusive said:
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
Click to expand...
Click to collapse
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...

gasparzim said:
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
Click to expand...
Click to collapse
yes, just rename it to something like install-recovery.sh.old

Bajo76 said:
yes, just rename it to something like install-recovery.sh.old
Click to expand...
Click to collapse
Thanks, looks like it´s working now.

[Q] Cant boot after changing /system attributes using CHMOD

Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
after that i tried to mount the system from shell command but failed... then the phone got hanged and when i removed the USB cable it rebooted straight into recovery...
since the ive tried to check directory listing with adb ls /system command but it returns nothing... adb ls /data also shows only 3 files... i had taken a backup of /system using adb pull but i dont knw how much that'll help...
i did not take any backups before that... was trying to install CWM so that i could take rom backup....
im not able to boot the phone normally...
i would like to know if i can go back to original state?? if not is ther any other solution like flashing a new ROM or something...??
i would like to extract contacts nd messages if possible...
System config:
- Samsung Galaxy S 4G... everything stock
- Rooted!!
thanks in advance...

chi_visor said:
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
Click to expand...
Click to collapse
'chmod 6 /system' did what you asked it to do. chmod, on a basic level, uses three (3) sets of permissions: global, group, and user. What you effectively did was set the user permissions to rw but blanked out everything else (like chmod 006).
If you can get into the shell, do this:
chmod 755 /system
That should put it back the way it was (7 = rwx for global, 5=rx for group, 5=rx for user)
See if that helps. Report back and let me know.
Real quick; I had my permissions backward. Although you still want 755 it should've read like this:
rwx for user
rx for group
rx for global
I had them backward.

Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??

chi_visor said:
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
Click to expand...
Click to collapse
I was worried about something like that. My guess is that your best bet is to see if you can get into download mode and flash a new ROM. Were you on Froyo or GB before? If you were on Froyo & you're trying to get to GB you'll need to insure you flash a ROM with the right boot loaders first, like chadster's KG4 (http://forum.xda-developers.com/showthread.php?t=1183413).
Let me know if I can be of help.

I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...

chi_visor said:
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
Click to expand...
Click to collapse
If your contacts were set to sync with Google or your carrier, then they will sync back to your phone after you flash. Given you were on Froyo, you can grab one of the Froyo ROMs from the bible (http://forum.xda-developers.com/showthread.php?t=1117554). Those will likely be rooted, deodexed, or something along those lines. If you want pure stock, you can grab that from samfirmware.com. You'll have to register to navigate to the firmware, though. I'd post a link but it wouldn't work right. Just go to the 'mobile' link and look for the SGH-T959V stuff. Either way, KD1 was the latest Froyo out there from Samsung.

Yup... I'll check on samfirmware.com..
sad abt contacts cuz dint sync the latest ones with google...
anyway i'll try the other method...
thanks..

Sorry man. Best of luck to you. Let me know if you get it fixed.

hi stephen_w,
I downloaded the T959VUVKD1 firmware from samfirmware.com....
I used odin to flash it...
after switchin on the phone in download mode... i flashed the firmware by browsing the file in PDA and leaving PIT, BOOTLOADER, Phone and CSC blank...
the process started and after cache.fs... below it was message:Complete(Write) operation failed.... it stopped nd showed fail in red...
i held the power key for a long time but then it started to show a phone linked to the computer with a yellow exclamation sign...
what does this mean?? im not able to boot into either recovery or download mode now...
please help...

ODIN will still see it when it looks that way, so don't fret! I had similar issues before but mine was a faulty download. Try using this one. It's not 100% stock as it's been deodexed, but it should work:
http://www.multiupload.com/7L5YDG8X8V

Ya im downloading tat one... Odin is detecting nd working... so i guess re-flashing should do the trick...
Jus to confirm I should leave fields other than PDA blank rite?

Yes, PDA only & let ODIN decide what should be checked.
Sent from my SGH-T959V using XDA App

Up and running jus like b4...
Thanks bro...

No worries; glad you're working again!

[DUMP] STOCK AT&T deodexed/zipaligned ICS

Here is a dump of my /system/app and /system/framework that is deodexed/zipaligned. Its just the directories; its not flashable in CWM. I'll try and put together a stock zip later, but I don't have time at work. If someone else wants to do it, feel free to PM me a link and I'll host it.
For now, developers will know how to use this. In addition, if you feel brave, you can use the following steps:
Prework:
Download the zip. Extract it. Copy the deodex_app and deodex_framework directories to your external SD card.
1) Boot your phone into recovery
2) Mount /system and /sdcard from the mount menu
3) adb shell rm /system/app/*.odex
4) adb shell rm /system/framework/*.odex
5) adb shell cp /sdcard/deodex_app/* /system/app/
6) adb shell cp /sdcard/deodex_framework/* /system/framework/
7) adb shell chmod 644 /system/app/*
8) adb shell chmod 644 /system/framework/*
9) Wipe Dalvik cache from the advanced menu
10) Make sure /system, /data, and /sdcard are unmounted in the mounts menu
11) Reboot. It took about 5 minutes for my phone to boot and then it said "Upgrading Android" or something like that and went through 175 apps or so.
Download here.
ROM developers, feel free to use this to base your ROMs on. Please give credit for the base source of your ROM as always.
Edit: Clarified its also zipaligned.

Awesome!! I wish I was brave enough to try this..

So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium

pingfl00d said:
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I need the source which is not available yet. I suspect it will be shortly after this is OTA'ed. But yes, once it is, I will be updating my stock-ish

Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.

rjohnstone said:
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
Click to expand...
Click to collapse
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?

romracer said:
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
Click to expand...
Click to collapse
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?

rjohnstone said:
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
Click to expand...
Click to collapse
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.

romracer said:
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
Click to expand...
Click to collapse
Most likely... no biggie.
Factory reset should take care of it.
Worst case, I have a nandroid backup.
Edit: factory reset didn't fix it... time for a restore.

I will try and add this too a zip. Thank you
EDIT:
I added this to my ROM. I am still working on ironing out all of the issues, but this helped!
http://forum.xda-developers.com/showthread.php?t=1566820
And if you want to mirror that would be amazing.

that actually worked perfectly! although you should probably add in there that people can use emmc instead of sdcard if they dont have an external card (i dont).

Thanks for this.
Sent from my SAMSUNG-SGH-I727 using xda premium

thanks
I waiting for .Zip flasheable

if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!

Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4

mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
I do most of it by hand. I'm a Linux/Windows System Administrator by day, so I'm comfortable with the command line I do use Cygwin for just about everything though rather than the Command Prompt.

promiseofcake said:
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
The one liner I pasted in the other thread should work for both app and framework. It has more includes in the class path than are necessary for framework, but I don't think it'll break it.
It assumes the following:
You are in a directory with app, framework, deodex_app, deodex_framework and tmp subdirectories. app and framework contain the originals from the phone. The one liner should be run from this top level directory. I'd recommend doing framework first. You'll also need to Google java.awt.jar and put it in the framework directory too. Don't upload this to your phone though, its just needed for deodex'ing.

finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.

mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
i think the problem most people are having isnt related to the deodexing (anymore) but trying to flash it in CWM. it seems that flashable zips are messing up everything, as i used the same files i tried flashing in a zip this way and it works now. the zip version was unusable.

quikt said:
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
Click to expand...
Click to collapse
That's basically exactly what I did (and my phone seems stable). Thanks for typing out the parts I left out
I've always had to flash the Superuser zip twice for some reason. I just flash it twice right on top of each other (without rebooting, exiting CWM, etc). Never have any problems in the actual OS doing it that way.
Grab the official Superuser zip from goo-inside.me/superuser

Root N920V

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?