Hey guys, I had lost my IMEI today.
I was lucky to find an auto-backed up .tar.gz file of my EFS folder.
Restored that folder and my IMEI is back and calls and everything is working.
Problem? I'm stuck in a permanent factory mode.
There's no lock screen, power menu directly reboots phone and there's a frustrating yellow overlay of my phone information. These things just won't go away whatsoever. Tried ODIN and a lot of methods on the internet.
Tried these via terminal emulator:
Code:
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
and tried to do these via root explorer apps also.
Please help I need to bring my phone back to life.
Edit: How I fixed it:
Not sure if step 1 is needed but this is how I did it. (I've used X-plore File Manager for all the file operations)
1.Change permission of every file and folder in /efs folder to 777. Reboot.
2.Delete the folder /efs/FactoryApp (NOT ENTIRE EFS FOLDER).
3.Wipe data/Factory Reset. (/efs/FactoryApp will get regenerated here)
4.Open /efs/FactoryApp/keystr file and change its contents to ON.
5.Open /efs/FactoryApp/factorymode file and change its contents to ON.
6. Reboot and your problem should be fixed now.
Are you doing it as root "su"?
What errors?
Sent from my GT-I9300 using Tapatalk 4
lmali92 said:
Hey guys, I had lost my IMEI today.
I was lucky to find an auto-backed up .tar.gz file of my EFS folder.
Restored that folder and my IMEI is back and calls and everything is working.
Problem? I'm stuck in a permanent factory mode.
There's no lock screen, power menu directly reboots phone and there's a frustrating yellow overlay of my phone information. These things just won't go away whatsoever. Tried ODIN and a lot of methods on the internet.
and tried to do these via root explorer apps also.
Please help I need to bring my phone back to life.
Click to expand...
Click to collapse
try this
https://docs.google.com/file/d/0B-9sw7RUYVLTQW5sSzR1aXJUams/edit?usp=sharing
install apk and open
method number 2 -go to efs/factory app/factorymode and open with file texteditor with root permission if is OFF you change in ON and save changes
but with apk is very easyer
rootSU said:
Are you doing it as root "su"?
What errors?
Click to expand...
Click to collapse
Hey, yes I'm doing it with su and there are no errors. I reboot after everything and it still stays the same.
Sent from my GT-I9100 using xda app-developers app
nik60 said:
try this
https://docs.google.com/file/d/0B-9sw7RUYVLTQW5sSzR1aXJUams/edit?usp=sharing
install apk and open
method number 2 -go to efs/factory app/factorymode and open with file texteditor with root permission if is OFF you change in ON and save changes
but with apk is very easyer
Click to expand...
Click to collapse
Hey I've tried method no. 2
I'll try that apk now and get back, thanks
Sent from my GT-I9100 using xda app-developers app
nik60 said:
try this
https://docs.google.com/file/d/0B-9sw7RUYVLTQW5sSzR1aXJUams/edit?usp=sharing
install apk and open
method number 2 -go to efs/factory app/factorymode and open with file texteditor with root permission if is OFF you change in ON and save changes
but with apk is very easyer
Click to expand...
Click to collapse
Tried the apk. Negative
No errors but still unsuccessful.
Sent from my GT-I9100 using xda app-developers app
If you look at the 4th command in post 1, if you browse to and open that file, does it say "on" in it?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
If you look at the 4th command in post 1, if you browse to and open that file, does it say "on" in it?
Click to expand...
Click to collapse
Yes I've checked both factorymode and keystr file, both are on. And I've also made sure their permissions are 744
Im using x-plore file manager.
Sent from my GT-I9100 using xda app-developers app
lmali92 said:
Yes I've checked both factorymode and keystr file, both are on. And I've also made sure their permissions are 744
Im using x-plore file manager.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
What permissions does the whole efs have?
wangdaning said:
What permissions does the whole efs have?
Click to expand...
Click to collapse
It's 771. What should it be?
Sent from my GT-I9100 using xda app-developers app
Logcat
OK I tried to logcat it and these are just a few of the unhealthy statements(A lot were repetitions I guess).
Code:
E/KeyguardViewMediator( 2258): cannot open file : /efs/FactoryApp/factorymode
E/FlashBarService( 2596): cannot open file : /efs/FactoryApp/factorymode
D/ActivityManager( 2258): cannot open file : /efs/FactoryApp/factorymode
W/System.err( 2832): java.io.FileNotFoundException: /efs/FactoryApp/factorymode: open failed: EACCES (Permission denied)
D/SetupWizardSkipReceiver( 3403): cannot open file : /efs/FactoryApp/factorymode
W/FactoryTestApp( 3403): WARNNING: java.io.FileNotFoundException: /efs/FactoryApp/hw_ver: open failed: EACCES (Permission denied)
E/FactoryTestApp( 3403): [Class] Support , [Method] setPermission , [Message] File not found : /efs/FactoryApp/hw_ver
W/FactoryTestApp( 3403): WARNNING: java.io.FileNotFoundException: /efs/FactoryApp/serial_no: open failed: EACCES (Permission denied)
E/FactoryTestApp( 3403): [Class] Support , [Method] setPermission , [Message] File not found : /efs/FactoryApp/serial_no
I know almost all of these are pointing towards permission problems but I don't know why they're occurring. I've set all the permissions according to all the suggestions I could find here on xda.
lmali92 said:
OK I tried to logcat it and these are just a few of the unhealthy statements(A lot were repetitions I guess).
Code:
E/KeyguardViewMediator( 2258): cannot open file : /efs/FactoryApp/factorymode
E/FlashBarService( 2596): cannot open file : /efs/FactoryApp/factorymode
D/ActivityManager( 2258): cannot open file : /efs/FactoryApp/factorymode
W/System.err( 2832): java.io.FileNotFoundException: /efs/FactoryApp/factorymode: open failed: EACCES (Permission denied)
D/SetupWizardSkipReceiver( 3403): cannot open file : /efs/FactoryApp/factorymode
W/FactoryTestApp( 3403): WARNNING: java.io.FileNotFoundException: /efs/FactoryApp/hw_ver: open failed: EACCES (Permission denied)
E/FactoryTestApp( 3403): [Class] Support , [Method] setPermission , [Message] File not found : /efs/FactoryApp/hw_ver
W/FactoryTestApp( 3403): WARNNING: java.io.FileNotFoundException: /efs/FactoryApp/serial_no: open failed: EACCES (Permission denied)
E/FactoryTestApp( 3403): [Class] Support , [Method] setPermission , [Message] File not found : /efs/FactoryApp/serial_no
I know almost all of these are pointing towards permission problems but I don't know why they're occurring. I've set all the permissions according to all the suggestions I could find here on xda.
Click to expand...
Click to collapse
Why don't you try setting perms to 777 and if it works start removing until it breaks.
Sent from my GT-I9505 using xda app-developers app
MemoryController said:
Why don't you try setting perms to 777 and if it works start removing until it breaks.
Click to expand...
Click to collapse
Tried. Didn't work. :banghead:
What if I delete the /efs/FactoryApp folder and factory reset the device?
It should automatically get regenerated right? And will my IMEI stay after that? :-|
Sent from my GT-I9100 using xda app-developers app
God it's finally gone. I think my whole FactoryApp folder was messed up.
I deleted it and wiped data from CWM. Rebooted and factory mode was still there. Opened both factorymode and keystr files and changed them from OFF to ON and rebooted again.
And I was greeted with the new phone setup on reboot
Thanks a ton all you fells. Problem fixed
Sent from my GT-I9100 using xda app-developers app
lmali92 said:
God it's finally gone. I think my whole FactoryApp folder was messed up.
I deleted it and wiped data from CWM. Rebooted and factory mode was still there. Opened both factorymode and keystr files and changed them from OFF to ON and rebooted again.
And I was greeted with the new phone setup on reboot
Thanks a ton all you fells. Problem fixed
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
hmmm interesting...
cannot find factoryapp
Hey I can't seem to find efs/factoryapp, it keeps telling me that the directory isn't there, I've done a factory reset via recovery mode it's still there, I can't exit factory mode
zachlag said:
Hey I can't seem to find efs/factoryapp, it keeps telling me that the directory isn't there, I've done a factory reset via recovery mode it's still there, I can't exit factory mode
Click to expand...
Click to collapse
OK I can confirm that you only need to delete the FactoryApp folder and do a factory reset for this to work. Dont worry about permissions. I couldnt get rid of the yellow writing even though my FactoryApp files said ON. Obviously corrupted because after deleting they said OFF, so changed to ON and fixed (6hours later!!!). All the abd stuff and terminal commands didnt work, only this solution. Dont worry the folder regenerates itself as he says so no risk.
jimmy080705 said:
OK I can confirm that you only need to delete the FactoryApp folder and do a factory reset for this to work. Dont worry about permissions. I couldnt get rid of the yellow writing even though my FactoryApp files said ON. Obviously corrupted because after deleting they said OFF, so changed to ON and fixed (6hours later!!!). All the abd stuff and terminal commands didnt work, only this solution. Dont worry the folder regenerates itself as he says so no risk.
Click to expand...
Click to collapse
i have
us cellular note 3 on mk2
i was rooted (supersu1.93) with twrp 2.6.3.7
i used es explorer to write off to both those files and rebooted,
comes back on
deleted the factory mode dir after i made backup on sd card
factory data reset
on still there and wont change to off
boot into twrp and wipe everything i can (dont think its wipe is really working well. its the first twrp officially for this device)
odin stock recovery
odin over full official mk2
factory mode still on upon boot
did a ##RTN#
still there
just wanted do add i dont have the yellow overlay and my power button works ok
i have swipe to unlock and no mobile data
if i set unlock to pattern it does stop and wait
if set to swipe to unlock it just goes right on past it on reboots
factory data mode is supposed to turn off isnt it?
what exactly is its function
well i just follow the directions with the echo commands and it actually made my phone worse
now i dont even see the swipe screen AND my power button has no menu to restart phone. when i hold power button in when phone is at ui it just shuts off now
that is new
i can edit them both to off but phone power button = shut down and no swipe screen seen at all upon boot
en11gma said:
i have
us cellular note 3 on mk2
i was rooted (supersu1.93) with twrp 2.6.3.7
i used es explorer to write off to both those files and rebooted,
comes back on
deleted the factory mode dir after i made backup on sd card
factory data reset
on still there and wont change to off
boot into twrp and wipe everything i can (dont think its wipe is really working well. its the first twrp officially for this device)
odin stock recovery
odin over full official mk2
factory mode still on upon boot
did a ##RTN#
still there
just wanted do add i dont have the yellow overlay and my power button works ok
i have swipe to unlock and no mobile data
if i set unlock to pattern it does stop and wait
if set to swipe to unlock it just goes right on past it on reboots
factory data mode is supposed to turn off isnt it?
what exactly is its function
well i just follow the directions with the echo commands and it actually made my phone worse
now i dont even see the swipe screen AND my power button has no menu to restart phone. when i hold power button in when phone is at ui it just shuts off now
that is new
i can edit them both to off but phone power button = shut down and no swipe screen seen at all upon boot
Click to expand...
Click to collapse
i made a backup before i deleted the /efs/FactoryApp directory. i copied the backup i made back into place and now i can see the swipe screen "for a sec or 2" and now my power button working but still stuck in factory mode.
really could use some help on this one as it looks like its really gonna be a good one
Thank you very much
lmali92 said:
Hey guys, I had lost my IMEI today.
I was lucky to find an auto-backed up .tar.gz file of my EFS folder.
Restored that folder and my IMEI is back and calls and everything is working.
Problem? I'm stuck in a permanent factory mode.
There's no lock screen, power menu directly reboots phone and there's a frustrating yellow overlay of my phone information. These things just won't go away whatsoever. Tried ODIN and a lot of methods on the internet.
Tried these via terminal emulator:
Code:
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
and tried to do these via root explorer apps also.
Please help I need to bring my phone back to life.
Edit: How I fixed it:
Not sure if step 1 is needed but this is how I did it. (I've used X-plore File Manager for all the file operations)
1.Change permission of every file and folder in /efs folder to 777. Reboot.
2.Delete the folder /efs/FactoryApp (NOT ENTIRE EFS FOLDER).
3.Wipe data/Factory Reset. (/efs/FactoryApp will get regenerated here)
4.Open /efs/FactoryApp/keystr file and change its contents to ON.
5.Open /efs/FactoryApp/factorymode file and change its contents to ON.
6. Reboot and your problem should be fixed now.
Click to expand...
Click to collapse
I had the exact same problem, spent the whole weekend looking for a fix,
Cheers mate ur a lifesaver.
Related
I installed the Galaxy S3 Retail Mode found in Google Play but had problems setting it up so I uninstalled it.
Now, I have a folder in /sdcard/ named RetailMode that contains photos used by the RetailMode application. But no matter what I do, I can't delete it. Can't delete any of the photos either.
I tried changing owners and changing permissions but failed. I even tried via adb shell.
Any ideas of how I can delete it?
Thanks in advance!
Beach_Head said:
I installed the Galaxy S3 Retail Mode found in Google Play but had problems setting it up so I uninstalled it.
Now, I have a folder in /sdcard/ named RetailMode that contains photos used by the RetailMode application. But no matter what I do, I can't delete it. Can't delete any of the photos either.
I tried changing owners and changing permissions but failed. I even tried via adb shell.
Any ideas of how I can delete it?
Thanks in advance!
Click to expand...
Click to collapse
Could try running a KIES update or one of the Jellybean OTA's that will wipe the internal sd card
Are you trying to do so as root? If you open a terminal (download Android Terminal from the market) and run:
Code:
su
rm -rf /sdcard/RetailMode
(upper/lower case is important!) what is the output?
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Steve_max said:
Are you trying to do so as root? If you open a terminal (download Android Terminal from the market) and run:
Code:
su
rm -rf /sdcard/RetailMode
(upper/lower case is important!) what is the output?
Click to expand...
Click to collapse
Beach_Head said:
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Click to expand...
Click to collapse
Reboot?
Tried that first. No go.
Since Retail Mode is installed and activated as a Device Administrator, I think it modified some settings. I just don't know what those settings are.
I don't want to re-flash so hopefully someone can help me with this...
kulisap said:
Reboot?
Click to expand...
Click to collapse
first you have to deactivate RetailMode as an administrator. than check if is also disabled in Accessibility also, just in case. than try to delete it. It might work.
Did that already too.
This is so frustrating...
Chaitanyapatel8880 said:
first you have to deactivate RetailMode as an administrator. than check if is also disabled in Accessibility also, just in case. than try to delete it. It might work.
Click to expand...
Click to collapse
only one choice left than... Full wipe...
There has to be another way...
Chaitanyapatel8880 said:
only one choice left than... Full wipe...
Click to expand...
Click to collapse
Had this one before but the app was smart app protector. Deleted it but it left a folder and cant delete it even in the pc. But iwas able to delete it using root explorer.
Sent from my GT-I9300 using Tapatalk 2
Beach_Head said:
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Click to expand...
Click to collapse
Install a BusyBox from the market (if you already have it, reinstall). if "rm" is trying to remove "-rf", it's NOT a standard "rm", which can explain your problems. Then try again.
After having followed the above: Should you get a "permission denied" as root (execute 'whoami' on the console to make sure you're root!)
then the file(s) is most probably flagged as immutable.
Executing the following will then resolve the issue: chattr -iR /sdcard/RetailMode
This is what I get when I issue that command: reading flags on /sdcard/RetailMedia: innapropriate ioctl for device
d4fseeker said:
After having followed the above: Should you get a "permission denied" as root (execute 'whoami' on the console to make sure you're root!)
then the file(s) is most probably flagged as immutable.
Executing the following will then resolve the issue: chattr -iR /sdcard/RetailMode
Click to expand...
Click to collapse
Since I upgraded to JB (official. spain's), each time I restart my phone I get the message "Unfortunately, factory mode has stopped".
and then I don't have lockscreen.
I know this topic was covered before, but no solution fixed it.
I already tried:
1. ensure /efs/IMEI/keystr exist and contain "ON" in it. (checked through emulator and explorer)
2. tried to create/check factorymode file exist. never found it, but iמ emulator wrote those lines:
su
echo -n ON > /efs/FactoryApp/factorymode
reboot
still nothing.
anyone can think of another solution?
maybe I'm doing something wrong with the factorymode file?
Do a full wipe/factory reset in recovery.
Shachar85 said:
Since I upgraded to JB (official. spain's), each time I restart my phone I get the message "Unfortunately, factory mode has stopped".
and then I don't have lockscreen.
I know this topic was covered before, but no solution fixed it.
I already tried:
1. ensure /efs/IMEI/keystr exist and contain "ON" in it. (checked through emulator and explorer)
2. tried to create/check factorymode file exist. never found it, but iמ emulator wrote those lines:
su
echo -n ON > /efs/FactoryApp/factorymode
reboot
still nothing.
anyone can think of another solution?
maybe I'm doing something wrong with the factorymode file?
Click to expand...
Click to collapse
Reboot into recovery format /system
Go into download mode and flash JB rom
Go back into download mode and flash Siyah v6 beta 4 kernel
Boot to recovery wipe data/factory reset
Boot device
Guys most of us encountered a similar problem like this - for no reason the lockscreen and power option menu wont work
sometimes you will get red warning like 'factory mode is on' some features wont work properly :crying::crying::crying:
Guys it's because of Corrupted EFS folder
So here is the exact solution to get rid of factory mode into user mode [get back your lockscreen and power option menu]
Its a proven method :victory::victory::victory:
You have to root your phone and install Terminal Emulator from Google Play.
Open terminal emulator and type as ;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
You now should not see the that message anymore. Its because of an EFS corruption.
Hope it helps!!!
Time to enjoy 'hurray' i got my lockscreen and power option menu
Anybody guys is that helped you...if yes please press thanks button...dont just see the post.
Sent from my GT-I8552 using Tapatalk 2
reserved
Hey please help me
When I type these code
Su
Bla bla bla
In terminal emulator
I get error
No such directory or file found
Please I want my lock screen anf power button back
Sent from my GT-I8262 using xda app-developers app
Omkar$ said:
Hey please help me
When I type these code
Su
Bla bla bla
In terminal emulator
I get error
No such directory or file found
Please I want my lock screen anf power button back
Sent from my GT-I8262 using xda app-developers app
Click to expand...
Click to collapse
Which means keystr and factorymode file already been removed...
Then you have to type only this:
Don't type just copy paste these codes
su
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
It will work definitely all the best..
Feedback me after u got ur buttons and lockscreen back
Sent from my GT-I8552 now Free
Got it?
Sent from my GT-I8552 now Free
Not working bro same error
I have addon.d, app,lost+found,reg_backup in my efs folder
Sent from my GT-I8262 using xda app-developers app
Omkar$ said:
Not working bro same error
I have addon.d, app,lost+found,reg_backup in my efs folder
Sent from my GT-I8262 using xda app-developers app
Click to expand...
Click to collapse
Do this manually
Install root explorer and open.
Go to efs/Factoryapp folder
Create a new file 'factorymode'
Open the file and type 'ON' and click save.
Create a new file 'keystr'
Open the file and type 'ONON' and click save
For both files permissions should be rwe-r-r
Reboot.
If it still don't work do the copy paste commands in emulator which is in first post after this..
It should work..I have successfully got my lockscreen and power menu button by this on my grand Quattro running JB 4.1.2
This is the only method to get back those...even u try reflashing your stock firmware u won't get it.do it again without mistakes in code..
In the code the first two line is to remove those two corrupted files and the next two steps is to add those two files and the following codes is to set permission which it needs minimum 777 permissions to work.....:beer::beer::beer: so if u get error like no such file directry exclude two lines below su.
Sent from my GT-I8552 now Free
Followed all above steps but not working
Alll codes worked
But after reboot no chage
I am using galaxy core jb 4.1.2
Can I use other galaxy core efs folderband flash it on my core
Btw I don't have factoryapp folder in efs instead I have app folder
Can u show your efs folder
Btw quattro is same as galaxy core
It should work
Sent from my GT-I8262 using xda app-developers app
How to take backup of efs folder for grand quattro? Please help me as I am new here.
Sent from my GT-I8552 using XDA Premium 4 mobile app
I have galaxy grand I9082 and your method worked fine but If i flash miui rom i cant get network signal, and i surprised that calls are coming but i cant make a call it says turn off flight mode how to resolve this.
efs folder empty after every reboot
fix?? plzzzzz
still no help
cannot create a file in efs mode as it says "file system is read-only"
what should i do ??????
i have rooted my phone ,installed terminal emulator and root explorer.
i have samsung galaxy quattro
Crap post...nothing worked !!
really need help
I 've followed step by step , the code runs fine but no change , lockscreen and power button menu still does not appear , I 've used a lot of ways such as EFS proffesional still no change , is there someone who can help me ? please
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?
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.