Enable all toggles + unlock native Tethering
If you have Safestrap installed and are on a MK2 or MJ7 rom/build you can flash the corresponding zip below and you will unlock native built-in tethering and also get all the toggles including the usually absent Wifi Hotspot toggle. Both versions have been tested and confirmed to be work. This also enables all the missing toggles, not only the Wifi Hotspot toggle. Toggle issue = solved. If you don't have Safestrap then let me know, I'll write up a script to do the same thing if needed.
@Scottchy014 made an awesome video of the process that you can watch here
Devs/Modders/Themers - You can use my script without my permission and you don't need to give me credit. I don't do this for ego/pride I'm already narcissistic enough as it is.
I545VRUFNC5_Tether_unlock_&_toggle.zip
md5:690b28f995fe7b33d2f1407a25b1abea
MJ7 Tether unlock w/ toggle
md5:b382d98e112adc5e48c7b37b2bb4bd6a
MK2 Tether unlock w/ toggle
md5:12e3eab158521d355ddd3956f340cf70
Verizon Galaxy S4 VRUEMJ7 Tether unlock
Unlocks WifiHotspot, USB Tether, and Bluetooth
Developed by Surge1223
11/02/2013
Please read the instructions; accidents while flashing framework-res.apk can and do happen and those mistakes lead to having to use full Odin restore tars. I almost made open1your1eyes0 brick had he not caught my mistake in the code. Luckily he was nice enough to test again, luckily that one worked
Instructions:
(Try the alternate method below first, it seems to work with less errors, but if you insist on using the script then FOR MK2 replace all instances of "MJ7" below with "MK2")
1. Extract MJ7_tether_unlock.zip and move the MJ7_tether_unlock folder to the root
of your micro sdcard so the structure looks like this: /mnt/extSdCard/MJ7_tether_unlock/
also make sure you have busybox installed and are using SuperSu and not the chinese superuser.
Finally, before continuing, remember to disable the Knox apps (5 I believe?) and security apps (the 4 VZW security apps) install busybox, remove the Chinese superuser, update SuperSu's binaries, enable usb debugging and under security disable verify apps while enabling unknown sources.
2. Download terminal emulator then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh tether.sh
3. After that your phone should reboot, and tethering should be unlocked! Also a copy of your original framework-res.apk
can be found in the following directory /mnt/extSdCard/MJ7_tether_unlock/orig-framework-res.apk
4. To restore back to your original framework-res.Code:apk, (i.e, relock tethering) then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh untether.sh
Downloads
MJ7
Download the zip here
Alternate link: Mirror
MD5: 029780a103ab8fb4929bb83b2270d6ef
To download just the modded MJ7 framework-res.apk click here
MK2
Download the zip here
MD5: ed0e0f974d7d8720690b8eb96461b5f3
To download just the modded MK2 framework-res.apk click here
ALTERNATE METHOD
DO NOT RENAME the original framework-res.apk file! You will have to use an Odin tar to recover!
1.Download the modded framework-res.apk from here for MJ7 or here for MK2 then copy it to /system first then change framework-res.apk's permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk. Then reboot and you should have tethering!
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
The Mod itself:
This is from the original arrays.xml
Code:
Code:
usb\\d
rndis\\d
wlan0
bt-pan
[color=red] [/color]
[color=red]com.samsung.spg
com.samsung.spg.NewSPGActivity[/color]
0
1
5
This is the modified arrays.xml
Code:
Code
usb\\d
rndis\\d
wlan0
bt-pan
0
1
5
[COLOR=Lime]7[/COLOR]
Give credit to @open1your1eyes0 for testing the second build after I screwed up the first just his input on the shell script and mod in general. Thanks internet, specifically this page. Also @Sir_Eagle for the MK2 framework-res.apk
Does this work on non rooted devices??
phgoodwrench said:
Does this work on non rooted devices??
Click to expand...
Click to collapse
Unfortunately, no. It has to overwrite a system file.
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Unfortunately, no. It has to overwrite a system file.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Was a stupid question. Just saw the first command in TE was to type SU. Guess I'll root this junk. Been putting it off forever since I didn't want to flash a ROM and tethering worked.
confirmed
I have gs4 Verizon running MJ7 4.3 and used this to unlock my tethering capability.
Thank you for this information and your work!
I have unlimited data plan and was stuck using WiFi router which burned up battery like crazy. This is so much better now.
Thanks again! :good:
Surge1223 said:
I see people complain about not having the Wifi or WifiHotspot toggles working depending on the rom they are on. The solution doesn't require SQLite Editor. You can solve this problem by appending the below to your /system/csc/feature.xml under <!-- Settings --> header by changing system to r/w while edition then chmod back to 644.
[/SIZE]
Code:
[SIZE=3]<CscFeature_Setting_DefQuickPanelOrder>Wifi;Bluetooth;Location;AirplaneMode;WiFiHotspot;SmartStay;AutoRotate;MobileData;SilentMode;PowerSaving;MultiWindow;AirGesture;AllShareCast;SBeam;Nfc;AirView;Sync;SmartScroll;DrivingMode;DormantMode;BlockMode</CscFeature_Setting_DefQuickPanelOrder>[/SIZE]
[/SIZE]
Click to expand...
Click to collapse
Not sure what you are saying here can you do a more detailed description?
Thanks
Sent from my VZW Galaxy Note 3
This is an amazing development and greatly appreciated, however, I don't understand the purpose of the APK file? Is this an APK that needs to be installed for any reason?
---------- Post added at 09:54 AM ---------- Previous post was at 09:52 AM ----------
Jsyme222 said:
This is an amazing development and greatly appreciated, however, I don't understand the purpose of the APK file? Is this an APK that needs to be installed for any reason?
Click to expand...
Click to collapse
Terribly sorry! I just read the developer note concerning the APK! OOPS! Forgot to read!
---------- Post added at 10:06 AM ---------- Previous post was at 09:54 AM ----------
Surge1223 said:
Verizon Galaxy S4 VRUEMJ7 Tether unlock
Unlocks WifiHotspot, USB Tether, and Bluetooth
Developed by Surge1223
11/02/2013
Please read the instructions; accidents while flashing framework-res.apk can and do happen and those mistakes lead to having to use full Odin restore tars. I almost made open1your1eyes0 brick had he not caught my mistake in the code. Luckily he was nice enough to test again, luckily that one worked
Instructions:
1. Extract MJ7_tether_unlock.zip and move the MJ7_tether_unlock folder to the root
of your micro sdcard so the structure looks like this: /mnt/extSdCard/MJ7_tether_unlock/
2. Download terminal emulator then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh tether.sh
3. After that your phone should reboot, and tethering should be unlocked! Also a copy of your original framework-res.apk
can be found in the following directory /mnt/extSdCard/MJ7_tether_unlock/orig-framework-res.apk
4. To restore back to your original framework-res.apk, (i.e, relock tethering) then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh untether.sh
Downloads
Download the zip here
Devs, I've included just the framework-res.apk w/ just the mod here so you can customize it more as needed for your roms.
The Mod itself:
This is from the original arrays.xml
Code:
</integer-array>
<string-array name="config_tether_usb_regexs">
<item>usb\\d</item>
<item>rndis\\d</item>
</string-array>
<string-array name="config_tether_wifi_regexs">
<item>wlan0</item>
</string-array>
<array name="config_tether_wimax_regexs" />
<string-array name="config_tether_bluetooth_regexs">
<item>bt-pan</item>
</string-array>
<array name="config_tether_dhcp_range" />
[COLOR=Red] [COLOR=Black]<[/COLOR]string[COLOR=Black]-array[/COLOR][/COLOR] name="config_mobile_hotspot_provision_app"[COLOR=Red]>[/COLOR]
[COLOR=Red]<item>com.samsung.spg</item>[/COLOR]
[COLOR=Red] <item>com.samsung.spg.NewSPGActivity</item>[/COLOR]
[COLOR=Red]</string-array[COLOR=Black]>[/COLOR][/COLOR]
<integer-array name="config_tether_upstream_types">
<item>0</item>
<item>1</item>
<item>5</item>
</integer-array>
This is the modified arrays.xml
Code:
</integer-array>
<string-array name="config_tether_usb_regexs">
<item>usb\\d</item>
<item>rndis\\d</item>
</string-array>
<string-array name="config_tether_wifi_regexs">
<item>wlan0</item>
</string-array>
<array name="config_tether_wimax_regexs" />
<string-array name="config_tether_bluetooth_regexs">
<item>bt-pan</item>
</string-array>
<array name="config_tether_dhcp_range" />
<array name="config_mobile_hotspot_provision_app" />
<integer-array name="config_tether_upstream_types">
<item>0</item>
<item>1</item>
<item>5</item>
[COLOR=Lime] <item>7</item>[/COLOR]
</integer-array>
I see people complain about not having the Wifi or WifiHotspot toggles working depending on the rom they are on. The solution doesn't require SQLite Editor. You can solve this problem by appending the below to your /system/csc/feature.xml under <!-- Settings --> header by changing system to r/w while edition then chmod back to 644. Following your next reboot/hot reboot/restarted systemui, pull down the toggle bar, click the settings button and it should allow you to choose to add any that weren't available previously.
Code:
[SIZE=3]<CscFeature_Setting_DefQuickPanelOrder>Wifi;Bluetooth;Location;AirplaneMode;WiFiHotspot;SmartStay;AutoRotate;MobileData;SilentMode;PowerSaving;MultiWindow;AirGesture;AllShareCast;SBeam;Nfc;AirView;Sync;SmartScroll;DrivingMode;DormantMode;BlockMode</CscFeature_Setting_DefQuickPanelOrder>[/SIZE]
Give credit to @open1your1eyes0 for testing the second build after I screwed up the first just his input on the shell script and mod in general. Thanks internet, specifically this page.
Click to expand...
Click to collapse
I am so happy to have tether again, but I am very curious as to how this goes unnoticed by Verizon? Since this gets processed through the native tethering app how does it stay below the radar of Big Red?
Caution
Southern_mind said:
Not sure what you are saying here can you do a more detailed description?
Thanks
Sent from my VZW Galaxy Note 3
Click to expand...
Click to collapse
So I saw this portion of the thread and thought I would try to achieve this also. I messed with the system folder and totally bricked my phone. No hope of recovery. It was my fault for messing with something that I knew nothing about but just want to caution anyone thinking of doing this to be very careful.
I changed permissions for this folder and locked up the phone and it won't even let me Odin, flash through recovery or sideload through adb.
So my device is toast.
Just be wary of messing with things unfamiliar.
dimitrisg said:
So I saw this portion of the thread and thought I would try to achieve this also. I messed with the system folder and totally bricked my phone. No hope of recovery. It was my fault for messing with something that I knew nothing about but just want to caution anyone thinking of doing this to be very careful.
I changed permissions for this folder and locked up the phone and it won't even let me Odin, flash through recovery or sideload through adb.
So my device is toast.
Just be wary of messing with things unfamiliar.
Click to expand...
Click to collapse
Sorry I changed the directions because I could have been more clear. You messed with the system folder? I was saying to make the system r/w and chmod 644 the file feature.xml under /system/csc/. The system folder it self should be chmod 755, but you dont chmod the system to anything, leave the system folder alone in fact never change the permissions of /system or any folder within the /system directory, only change it on files within a folder. For example /system and /system/csc should both be rwxr-xr-x (755) and never changed, while /system/csc/feature.xml should have its permissions set to rw-r--r-- (644) What do you mean you cant Odin what happens when you try?
what's chmod 644?? I've been around a while but I never heard that before?
Sent from my VZW Galaxy Note 3
Southern_mind said:
what's chmod 644?? I've been around a while but I never heard that before?
Sent from my VZW Galaxy Note 3
Click to expand...
Click to collapse
When people say"push the app to /system and then change permissions" the permissions they are referring to is setting chmod the app to 644 which is setting the permissions for the owner, group and others.
chmod 644 = rw-r--r--
Owners -6 = read and write
Group - 4 = read only
Others -4 = read only
Number convention:
4 = read only
2 = write only
4 + 2 = 6
6 = read and write
5 = read and execute
5+2 =7
7= read, write and execute
Sent from my SCH-I535 using xda app-developers app
Southern_mind said:
what's chmod 644?? I've been around a while but I never heard that before?
Click to expand...
Click to collapse
That's the UNIX "change mode" command. That's the way that UNIX systems define the protection mode for files.
644 is a protection mode, meaning read/write for owner (6), read for group (4), read for all (4).
Your root file manager should be able to allow you to set the mode and ownership of any file that you copy around.
Surge1223 said:
When people say"push the app to /system and then change permissions" the permissions they are referring to is setting chmod the app to 644 which is setting the permissions for the owner, group and others.
chmod 644 = rw-r--r--
Owners -6 = read and write
Group - 4 = read only
Others -4 = read only
Number convention:
4 = read only
2 = write only
4 + 2 = 6
6 = read and write
5 = read and execute
5+2 =7
7= read, write and execute
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
k1mu said:
That's the UNIX "change mode" command. That's the way that UNIX systems define the protection mode for files.
644 is a protection mode, meaning read/write for owner (6), read for group (4), read for all (4).
Your root file manager should be able to allow you to set the mode and ownership of any file that you copy around.
Click to expand...
Click to collapse
Well thanks for the info. I've been doing that for years and didn't know that.
Surge1223 said:
Sorry I changed the directions because I could have been more clear. You messed with the system folder? I was saying to make the system r/w and chmod 644 the file feature.xml under /system/csc/. The system folder it self should be chmod 755, but you dont chmod the system to anything, leave the system folder alone in fact never change the permissions of /system or any folder within the /system directory, only change it on files within a folder. For example /system and /system/csc should both be rwxr-xr-x (755) and never changed, while /system/csc/feature.xml should have its permissions set to rw-r--r-- (644) What do you mean you cant Odin what happens when you try?
Click to expand...
Click to collapse
I am certainly not blaming anyone for this, it was clearly my fault for messing where I shouldn't be but I appreciate you wanting to help.
After I changed the system folder permissions, it immediately crashed. When it rebooted it bootlooped twice then booted into system recovery where the android guy lay on his back dead with a red exclamation point in his belly. It simply said error and nothing else but gave options to update, reboot, wipe, the usual.
I tried every file to be had that I could download for Odin, or recovery update. Odin simply failed every time. Recovery update always said signature match fail on every rom file. I must have tried 6 different rom files including one that is claimed to be the ME7 newest update untouched.
All methods completely failed.
I have rooted for years, installed countless ROM files on all my phones and this is the first I have bricked. I am not anything more than a reader that follow directions when it comes to this stuff, but have always been able to fix any problems until this one.
I have read threads on unbricking until I am sick of reading and trying. I guess its time to throw in the towel.
Thanks for updating the directions so nobody else does the stupid that I did.
dimitrisg said:
I am certainly not blaming anyone for this, it was clearly my fault for messing where I shouldn't be but I appreciate you wanting to help.
After I changed the system folder permissions, it immediately crashed. When it rebooted it bootlooped twice then booted into system recovery where the android guy lay on his back dead with a red exclamation point in his belly. It simply said error and nothing else but gave options to update, reboot, wipe, the usual.
I tried every file to be had that I could download for Odin, or recovery update. Odin simply failed every time. Recovery update always said signature match fail on every rom file. I must have tried 6 different rom files including one that is claimed to be the ME7 newest update untouched.
All methods completely failed.
I have rooted for years, installed countless ROM files on all my phones and this is the first I have bricked. I am not anything more than a reader that follow directions when it comes to this stuff, but have always been able to fix any problems until this one.
I have read threads on unbricking until I am sick of reading and trying. I guess its time to throw in the towel.
Thanks for updating the directions so nobody else does the stupid that I did.
Click to expand...
Click to collapse
Did you try to use adb at all? Where does odin fail at? You can try three suggestions I have, but first install android-sdk tools and make sure adb is working.
1. Connect your phone to your pc via usb and run the attached adb_system_fix.bat file found in the the Samsung_Tools folder ive uploaded here while your phone is attempting to boot.
2. Boot to recovery and try the to use adb/ab sideload there and enter the following
Code:
adb shell su -c "mount -o remount rw /system"
adb shell chmod 755 /system
3.(last resort, try any other suggestion first!)
Download the VRUEMJ7 stock odin tar from here and extract the .pit file from within (temporarily rename the tar.md5 to tar to extract) then boot to download mode and open Odin 3.09 and select the pit file in the pit slot (also check repartition) and the odin tar in AP. Hit start
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Did you try to use adb at all? Where does odin fail at? You can try three suggestions I have, but first install android-sdk tools and make sure adb is working.
1. Connect your phone to your pc via usb and run the attached adb_system_fix.bat file found in the the Samsung_Tools folder ive uploaded here while your phone is attempting to boot.
2. Boot to recovery and try the to use adb/ab sideload there and enter the following
Code:
adb shell su -c "mount -o remount rw /system"
adb shell chmod 755 /system
3.(last resort, try any other suggestion first!)
Download the VRUEMJ7 stock odin tar from here and extract the .pit file from within (temporarily rename the tar.md5 to tar to extract) then boot to download mode and open Odin 3.09 and select the pit file in the pit slot (also check repartition) and the odin tar in AP. Hit start
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Wow! Ok, sounds promising. Will do so now. I will post again with results.
Thanks!:fingers-crossed:
---------- Post added at 09:12 PM ---------- Previous post was at 08:37 PM ----------
Surge1223 said:
Did you try to use adb at all? Where does odin fail at? You can try three suggestions I have, but first install android-sdk tools and make sure adb is working.
1. Connect your phone to your pc via usb and run the attached adb_system_fix.bat file found in the the Samsung_Tools folder ive uploaded here while your phone is attempting to boot.
2. Boot to recovery and try the to use adb/ab sideload there and enter the following
Code:
adb shell su -c "mount -o remount rw /system"
adb shell chmod 755 /system
3.(last resort, try any other suggestion first!)
Download the VRUEMJ7 stock odin tar from here and extract the .pit file from within (temporarily rename the tar.md5 to tar to extract) then boot to download mode and open Odin 3.09 and select the pit file in the pit slot (also check repartition) and the odin tar in AP. Hit start
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can you give me some direction on how to perform the adb operation. I am able to boot to recovery, I have adb installed and know how to access it from CMD window. But not sure how to send commands to phone.
Can you help a little more?
I tried method 1 but it did nothing. What I did was starting the bat file and then booted phone. It just kept buzzing over and over like a fast bootloop.
Going to try method 2 but a little lost.
Please help a little more?
Thanks
dimitrisg said:
Wow! Ok, sounds promising. Will do so now. I will post again with results.
Thanks!:fingers-crossed:
---------- Post added at 09:12 PM ---------- Previous post was at 08:37 PM ----------
Can you give me some direction on how to perform the adb operation. I am able to boot to recovery, I have adb installed and know how to access it from CMD window. But not sure how to send commands to phone.
Can you help a little more?
I tried method 1 but it did nothing. What I did was starting the bat file and then booted phone. It just kept buzzing over and over like a fast bootloop.
Going to try method 2 but a little lost.
Please help a little more?
Thanks
Click to expand...
Click to collapse
Alright open a cmd prompt as admin. Then type:
Code:
adb devices
It should say something
Then type
Code:
adb shell
su
mount -o remount,rw /system
chmod 755 /system
adb reboot
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Alright open a cmd prompt as admin. Then type:
Code:
adb devices
It should say something
Then type
Code:
adb shell
su
mount -o remount,rw /system
chmod 755 /system
adb reboot
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well as expected it failed. Anything I type in and enter I get "error: closed"
It is a lost cause I am afraid.
I am considering method 3 and can follow most of the instructions, but the last instruction is where I lose you. It says "..and the Odin file in the AP". is that supposed to be PDA?
After this I wont bug you anymore since it is obviously a lost cause.
Thanks for everything.
dimitrisg said:
Well as expected it failed. Anything I type in and enter I get "error: closed"
It is a lost cause I am afraid.
I am considering method 3 and can follow most of the instructions, but the last instruction is where I lose you. It says "..and the Odin file in the AP". is that supposed to be PDA?
After this I wont bug you anymore since it is obviously a lost cause.
Thanks for everything.
Click to expand...
Click to collapse
Alright I sent you a pm
Will this trigger any part of verizons security? will the system know if something was flashed?
Related
Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.
Can someone knowledgeable please submit a detailed post, which instructs how to remove any files added during the Root Process, as well as any other file permission changes or modifications of any other type?
I see many half assed posts in these forums made by unqualified members, which are nothing but a waste of time and clutter this great resource. I would appreciate it if this post could be addressed by those who truly understand this process.
The file that was used to Root the SCH-i905 from Verizon was the one attached to this post.
Thanks in advance! This could be a great learning tool if answered properly.
Can some one please respond? Or is it that everyone is too scared to post helpful information?
Well, since no one was of any assistance, I was forced to piece together information and come to an understanding of how this works, and how to fully reverse what was done by this Root Update.
To begin, I would like to mention, that removing Superuser.apk from the /system/app folder, along with 'su' from the /system/bin folder, will negate your Root Access, and put you back to your default levels of access. This will prevent Mobile Device Management Solutions, such as AirWatch, Zenprise, or MobileIron from detecting your device as being compromised.
I was not successful in removing these two files via the ADB shell, however I was successful when using a Terminal Emulator App on the Device itself.
1.) I began by installing a free Terminal Emulator from the Android Market.
2.) Launched the Terminal Emulator and typed 'su' , then pressed Enter to gain Root Shell Privileges.
3.) From the Root Shell, I typed the following commands to remount the '/System' Directory to gain Read/Write Access.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
4.) I typed the following commands to remove 'Superuser.apk' and 'su'.
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
5.) Type the following command to remount the '/System' Directory back to Read Only.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
6.) Sync your device with Google under Settings / Accounts & Sync.
7.) Reboot your device, and you are good to go.
It might be a good practice to perform a Factory Reset on your device after doing this, however this is not completely necessary. I tested the Air-Watch Agent installation after performing the procedure mentioned above, and the Air-Watch console no longer detected my device as being compromised.
I will add that on my sch-i905 I found the bin directory under system not under system/app. For me, replacing cd /system/app/bin with cd /system/bin did the trick but the rest worked a treat - thanks for the post!
Thanks for pointing out my typo. I corrected the path in my Post.
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
tbcpn said:
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Stock Recovery isn't required to Root the device. However, if you wish to install CWM via ROM Manager from the Android Market, Root Permissions are required.
If you use an ODIN Flash of CWM, there is no need for Root Permissions because you are flashing via ODIN.
The stock recovery zip file that you referenced in the other post should be fine.
Just use ODIN to Flash back to Stock Recovery and use the process that I mentioned to remove Root Permissions and Super User, and you should be all set to return your device after a Factory Wipe.
Cheers!
~Scott~ said:
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Scott,
I'm sorry for just seeing your post. I'm sure that you figured it out by now. You need to gain Root Access to your device again to remove Super User. You are in a Catch22.
If you are using an SCH-I905, Root your device, then download Script Manager from the Android Market.
Run this very simple Bash Script that I wrote to remove Root and Super User.
Paste this into notepad and save it as Unroot.sh then run with Script Manager.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Be sure to run the Script as Root from within Script Manager. The app will kind of freeze up as soon as it runs, which is normal. This will certainly take care of your problem.
Thanks for your post of stockrec in a different post. You saved me a month ago with that one.
Cheers!
Will Samsung know if I rooted my GT 10.1 LTE after using these commands, and sending in for warranty?
Does anyone know how often airwatch checks for the root? anyway to bypass the checks?
Is this the same for the US Cellular 4G Tablet? I have been reading and all that I have found was WiFi only files. Which if I were to root with those I lose the 4G radio.
Perfect.. Just what I need. Thanks
The thing wont recognize my phone and wont show the options to do xrecovery or any of the other options except for Flash...please help im desperate for a rom
You need to root first.
Here: http://forum.xda-developers.com/showthread.php?t=1196421
Then in flashtool click 'ask root permissions' and have your phone unlocked and accept superuser permissions w/the prompt on your phone. Then you're good to go.
*edit- make sure it is the fixed xrec for 2.3.3. I use a Rom w xrec included so I didn't have to install it & I dont remember if that's the one in flashtool now.
Which firmware version are you on?
I have done that already...i am rooted because I have superuser on my phone. Where do I check firmware?
Sent from my X10i using XDA App
zm4 said:
I have done that already...i am rooted because I have superuser on my phone. Where do I check firmware?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
unzip xrecovery file and copy all files manually to the right places using root explorer then check all boxes on permitions.
reboot and try
How do i do that?
zm4 said:
How do i do that?
Click to expand...
Click to collapse
a very old guide written by me HERE
read "2nd mode" but use xrecovery v3 instead the one linked there
will this work for 2.3.3?
zm4 said:
will this work for 2.3.3?
Click to expand...
Click to collapse
these commands still the same you just need to change (eventually) to the right path.
check the zip structure to see that
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/xrecovery.tar of=/system/bin/xrecovery.tar
reboot
chargemon to \system\bin
charger to \system\bin
sh to \system\xbin
xrecovery.tar to \system\xbin
i dont see any busybox file or anything like that...please help i dun think busybox has been installed...
zm4 said:
i dont see any busybox file or anything like that...please help i dun think busybox has been installed...
Click to expand...
Click to collapse
ok...you have a reading problem kiddin´
Crowds said:
these commands still the same you just need to change (eventually) to the right path.
check the zip structure to see that
Click to expand...
Click to collapse
type this:
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/charger of=/system/bin/charger
dd if=/sdcard/sh of=/system/xbin/sh
dd if=/sdcard/xrecovery.tar of=/system/xbin/xrecovery.tar
reboot
this should do it
cheers
where do i get this adb thing?
zm4 said:
where do i get this adb thing?
Click to expand...
Click to collapse
forguet it...
copy all files to sdcard then copy/paste to the right places after that use root explorer and do this ON EVERY FILE YOU COPIED:
HTML:
- Press and hold on each file;
- Check all Permitions on the drop down menu;
- After changes were made save and exit;
- Reboot.
try enter on xrec
*Cannot open for read: No such or directory* wth?
where does meta go?
zm4 said:
where does meta go?
Click to expand...
Click to collapse
Anywhere. Just copy the files I told you to. I didn't referred anything about that, did I?
Sent from my X10 Erenz MIUI 1.9.2 using Tapatalk
Just start all over with flashtool it will work then.
Go to settings then applications, then development, check debug mode.
Start flash tool on your pc and connect the phone
IF the phone is rooted, it should be recognized by flash tool
On flash tool click ask root perm, look at your phone screen, superuser should pop up asking if to give permission, simply choose allow.
Then click recovery on flash tool and wait a sec....
should pop up asking which gingerbread version to use. choose 0.3GB, since its gb version you have.
when you're ready to use xrecovery, restart the phone
as soon as the phone comes on and the first sony ericsson name comes up, keep pressing the back button, xrecovery will come up.
i did both kernel things...but the thing is it won't recognize my device as a rooted device...i have superuser and I have used apps that require root...so i guess the problem is well idk...and thats what i need help with sorting out.
1. Install busybox from market (xrec needs busybox)
2. Give root explorer root acces and mount /system writeable (look in settings of your file explorer)
3. Copy files to right place:
chargemon to /system/bin
charger to /system/bin
sh to /system/xbin
xrecovery.tar to /system/xbin
4. Give above files the right permissions (long touch on file and choose property option):
user > read, write, execute
other > read, execute
group > read, execute
Hi everyone.
I apologize for my first post because it's not one helping, but one asking for help instead.
I have recently struggled with the problem of not being able to move apps to the SD card which you may already be aware of.
So I read somewhere about changing some things on /system/etc/permissions/platform.xml and I had the stupid idea to try to change it without really understanding it.
So I did some ****. Now I can't mount sd (internal or external) and I don't have permissions to restore platform.xml (I have a platform.xml.bak in the same directory which is identical to the original one).
So I was wondering if there could be any trick to restore it. Neither ES File Manager nor Terminal Emulator were capable of replacing the files or edit platform.xml's content (even with root access, su - with terminal emulator).
What could I do? I honestly don't think a factory reset would solve that.
My ROM is stock UBDLI2 (4.1.1) which I found kinda hard to find.
Since you haven't posted a log of your Android Terminal Emulator session, here's my guess at trying to resolve this:
Code:
su
mount -o remount,rw /system
mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
If you need it, chown root.root platform.xml && chmod 644 platform.xml.
similar problem with platform.xml
qwerty12 said:
Since you haven't posted a log of your Android Terminal Emulator session, here's my guess at trying to resolve this:
Code:
su
mount -o remount,rw /system
mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
If you need it, chown root.root platform.xml && chmod 644 platform.xml.
Click to expand...
Click to collapse
I was trying to replace my platform.xml file with a modified platform.xml file and in doing so I moved the 0riginal platform.xml file to another folder (just in case I needed the 0riginal again), I changed the permissions of the permissions folder and rebooted for them to take affect without having the platform.xml file in there and boom I'm in never-never-bootloop land. Can anyone help me or does this phone need to be used for skeet shooting? Thanks in advance!
Reflash the same rom, no wipe.
boomboomer said:
Reflash the same rom, no wipe.
Click to expand...
Click to collapse
Thanks for the reply. I was rooted but still on stock since I had yet to successfully get a custom recovery on my phone (apparently SGH-I337 on the BN1 baseband is tough to get a custom recovery on)...so I only have the stock recovery which really doesn't offer many options. And everytime I have tried to flash anything via the custom recovery it fails due to it not being signed (or at least I think that is what it says). I'm open to try anything if you got more ideas.
Odin
Odin
boomboomer said:
Odin
Click to expand...
Click to collapse
I don't want to be "that guy" as described in your signature...so I want to first say I have searched on this, but I have only found various sections on Odin instructions for various versions of Odin typically pertaining to one specific topic rather than an actual manual/guide for how to use Odin to reinstall a file that was idiodically removed (that'd be me....the idiotical remover of pertinent files). So I hate ask you for more help, but I only can't seem to get anything I try flashing with odin to work, I'm not sure if I'm putting things in the wrong slot (BOOTLOADER, PDA, PHONE, CSC) or what, but I really need some guidance.
Go read the sticky thread in general forum, how to flash with Odin, you can only flash the whole firmware not one file.
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.