Related
Check this thread for updated and improved information, many thanks to j4mm3r
http://forum.xda-developers.com/showthread.php?t=953110
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2
Extract the above files using your favourite program
Using adb, install all three files to /data/local:
adb push su /data/local
adb push Superuser.apk /data/local
adb push busybox /data/local
Use adb remount to open the /system directory
adb remount
Use adb shell to move files
adb shell
cd /data/local
cat Superuser.apk > /system/app/Superuser.apk
cat su > /system/bin/su
cat busybox /system/xbin/busybox
Symlink su and set permissions:
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
Typing su should now work
su
su: access granted, courtesy of www.magicdroidapps.com
Install busybox
exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,
su
busybox --install -s /system/xbin
That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.
Good Luck
really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
anbradle said:
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
Click to expand...
Click to collapse
Check your steps, especially permissions and the symlink. Works consistently on reboot for me.
Homer_S_xda said:
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
Click to expand...
Click to collapse
I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin
chhaggerty said:
It wouldn't work for me without installing in /system/bin and using a symlink to /system/xbin
Click to expand...
Click to collapse
It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...
[email protected]:/system/bin # echo $PATH
echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
[email protected]:/system/bin # ls -l su
ls -l su
su: No such file or directory
[email protected]:/system/bin # ls -l /system/xbin/su*
ls -l /system/xbin/su*
-rwSr-sr-t root root 76232 2011-02-04 09:08 su
-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic
-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new
-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org
chhaggerty said:
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2.
Good Luck[/B]
Click to expand...
Click to collapse
i might take credit for gaining root, but the rest is all you
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
nswenson said:
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
Click to expand...
Click to collapse
Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
You were right I tried again and now I am rooted after reboot. Thanks
jleecong said:
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
Click to expand...
Click to collapse
Okay...
I am running HC (v2) off a 8gb sd card.
So do I just do these steps to gain root or do I need to partition the sd card first?
Thanks
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
agreed, i was just going for root myslef
j4mm3r said:
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
In
http://howto.ccroms.net/android_project/build/mod/root
I would have though that the purpose of the changes, specifically;
LOCAL_FORCE_STATIC_EXECUTABLE := true
LOCAL_STATIC_LIBRARIES := libc
Were what should resolve the _mktemp not found?
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Mikey1022 said:
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Click to expand...
Click to collapse
yes, at the stands, its just root access. granted i had my own reasons for this
I've rooted my HTC Amaze. The rootedness persists across reboot. Here's how I did it.
1. Copy the zergRush temp root to the phone. I put it in /data/local
2. Run zergRush on the phone via adb shell.
One you have temp root do this (from the PC)
1. adb remount
2. adb push su /system/bin/
3. adb shell chmod 04755 /system/bin/su
Then you can install superuser.apk and reboot. After rebooting you should be able to adb shell and type su. This should prompt you (on the phone) to allow su. Once you allow it then any apps that need root should begin working.
You can find the zip file that contains the su binary here
NOTE: the adb daemon will not be running as root so, when you adb shell to the device you will not have root. You just run su and then you have root.
Questions? Just ask. I'll do my best to help. But, remember, you do this all at your own risk.
-xdadevelopers-user
I had some weirdness when allowing a second root app in superuser. It would consistently FC. The first root app was fine and continued to work but I couldn't get another root app to be authorized.
It turns out it's related to the permissions on the superuser databases. To fix my problem I went to home>menu>settings>applications>manage applications>superuser>clear data. Then run superuser and dismiss the startup dialog. Now adb shell and run su. It will prompt on the device and you should allow it. You should now have the root prompt in your adb shell session. From there type
Code:
chmod 666 /data/data/com.noshufou.android.su/databases/*
Now you can run more root apps without superuser FCing.
-xdadevelopers-user
Very nice work, I will probably wait until we have recovery to actually do it. This is a great start though, hopefully this works with no problems as I saw that some were "bricking" their devices using the Zerg method for temp root.
This is still temproot , it won't allow u to go into /system to delete bloat or edit framework .
Sent from my HTC_Amaze_4G using XDA Premium App
Revolution said:
This is still temproot , it won't allow u to go into /system to delete bloat or edit framework .
Sent from my HTC_Amaze_4G using XDA Premium App
Click to expand...
Click to collapse
Yes, it will. In fact, that's basically all it does. Of course if you want to change /system/ you'll need to su to root first, then remount it RW. From there you can make any changes you want. The changes you make will persist across a reboot. To test this I deleted teeter.apk and teeter.odex from /system/app and rebooted. Teeter is now gone from my phone.
So, unless I'm misunderstanding what you mean, this is permanent root.
-xdadevelopers-user
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
xdadevelopers-user said:
Yes, it will. In fact, that's basically all it does. Of course if you want to change /system/ you'll need to su to root first, then remount it RW. From there you can make any changes you want. The changes you make will persist across a reboot. To test this I deleted teeter.apk and teeter.odex from /system/app and rebooted. Teeter is now gone from my phone.
So, unless I'm misunderstanding what you mean, this is permanent root.
-xdadevelopers-user
Click to expand...
Click to collapse
Revolution said:
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
Click to expand...
Click to collapse
For the record yes it dose, but your a dev next time try it b4 you post saying it don't work because u make yourself seem like you don't know what your talking about
Sent from my HTC_Amaze_4G using xda premium
I asked a question , i could speak and ask question's. kk .
Jaywan said:
For the record yes it dose, but your a dev next time try it b4 you post saying it don't work because u make yourself seem like you don't know what your talking about
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Revolution said:
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
Click to expand...
Click to collapse
Yes, you can make changes (add/edit/delete) to the files in /system.
I added:
/system/bin/su
/system/app/TitaniumBackup.apk
and deleted:
/system/app/teeter.apk
/system/app/teeter.odex
I did not edit anything in /system but I could if I had a reason to.
-xdadevelopers-user
for what it's worth...
I used the UOT kitchen to modify the battery to include percent. Since we don't have recovery yet I manually pushed the framework-res.apk and SystemUI.apk and then manually deleted the dalvik-cache. Now my status bar has the modified battery. Woohoo!
I was going to build a recovery today but android.git.kernel.org is STILL DOWN. Since the instructions I have require it I guess I'll wait for someone who already has the sources or until android.git.kernel.org comes back (I'm starting to wonder if it ever will).
-xdadevelopers-user
This is ****ing GENIUS work! Good job man. Pioneering for our amaze!
Not sure what I might be doing wrong but my su disappears after a reboot.
Try pushing to both xbin and bin
Sent from my HTC Sensation Z710e using xda premium
I did... No dice.
can you guys tell me what phone says when rebooting into hboot when its searching for a .zip, .nbh etc
its something like this
Example Sensation): PG58IMG.zip
It's not working for me.
C:\Users\Administrator\Desktop>adb push zergRush /data/local/
20 KB/s (21215 bytes in 1.000s)
C:\Users\Administrator\Desktop>adb shell
$ chmod 755 /data/local/zergRush
chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: Permission denied
$
Click to expand...
Click to collapse
EDIT
I removed the files in the tmp directory and it worked!
BUT
It's not consistent. When I reboot the su file disappears.
I've unlocked my bootloader. This may be required. Can anyone confirm that this works/fails on a locked bootloader?
-xdadevelopers-user
Finally, you sir are a genius
Sent from my HTC_Amaze_4G using Tapatalk
xdadevelopers-user said:
I've unlocked my bootloader. This may be required. Can anyone confirm that this works/fails on a locked bootloader?
-xdadevelopers-user
Click to expand...
Click to collapse
I'm on a locked bootloader. It doesn't work.
cmenard said:
I'm on a locked bootloader. It doesn't work.
Click to expand...
Click to collapse
Confirmed, same result for me on a locked bootloader. On reboot, it all goes away (or comes back).
Ive been googling on the intranet machine for awhile now and cant find out how to get the binary for this or just zipalign my apks another way. I am using ROM toolbox pro.
xxbgjhn159xx said:
Ive been googling on the intranet machine for awhile now and cant find out how to get the binary for this or just zipalign my apks another way. I am using ROM toolbox pro.
Click to expand...
Click to collapse
Download it and put it in /system/xbin. Then chmod it to 755. IF you need steps on how to do this, let me know.
http://dl.dropbox.com/u/34706306/zipalign
Yea I do. Im not sure what chmod it to 755 means. I know how to dl it n put it in the /system/xbin. Anywhere in there Im guessing.
Will this run the whole thing? Or is this just the binary for it? Would I still use ROM Toolbox run zipalign? THANKS a lot Ive been trying to find a fix for awhile.
Quick explanation:
Open a terminal emulator, navigate to /system/xbin with the "cd" command, and type "chmod 755 whateverthefileis". That'll change the permissions. If you want an explanation of what you're actually doing, you can read below. It's not necessary if you're not interested though.
If you're curious:
I guess I'll attempt briefly explaining the chmod command and Linux (Unix, Android, etc) permission notation. What do you want the file's permissions to be? In Linux, a file has an owner (who is the most intimately tied to the file), a group (which allows you to assign fewer privileges than the owner, but more control than default) and other (which means anyone not specified by the previous 2 conditions). For each of these groups, you can assign read, write, and execute permissions. These are written as rwx triplets. The notation "rwx" means full read, write, and execute permissions to whatever category of user that triplet is referring to. If you want to deny one of those permissions, replace the letter by the "-" placeholder. So "r-x" would mean that category of users wouldn't have write permissions. Files have these permissions listed in rwx triplets for the owner first, then the group, then others and are lead by what will usually be an initial "-" placeholder. So a file with permissions listed as "-rwxrw-r--" has an initial "-" placeholder like usual, followed by full rwx permissions for the owner, read and write permissions for the group, and read permissions for everyone else. You can view the permissions of any file by opening a terminal emulator, navigating to the directory where it is located and typing "ls -l" which will list details about each file in the directory, including permissions.
The chmod command in the form that was mentioned above, condenses the triplet describing the permissions for each group into a single number. It does this by treating permissible operations in each triplet as a 1, and operations that are denied as a 0. So if the owner's permissions are described as "rw-", this would translate into "110". This number is then read as binary and converted to decimal. 110 in binary equals 6 in decimal. So what "chmod 755 whateverfile" means is change the permissions of whateverfile to allow the owner full rwx permissions, allow members of the group the file belongs to read and execute permissions. And allow everyone else read and execute permissions as well. So "755" means "111|101|101" if you expand those back to the binary. And if we replace each 1 with the number it is representing, it will look like "rwxr-xr-x".
imchairmanm said:
Quick explanation:
Open a terminal emulator, navigate to /system/xbin with the "cd" command, and type "chmod 755 whateverthefileis". That'll change the permissions. If you want an explanation of what you're actually doing, you can read below. It's not necessary if you're not interested though.
Click to expand...
Click to collapse
I probably should check the threads I post assistance to a little more often. Thanks for responding.
I cant put the file into my /system/xbin. It says error permission denied or something like that. I cant save it straight to there either.
Type "su" and then hit Enter. When the box comes up for allowing privileges, allow them. Now try again.
Sent from my DROID X2 using Tapatalk
Hey everyone, I got this to work using ROM Toolbox Pro's root browser. Thanks for all the help!!!
how long did the script take? i'm already on about 30 minutes and am just curious if it'll be done before i leave the office @ 5.
works
Moon Shadow - NM said:
Download it and put it in /system/xbin. Then chmod it to 755. IF you need steps on how to do this, let me know.
http://dl.dropbox.com/u/34706306/zipalign
Click to expand...
Click to collapse
Works! thanks..
zipalign missing
Just logging in & want to say thanks for the help.
Nice tip for the starters as I am. Thanks
Moon Shadow - NM said:
Download it and put it in /system/xbin. Then chmod it to 755. IF you need steps on how to do this, let me know.
http://dl.dropbox.com/u/34706306/zipalign
Click to expand...
Click to collapse
May i know where you got that file from?
nuthng kinda happens after doin chmod...normal?
Sent from my Micromax Infinity P275 using xda premiumf
Hi,
Imagine a scenario where you have just system access on android , and you want to continually have it, so you use the su binary, with the correct permission and the setuid flag on, and the owner being system, you do:
Code:
chown 1000:1000 su2
chown 06755 su2
you have the ability to change the owner to system as you do when rooting, and you also set the appropriate permission as you do when rooting,
06775 being the permission code to all have execution permission, and the setuid flag on.
But when dealing with system permission that doesn't work. it only works with root.
I know it's a weird question, but if any could answer it, id be glad .... thanks
If i get you right you want your /system to be rw by user, without root?
Why on earth would you want such an insecure system?
It is a silly idea!
No, i want to su binary to work for system user, as it works for root user, when you just have system access. system user,
is much like root, but with less power. its uid is 1000.
CtrlAltDelIrl said:
If i get you right you want your /system to be rw by user, without root?
Why on earth would you want such an insecure system?
It is a silly idea!
Click to expand...
Click to collapse
And what is your point then?. Your idea?
I don't get it. Isn't having system access and having "root" the same thing? I mean, the definition of "root" is having system access, no?
can someone explain how to use bypasslkm in further detail. i looked through multiple threads but im stilll not getting the handle on it,
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD app
sfgrimes said:
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
Deleted
Sent from my SCH-I545 using Tapatalk
JTSDeveloper said:
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
I had the same issue. Here is the binary from Surges dropbox https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm
Make sure you copy it to the right directory and follow all the commands.
Sent from my SCH-I545 using XDA Premium HD app
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Surge1223 said:
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Click to expand...
Click to collapse
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
JTSDeveloper said:
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
Click to expand...
Click to collapse
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's still not working. Any ideas? Should I move it directly into /data/local/tmp
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
JTSDeveloper said:
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
Click to expand...
Click to collapse
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Solution to the 755 bypasslkm issue!!!!!
k1mu said:
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Click to expand...
Click to collapse
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
EinGlo said:
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
Click to expand...
Click to collapse
worked perfectly and all my confusion is now gone thank you.
Fix works but new issue
JTSDeveloper said:
worked perfectly and all my confusion is now gone thank you.
Click to expand...
Click to collapse
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
EinGlo said:
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
Click to expand...
Click to collapse
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Issue with auto-running my solution
k1mu said:
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Click to expand...
Click to collapse
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
update
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
I tried again.
Ok, so I figured out the coding a little bit. Im not used to this, so forgive my ignorance.
I did the code as u typed it. BUT I made a change. Because I kept getting the "file not found " error. I added ".bin" to the end of the bypasslkm code line. It generated a real response. I felt relieved. I went ahead and typed the last line of code.
THEN I was told the file already exists... I have attached a picture of what I got in android Terminal
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Question
k1mu said:
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Click to expand...
Click to collapse
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
EinGlo said:
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Click to expand...
Click to collapse
I'm sure there are programs that can be set up to run scripts as root during boot; However, that's complicated since you want this to run while the phone is booting, before there's any opportunity to allow SuperSU to ask for permission.
EinGlo said:
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Click to expand...
Click to collapse
That's a problem that's fixed by an edit to /system/etc/permissions/platform.xml, adding a stanza that permits external storage write access.
EinGlo said:
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
Click to expand...
Click to collapse
The need to run the "bypasslkm" program is because of the downgrade. If you go to a clean rooted Kit Kat ROM, it shouldn't have any issues with WiFi being enabled. That may be the easiest way to fix this.