remount failed: Operation not permittedWhat happens when you do adb remount?
remount failed: Operation not permittedWhat happens when you do adb remount?
adb remount will fail without unsecured kernel. It works during the rooting process when the kernel is temporarily unsecured (really a debugging mode).try sudo adb remount?
I am having the same issue.I am in the same boat; I had jcase's root prior to the ICS update then last root. I tried the bat file and manually entering in the commands. No luck.
I don't have my cable with me but if the people that had root from jcase's method
are the only ones that are having trouble which should include myself then we my
have to do a factory reset in the prime first. The main reason I say this is because
I have noticed that all the apps ask for su and are granted because one they are
still in the SuperUser apps db. And two because su is still in the system/xbin
directory. If someone that has their cable and can do a factory reset then try to use
this method it may have a different outcome. I am only guessing as I cannot
test this theory at the moment.
What do you think -viperBOY-
I really want an unlocked bootloader right now. Come on Asus hurry up.
Factory reset won't do anything. Because the stuff in the /system partition stays in tact. For example, I had su in /system/bin (after ICS OTA) but the perms on it were wrong and couldn't be changed, so factory reset won't remove that.I don't have my cable with me but if the people that had root from jcase's method
are the only ones that are having trouble which should include myself then we my
have to do a factory reset in the prime first. The main reason I say this is because
I have noticed that all the apps ask for su and are granted because one they are
still in the SuperUser apps db. And two because su is still in the system/xbin
directory. If someone that has their cable and can do a factory reset then try to use
this method it may have a different outcome. I am only guessing as I cannot
test this theory at the moment.
What do you think -viperBOY-
I really want an unlocked bootloader right now. Come on Asus hurry up.
Thanks for calling this out, I was going to do this but saw your previous post. Any info I can provide to help track down the inconsistency?i hope this doesn't sound to ignorant. im using ubuntu with adb working, shows up fine in device. this method should work just fine in linux right? i guess what im asking is do you think if i tried from windows i would'nt get the permission denied?
---------- Post added at 10:40 AM ---------- Previous post was at 10:33 AM ----------
Thing is dandmcd, got it work having previously rooted honeycomb. See a couple posts up. There must be a inconsistency some where...
Factory reset won't do anything. Because the stuff in the /system partition stays in tact. For example, I had su in /system/bin (after ICS OTA) but the perms on it were wrong and couldn't be changed, so factory reset won't remove that.
I have updated PrimeTime to root ICS (using this method, with permission from OP) and I'm almost done testing it. Just fixing some backend stuff. One annoying thing is that you can't do "adb remount" because the kernel is "secure" so I'm just making a script so you can do "adb shell sysrw" to make /system r/w (even when not root). Give me an hour or so and keep a look out on my Twitter for those who want to test![]()
Thanks for the info on the reset. I am just trying to think of why some say it worksFactory reset won't do anything. Because the stuff in the /system partition stays in tact. For example, I had su in /system/bin (after ICS OTA) but the perms on it were wrong and couldn't be changed, so factory reset won't remove that.
I have updated PrimeTime to root ICS (using this method, with permission from OP) and I'm almost done testing it. Just fixing some backend stuff. One annoying thing is that you can't do "adb remount" because the kernel is "secure" so I'm just making a script so you can do "adb shell sysrw" to make /system r/w (even when not root). Give me an hour or so and keep a look out on my Twitter for those who want to test![]()
Yes, that is where I was. Had root, updated to ICS, lost root. My tool has gotten root back for me, but it's not quite ready for you guys just yet. Busybox isn't installing like it should, I'm about to remove it from the build (it wasn't even working in the last version lol).Thanks for calling this out, I was going to do this but saw your previous post. Any info I can provide to help track down the inconsistency?
---------- Post added at 11:14 AM ---------- Previous post was at 11:06 AM ----------
I am happy to test. I will keep an eye on Twitter. Any chance this will fix the problem for those of us who were dumb enough to do the ICS upgrade before unrooting or preserving our root, and for whom the method on this thread appears to be working, but doesn't result in a functional root access?
Because the syntax isn't 100% correct. Wait for the PrimeTime v3i get permission denied after issuing this command... adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop", Same here...Sigh!!! in time![]()
You can try using a 3 line process instead of that lineNO GO, everything went through but didnt get root access...
It was 755, not 06755. I could "run" su, it just wouldn't get the root shell and subsequently all the permission denied issues. This is likely because it's sticky bit didn't get transfered properly.Do you know what permissions su had once you updated to ICS from a Honeycomb rooted device?
Would somebody send me the info for "ls -l" for the /system/xbin directory from a device that previously had root with Honeycomb and is having issues now (may need to get a root shell for it to run).
Same here.It was 755, not 06755. I could "run" su, it just wouldn't get the root shell and subsequently all the permission denied issues. This is likely because it's sticky bit didn't get transfered properly.