Related
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back
S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App
wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.
Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App
Folks,
I need someone on DL17 to test for root access. Due to the small community, I haven't heard if anyone is rooted on DL17.
While I can build kernels and get clockwork working for DJ20, for DL17, I need the stock kernel dumped, and for that I need root.
Steps:
1. Go to Index of /files and download rage.bin. (right click, save as)
2. Copy or adb push rage.bin to /data/local/tmp on your phone.
3. In adb shell:
Code:
chmod 755 /data/local/tmp/rage.bin
Then
Code:
/data/local/rage.bin
It will give you a wall of text. Wait a few minutes, hit ctrl-c to close adb shell, then type
Code:
adb kill-server
Then do adb shell again. It should (hopefully) take you to a # prompt. Please report back.
Thanks.
adrynalyne said:
Folks,
I need someone on DL17 to test for root access. Due to the small community, I haven't heard if anyone is rooted on DL17.
While I can build kernels and get clockwork working for DJ20, for DL17, I need the stock kernel dumped, and for that I need root.
Steps:
1. Go to Index of /files and download rage.bin. (right click, save as)
2. Copy or adb push rage.bin to /data/local/tmp on your phone.
3. In adb shell:
Code:
chmod 755 /data/local/tmp/rage.bin
Then
Code:
/data/local/rage.bin
It will give you a wall of text. Wait a few minutes, hit ctrl-c to close adb shell, then type
Code:
adb kill-server
Then do adb shell again. It should (hopefully) take you to a # prompt. Please report back.
Thanks.
Click to expand...
Click to collapse
Bro I just used my one click...works fine. Full root and busybox.
Sent from my SCH-I400 using XDA App
Great. Can you post the DL17 zImage?
Thanks.
adrynalyne said:
Great. Can you post the DL17 zImage?
Thanks.
Click to expand...
Click to collapse
Give me a sec.
Sent from my SCH-I400 using XDA App
have you tried my clockwork recovery? It works on DJ20, but I need more tests on DL17.
adrynalyne said:
have you tried my clockwork recovery? It works on DJ20, but I need more tests on DL17.
Click to expand...
Click to collapse
No
Sent from my SCH-I400 using XDA App
Can you give it a shot and if it doesn't work, give me the exact error message?
adrynalyne said:
Can you give it a shot and if it doesn't work, give me the exact error message?
Click to expand...
Click to collapse
Sure linke to it.
Sent from my SCH-I400 using XDA App
http://adrynalyne.us/files/odin/cont_cwm_recovery_2.tar.md5
http://www.mediafire.com/?3m25rg785awfjsh DL17 zImage
One thing you should note though is the data mounting problem jt fixed with voodoo clockwork, koush never got to it. Im porting 3.0.1 now.
Sent from my SCH-I400 using XDA App
I was just building clockwork for them because I noticed they had the cdrom/mass storage bug with DL17, and there was NO recovery to flash a kernel with...
You can flash a kernel with adb commands.
Sent from my SCH-I400 using XDA App
Im fully aware how to. Most are not. Its for them, not for me. I rather make it easy than hard.
I get what your saying, but a one click works just fine and so does odin... are you working on 2.0 or 3?
Sent from my SCH-I400 using XDA App
Im working on getting these guys through the dark ages, today, instead of a month from now.
I triy to type "adb shell" in cmd which works but upon typing "su", it throws me a: "permission denied" and on the screen it says: "shell has been denied Superuser permissions.
In the superuser app, there is no record of ever accepting or denying "shell" and clearing Superuser's apk data doesn't help. Everything else related to root works besides giving adb root permissions.
What to do? In some other forum, someone said it was kernel related?
You need to go to settings then developers options and enable root access to adb.
Sent from my Galaxy Nexus using xda premium
jhernand1102 said:
You need to go to settings then developers options and enable root access to adb.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not running CM9 anymore, though, but I have no such option? I'm running stock.
Theshawty said:
Not running CM9 anymore, though, but I have no such option? I'm running stock.
Click to expand...
Click to collapse
*facepalm*
Stock rom does not come rooted, so having that option under stock settings menu wouldnt make any sense.
And you still remember that you opened this because of a feature of cm9, that you were not familiar with at the time?
Sent from my i9250 using Forum Runner
bk201doesntexist said:
*facepalm*
Stock rom does not come rooted, so having that option under stock settings menu wouldnt make any sense.
And you still remember that you opened this because of a feature of cm9, that you were not familiar with at the time?
Sent from my i9250 using Forum Runner
Click to expand...
Click to collapse
Well obviously I have rooted my phone and now when I tried that command again (for like the 30th time) it magically worked.
I don't know why, though. "Shell" couldn't seem to get superuser permissions when everything else that required root worked perfectly?
If youre talking about stock, Kernel/boot.img is secure
But it should work.
Sent from my i9250 using Forum Runner
bk201doesntexist said:
If youre talking about stock, Kernel/boot.img is secure
But it should work.
Sent from my i9250 using Forum Runner
Click to expand...
Click to collapse
I've never understood what the difference between "secure" and "insecure" boot.img is.
I'm kind of new to Android, but I have decent computing experience. My problem is that I recently rooted my SPH-L710 (stock rom) and when I ran Busybox I received the error message "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is improperly rooted. Try removing the superuser/supersu permissions, uninstalling this app," etc etc.
I have attempted various methods using things like root explorer and terminal emulator to remove/ change the permissions so I might delete the su file, to no avail as the phone isn't properly rooted. One thread on here mentioned that formatting the sd card - I assume it meant the phone itself - would do the trick. After that, I would of course have to flash a rom, correct? Thanks for your time.
I would do the rooting process over again, with a new download of all files.
Do you have cwm or another custom recovery working?
sent from a secret underground bunker
winstonmarrs74 said:
I'm kind of new to Android, but I have decent computing experience. My problem is that I recently rooted my SPH-L710 (stock rom) and when I ran Busybox I received the error message "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is improperly rooted. Try removing the superuser/supersu permissions, uninstalling this app," etc etc.
I have attempted various methods using things like root explorer and terminal emulator to remove/ change the permissions so I might delete the su file, to no avail as the phone isn't properly rooted. One thread on here mentioned that formatting the sd card - I assume it meant the phone itself - would do the trick. After that, I would of course have to flash a rom, correct? Thanks for your time.
Click to expand...
Click to collapse
try flashing this in recovery http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip its the binary files required for SuperUser if your having trouble with gaining root access
Annnnd try opening super user or super such right after booting
Sent from my SPH-L710 using xda app-developers app
mjben said:
I would do the rooting process over again, with a new download of all files.
Do you have cwm or another custom recovery working?
sent from a secret underground bunker
Click to expand...
Click to collapse
I'm running CWM. I've successfully rooted a few times before, but this last time it didn't work. I unrooted and then rooted again three times and even re-downloaded all the files (cwm, odin, rom) but I can't seem to fix this. I'll attempt it again and hopefully it'll take this time.
Fantastic! I flashed the su binary zip, rebooted and superuser was already to go and phone is now properly rooted. Thanks very much! :good:
Thank you!
evo4gnoob said:
try flashing this in recovery (SU url I can't post...) its the binary files required for SuperUser if your having trouble with gaining root access
Click to expand...
Click to collapse
I would like to take this opportunity to thank you. I had been having issues trying to get root on my Sprint GS3, and nothing worked until I used that SU.
:laugh:
Paleogryph said:
I would like to take this opportunity to thank you. I had been having issues trying to get root on my Sprint GS3, and nothing worked until I used that SU.
:laugh:
Click to expand...
Click to collapse
No problem m8 glad I could help
Sent from my SPH-L710 using xda app-developers app
Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.
I used the root method from CF-autoroot.
Once it failed I pulled the battery and flashed SuperSU-v2.19zip..
Now I get the binary update notification...
If I can just get some help from anyone that knows what they are doing that would be awesome..
Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing
BTW: I got the 64 su file from root junky...
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
samep said:
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
z31k said:
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
Click to expand...
Click to collapse
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Edit 2: if using custom kernel, don't need liboemcrypto.so
Sent from my SM-N910P using Tapatalk
samep said:
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
pbedard said:
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
The OP says he can flash mods. I'm assuming here and you know the consequences of such, but thought it also possible to mount system and use the TWRP file manager to edit system.
I'm still OB7 but following with interest regarding the root of OG5 and recovery methods.
Edit: If L Speed Mod flashes successfully, default mode should give more freedom if using ADB and it doesn't need root. I think it's all shell scripts. (ADB Insecure required for booted mode adb access.)
Sent from my SM-N910P using Tapatalk
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Ill look into it flashing l speed mods.. maybe that can be a door... I know that Selinux and fix permissions can be applied via TWRP. SU binaries are applied.. they were in the system folders. So su is where its supposed to be. Busybox is where its supposed to be, 2.49 does not work just older builds. Its all a matter of figuring out how to update binaries??
pbedard said:
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I would love to debloat in adb shell, however whenever I make a shell environment the device will not detect in adb shell. regular adb commands is fine, just when I start shell.. Suggestions?
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
z31k said:
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
Click to expand...
Click to collapse
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
samep said:
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
z31k said:
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
Click to expand...
Click to collapse
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
samep said:
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, that's the thing. I need all the help i can get. I posted over here because you guys have development. I have been watching your forum like a hawk, just waiting for you guys to get 5.1.1. Lol....We dont in the sprint note edge forum. But i figure its the same hardware.
So with all that said, i really appreciate your help. Its a great step at a fresh direction.