Will this mod posted at the original inc. work for our phone as well?
http://forum.xda-developers.com/showthread.php?t=1621808
Before I flashed it I figured I would see if anyone tried it out.
It shouldn't hurt anything to try it. Just do a backup in recovery first then flash. If you have any problems you can easily go back that way. Only way to know for sure if it'll help with battery life is to try it. There should be no ill effects with doing so. Worst case scenario would be a bootloop in which case you have your backup. Next worse case... It does nothing for you.
Sent from my ADR6350 using xda premium
Ok Cool. I wasn't sure what negative things could happen if I flashed it. Thanks for clearing that up for me. I'm going to flash it tomorrow and see how it goes.
Just fyi, I went a head and set it up on mine with no issues. Can't say anything for battery life yet, too early to tell.
Sent from my ADR6350 using xda premium
I just flashed it on MIUI no problems, but I don't think it is compatible with this rom.
I ran "grep busybox /init.rc" in terminal and it is giving me permission denied.
I am assuming MIUI is not support "init.d".
Do you know if your cm 7.2 is supported by this?
kubes069 said:
I just flashed it on MIUI no problems, but I don't think it is compatible with this rom.
I ran "grep busybox /init.rc" in terminal and it is giving me permission denied.
I am assuming MIUI is not support "init.d".
Do you know if your cm 7.2 is supported by this?
Click to expand...
Click to collapse
Type su before the command. I believe miui has init.d support though. I've never run it myself though. But I think it does.
Sent from my ADR6350 using xda premium
CondemnedSoul said:
Type su before the command. I believe miui has init.d support though. I've never run it myself though. But I think it does.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Just did the su command and still giving permission denied.
Maybe I need to fix permissions, I'm not too sure.
kubes069 said:
Just did the su command and still giving permission denied.
Maybe I need to fix permissions, I'm not too sure.
Click to expand...
Click to collapse
When you put in the command, did you get a superuser popup or permission granted notification?
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yes, I got the pop up and i granted it access. I was still getting permission denied in some lines when i typed in the codes in the terminal.
It made minimal improvement if any at all for me.
Amphibliam said:
It made minimal improvement if any at all for me.
Click to expand...
Click to collapse
What rom are you running?
And did you run those codes to see if it stuck? I'm just trying to make sure I'm doing this right lol.
kubes069 said:
Yes, I got the pop up and i granted it access. I was still getting permission denied in some lines when i typed in the codes in the terminal.
Click to expand...
Click to collapse
Probably means your ROM doesn't support init.d, the OP in the thread you linked said to use dsixda's kitchen, try finding that with google.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Related
I was browsing around XDA and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1296916
Can this root our phones? Can someone clarify if this can or can't?
Why don't you try it out yourself and clarify it for the rest of us
Sent from my R800a using XDA App
I don't know how, that's why I am asking...
I would say no as I think it uses the same exploit as Gingerbreak and it got patched in 2.3.3. So I would say it works on 2.3.2 and down. Even more someone is reporting it not to work on 2.3.5.
But go ahead and try
Regards Dousan...
I'm on 2.3.3 R800x, I would like to try it, but I don't know how. Noob question here, how do you perform this?
Sent from my R800x using XDA App
I don't believe it will work. Isn't this just for HTC phones? Or phones with S-OFF?
e: balls. maybe i should read the entire thing next time.
Its Android wide, according to the thread.
Sent from my R800x using XDA App
I'll try it once I get home (gimme 30 minutes)
Sent from my R800x using XDA App
HTC reset my Nexus One to stock 2.3.4 unrooted after an off-warranty repair. zergRush worked for local root and then I was able to remount, push Superuser etc. Thanks!
Click to expand...
Click to collapse
Should work... *,* 2.3.4 nordic, I'm coming!
Tried and failed
I tried it 3x on my 2.3.3 R800x to no avail
Does anybody know if flash tools works on Ubuntu? I'm willing to rollback the update and see if 2.3.2 works with this one...
paxChristos said:
I tried it 3x on my 2.3.3 R800x to no avail
Does anybody know if flash tools works on Ubuntu? I'm willing to rollback the update and see if 2.3.2 works with this one...
Click to expand...
Click to collapse
Confirmed 2.3.3 as well as 2.3.2 wont work.
Sent from my R800x using XDA App
Damn, this sucks, I thought I had something Oh well...
EDIT: I keep getting permission denied
Cl8rs said:
Damn, this sucks, I thought I had something Oh well...
EDIT: I keep getting permission denied
Click to expand...
Click to collapse
did you do chmod??
Android is based off linux, and chmod is what's used to set permissions for files you don't own
chmod 755 (or chmod 777) should fix this
Does anybody know if flash tools works on Ubuntu? I'm willing to rollback the update and see if 2.3.2 works with this one...
Click to expand...
Click to collapse
You can use a Windows VM inside Ubuntu, with USB capabilities. It needs Oracle's VirtualBox software.
Thank you, Logseman
Sent from my R800x using Tapatalk
paxChristos said:
did you do chmod??
Android is based off linux, and chmod is what's used to set permissions for files you don't own
chmod 755 (or chmod 777) should fix this
Click to expand...
Click to collapse
I'm not sure what you mean, I am on Windows 7 though...
Cl8rs said:
I'm not sure what you mean, I am on Windows 7 though...
Click to expand...
Click to collapse
adb shell (in laymen's terms is) linux terminal (command prompt) after you push the file, cd to /data/local, them run "chmod 755 zergRush" it'll work.
Sent from my R800x using XDA App
So in other words, if I was running Linux, I could root my phone?
No, Android is linux based, what hes saying is in adb you use linux commands, in this case changing the permissions on the file to run it in the first place, but from what Ive read even if it does run its not working for us ATM
Thanks for the clarification. So are they fixing/updating it to work with our phones?
Hello all, I tried searching through some threads but couldn't find anything. I have racings ics build on my phone and I was able to install superuser but for some reason when I try to open root explorer or TB the prompt to allow the apps doesn't show up. I've tried updating superuser and wiping cache and fixing permissions. Has anyone had this problem?
Sent from my Xoom using Tapatalk
Flash this
http://goo-inside.me/superuser/Superuser-3.0.7-efghi-signed.zip
or direct link from the source http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Thanks for your help guys that did it, I was getting pretty frustrated haha
Sent from my Xoom using Tapatalk
btbaker2008 said:
Thanks for your help guys that did it, I was getting pretty frustrated haha
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
i know this has been answered, but for future - did you check the settings in SuperUser?
there is a way change how/when they appear.
Yeah I checked that and messed atound with the prompt settibg and ut didn't do anything. Flashing the new superuser file provided fixed it though
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I have flashed that SuperUser app more than 20 times but it still doesn't install. CWM says installation is successful, but it doesn't pop up.
aranurea said:
I have flashed that SuperUser app more than 20 times but it still doesn't install. CWM says installation is successful, but it doesn't pop up.
Click to expand...
Click to collapse
Same here
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.
okay, first off im gonna start out saying i am a samsung user and know nothing about htc. my buddy got an evo 4g for free and he wants me to root and install a rom, so i figured out i need s-on but have no idea how to do it. i tried the revolutionary thing but i entered the beta code and it always says invalid. please help! how do i do this?
Check your Hboot version first, if you haven't already done so. You can check the version by going into the bootloader (volume down+power). If it's 2.18 you'll have to use the Htcdev method to unlock the bootloader, install a custom recovery and root the phone. Revolutionary won't work with the newest Hboot. Incidentally, you don't have to have S-OFF to install a ROM or flash kernels, for that matter. So long as the bootloader is unlocked and the phone is rooted with a custom recovery, you're good to go.
Sent from my PC36100
Its like 2.16.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
spitfire2425 said:
Its like 2.16.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
For that h boot u can use revolutionary. First u need to install drivers ,make sure u check on usb debugging and unknown sources When u enter beta key make sure its entered correctly it is case sensitive from my PC36100 using xda premium
I found it worked much better just to copy the beta key and then paste it once prompted to enter it. It seems like a lot of people were getting errors trying to manually type the key in, but hey, if it works, it works
Sent from my PC36100
FinZ28 said:
I found it worked much better just to copy the beta key and then paste it once prompted to enter it. It seems like a lot of people were getting errors trying to manually type the key in, but hey, if it works, it works
Sent from my PC36100
Click to expand...
Click to collapse
ive tried that many times, it just wouldnt work.
spitfire2425 said:
ive tried that many times, it just wouldnt work.
Click to expand...
Click to collapse
Weird. Worked for me when I rooted my last EVO, no problem whatsoever.
Sent from my PC36100
FinZ28 said:
Weird. Worked for me when I rooted my last EVO, no problem whatsoever.
Sent from my PC36100
Click to expand...
Click to collapse
everytime i try it it says invalid beta key even when i copy and paste
spitfire2425 said:
everytime i try it it says invalid beta key even when i copy and paste
Click to expand...
Click to collapse
Okay, dumb question. When you entered the serial number of the phone to get the key, did you make sure you didn't use O for 0 (zero)? Not sure that could be part of the issue but worth looking at. I honestly can't think of anything else at this point. I remember when Revolutionary first came out last year, people were having a lot of issues with getting the beta key accepted. I for one didn't have this issue so I'm at a loss at this point.
Sent from my PC36100
I got it all worked out.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
spitfire2425 said:
I got it all worked out.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What ended up being the problem?
Sent from my PC36100
ok so i check for the boot loader version then what? i then install a custom made one from my computer? then i make a backup onto my sd card or comp? i have titanium but it says i need to be rooted...also...when do i instal the kernal? and where the heck do i find this stuff?:banghead:
HTC EVO 4G PC36100 ~ XDA Premium
If I recall correctly, there is a su binary file that you have to flash from recovery once you've run Revolutionary. It's a zip file that's in the Revolutionary guide. Running the su binary is what actually gives you root. You'll need to make sure that you have the app Superuser or SuperSU installed, as it will actually give permission for root apps (such as Titanium Backup) to operate. As far as kernels and such, look under the development section there, as there is a ton of great info there
Also, once you get rooted, I'd suggest going into Recovery and making a full Nandroid backup, especially if you plan on flashing a ROM or kernel. It'll come in handy if you get in a tight spot down the road.
Sent from my PC36100
FinZ28 said:
What ended up being the problem?
Sent from my PC36100
Click to expand...
Click to collapse
I'm not sure what the problem was but I ended up updating to gb with 2.18 hboot then downgraded to android 2.2 then ran the unrevoked program then flashed a rom. Worked perfectly.
Sent from my SAMSUNG-SGH-I727 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.