Related
Hi Guys , sorry for my bad english i'm European.
I dont know why but on my SGS II i9100 on every ICS rom , Samsung or Unofficial i get no lock screen or power off menu. The only fix i attempted is Permissions Fix from CWM but lockscreen is still missing.
Any fixing methods?
Hi,
just want to make sure, you happened to choose "No scree lock" for Screen security?
Settings>Security>Screen lock
kkipsy said:
Hi Guys , sorry for my bad english i'm European.
Click to expand...
Click to collapse
That would be a terrible excuse if you were from the UK
Anyway, have you wiped data and caches?
re
hehe ^^
does not matter what i chose from settings , no lock , slide , pattern or pin. screen lock simply does not work.. and when i press the power button ( lock button ) for 2 seconds the phone shuts down , without the power off confirmation. pretty annoing.
Yes xethor , i did. Steps i did : permission fix from CWM , data / cache delete , factory reset.. still nothing
i dont think it's beacause of the custom ROM , i get no lockscreen in oficial sammy rom or any ICS rom.
Pretty sure this is the 3rd fail thread on this in as many days. Why you guys make new threads every time instead of using dedicated threads is beyond me.
Anyway, see posts in other threads.
Odia said:
# echo -n ON > /efs/imei/keystr
# reboot
Click to expand...
Click to collapse
oinkylicious said:
There's plenty of other information in the threads dealing with these ROMs too. If only people would ask/read there, rather than making new threads for every issue they encounter.
(potential original source in T989 forums http://forum.xda-developers.com/showthread.php?t=1438451)
Click to expand...
Click to collapse
re
# echo -n ON > /efs/imei/keystr
# reboot
i'm a noob in this kind of stuff... i dont know how to operate those commands.
ew
please , can someone redirect me to a thread where those commands are explained , how i run those commands on a rooted ICS sgs2?
hmmm , my first quess , is that i must use some app to navigate to efs/imei , and edit keystr file ... i will try that! also make a backup of EFS folder!!
kkipsy said:
please , can someone redirect me to a thread where those commands are explained , how i run those commands on a rooted ICS sgs2?
Click to expand...
Click to collapse
- Download "Terminal Emulator" app from market
- open it
- type into the command shell you just got:
Code:
su
echo -n ON > /efs/imei/keystr
sync
reboot
re
thank you HellcatDroid and oinkylicious ! problem solved !
my problem solved to!!!! thank you man !!!
thanks!!! it's help me also!
don't wanna be the scrub, but my lock screen is still gone. restored all of my efs backups and it's still not back any other thoughts?
EDIT: after a bit of derp on my part, I realized that the EFS folder wasn't keeping my changes despite all the attempts to restore the keystr file. In order to fix this, I had to set all permissions to 777, then reset the keystr file to ON. Once I had my lockscreen and boot menu back I just rebooted into CWM and proceeded to fix permissions.
in short, if the editing doesn't work:
1) Change permissions of the EFS and IMEI folder to 777
2) edit the keystr file
3) fix permissions in CWM
And how did I set efs and imei permission. Plz?
It fixed mine too!!! however the IMEI still starts with 00... I know thats not right since samsungs imei starts with 3 soemthing. please help how i can restore my original imei
thanks
My I9100 has a problem when I use sammy roms, the lockscreen never apears. this happened after I installed my first ICS rom. a friend encountered the same problem and was able to fix it by running these commands on the terminal emulator:
su
echo -n ON > /efs/imei/keystr
sync
reboot
this does not solve my problem, would it be possible that the cause of the problem is that the keystr file has the incorrect permissions? the file currently has these permissions: -rw------- I try and fix the permissions from CWM and the recovery hangs, It says fixing permissions and it never finishes.
any suggestions?
Note: when I flash CM9 or an akop rom the lockscreen does work
Tried to flash sammy with full wipe?
przemcio510 said:
Tried to flash sammy with full wipe?
Click to expand...
Click to collapse
yes, I tried, factory reset x3, wipe cache x3, wipe dalvik x 3 and even wipe sys.
Wooo, so that's strange, maybe flash other version?
I have tried over 7 sammy roms, and the problem persists, on CM9 the problem is fixed, but sammy roms work better for me
Just try it like this:
# su
# echo -n ON > /efs/imei/keystr
# reboot
nutricionven said:
would it be possible that the cause of the problem is that the keystr file has the incorrect permissions? the file currently has these permissions: -rw-------
I try and fix the permissions from CWM and the recovery hangs, It says fixing permissions and it never finishes.
any suggestions?
Note: when I flash CM9 or an akop rom the lockscreen does work
Click to expand...
Click to collapse
Your instincts are correct. The file needs at least 644 permissions, or rw-, r--, r--. "Fix permissions" from recovery does not fix this. Long click the file from root explorer and adjust the permissions there.
Or, from terminal emulator type:
su
chmod 644 /efs/imei/keystr
ctomgee said:
Your instincts are correct. The file needs at least 644 permissions, or rw-, r--, r--. "Fix permissions" from recovery does not fix this. Long click the file from root explorer and adjust the permissions there.
Or, from terminal emulator type:
su
chmod 644 /efs/imei/keystr
Click to expand...
Click to collapse
that solved my problem thanks
OK, so I have a rooted I9300 and for some reason for the last few weeks I cant update the subinary and titanium wont get root access.
I did many google searches, tried a few thing eg (http://forum.xda-developers.com/showthread.php?t=1900217) , tried rooting again (even though I know Im rooted but nothing works.
So the next thing I want to try is to unroot my phone and root again.
My question is, because I cant access titanium to back everything up,
is there a way to unroot WITHOUT losing all apps and data?
Thanks a lot in advance.
Make nandroid backup and restore apps using titanium when your phone are rooted again.
Use MybackupPro to backup messages/contacts/bookmark/system setting/bookmarks.
Sent from my GT-I9300 using xda app-developers app
Uninstall super su via Google Play and reinstall .
jje
Cant use nandroid. It needs busybox which requests root access.
JJEgan said:
Uninstall super su via Google Play and reinstall .
jje
Click to expand...
Click to collapse
Tried it- it wont uninstall but go back to an earlier version.
Reinstalled the latest version and Im getting the same message.
Root checker app says "This device does not have proper root access".
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
qwerty12 said:
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
Click to expand...
Click to collapse
I tried rooting again- didn't change anything.
I do have CWM.
Tried using ADB, but it requests root access and fails to get it...
tomerstern said:
I do have CWM.
Click to expand...
Click to collapse
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
If you don't already have ADB setup and the correct drivers installed (if you already have Kies installed then you have the drivers installed). do the following. You can check, if you wish, by seeing when you connect your phone in recovery - you should have a SAMSUNG Android ADB Device under SAMSUNG Android Phone or an Android Debugger Bridge device in Device Manager. If not:
Download http://dl.google.com/android/repository/platform-tools_r14-windows.zip and extract the three files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to a place of your choosing
install the drivers: http://www.mediafire.com/?2243ouw1701zp8l (Extracted from Kies_2.5.0.12094_27_11.exe)
disconnect and reconnect your phone
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
That should unroot your phone.
Go to "Install ZIP from sdcard" and choose to install a zip from the internal sdcard.
Exit out of the root shell (Ctrl+C or, alternatively, "exit" and you'll be sent back to the command prompt) on your computer and download the SuperSU ZIP.
Go back to the command prompt and type this "adb push " (including the space) and drag the CWM-SuperSU-v0.96.zip onto the command prompt window, add a space and type "/data/media". You should have something like "adb push <path to CWM-SuperSU-v0.96.zip> /data/media"
This should put the SuperSU ZIP onto the root of your internal memory card. Choose go back on your phone and select to install a ZIP from the internal memory card again. You should see CWM-SuperSU-v0.96.zip. Install it, reboot, update SuperSU from the Play Store and run SuperSU from the app drawer. You should get a prompt asking you to update the su binary. Do so.
Grab Android Terminal Emulator on the Market, and run "su". If all went well, SuperSU should ask you for permission. Grant it and if the $ turned into a # and the command "id" says uid=0 (root) then you're rooted!
OK, Im really sorry and embarrassed to say that I got confused with my tab 10.1.
I Do not have CWM installed.
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
What can I do now?
Thanks again and sorry for the confusion..
tomerstern said:
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
Click to expand...
Click to collapse
Flashing CF-Root should always get you CWM as it's done through ODIN, which does not care if your phone is rooted or not. When you're flashing CF-Root, make sure the auto reboot option remains ticked. If your phone doesn't boot into CWM after ODIN reboots it, then take note of the following:
Chainfire said:
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
qwerty12 said:
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
Click to expand...
Click to collapse
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
tomerstern said:
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
Click to expand...
Click to collapse
Under the mounts and storage option, select mount /system. It will change to "unmount /system" if selected correctly.
The commands are run from an "adb shell" session, which you can get to by doing this:
Extract those three ADB files from that platform-tools ZIP to a folder somewhere (I chose C:\adb out of randomness). Open that folder and while holding down the shift key, right-click a blank, white area in the folder and select "Open command window here". You can then type "adb shell", which will allow you to run those commands.
qwerty12 said:
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
Click to expand...
Click to collapse
There isnt mount system there. I see unmount system.
I see mount data, preload etc.
OK, that's fine, you may move on to running those commands.
Two problems:
1. running "chattr -i /system/xbin/su"
resulted in a "chatter not found" message.
2. Trying to push the su zip resulted in this message: "error: device not found".
tomerstern said:
"chattr -i /system/xbin/su"
Click to expand...
Click to collapse
If rm worked on /system/xbin/su, then ignore it as you don't need it anyway.
2. Trying to push the su zip resulted in this message: "error: device not found".
Click to expand...
Click to collapse
Reconnect the phone and try again?
not working after numerous attempts.
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
tomerstern said:
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
Click to expand...
Click to collapse
That should be fine
moved it to internal memory and after shutdown, power+home+volume up wont take me to cwm anymore but to android system recovery.
Why? How do I get back to cwm? Install it again with Odin?
BY THE WAY, I can still see supersu is installed on my device. Does it mean what we did did not work?
OK, I can confirm this method works
I just installed the zip of the supersu and now Ive got full root privileges.
The reason I couldnt get into cwm was that for some reason I get a short android upgrade each time I boot up. This upgrade deletes cwm. Thats why I found out that I need to install CWM and then immidiately press power-volume up-home, before i let the device power up.
I want to give a big thanks to qwerty12 for the help and much needed patience.
Hi guys! My unit is from " SHW-M250S" which i converted to "i9100" and currently running on "ROOTBOX JB 3.0"
The problem is like this:
My "LOCK SCREEN" is not working EVERYTIME i flash a stock rom. (Lockscreen works with rootbox though)
I just cant understand what's causing this error.
I tried downloading other stock rom. So far I at least tried "TWO" stock roms the other one is pre-rooted.
Another problem when flashing stock rom and some other custom roms is:
My phone shuts down when press+hold the power button in just a matter of second instead of activating the power menu first before shutting down.
Please help.
Does anyone here having the same issue?
What can you suggest?
I appreciate your help.
In /efs/imei/ folder create a file named "keystr", then open it, type ON in it, save, reboot.
OR
in terminal emulator / adb type
echo -n ON > /efs/imei/keystr
Click to expand...
Click to collapse
You need to be rooted.
przemcio510 said:
In /efs/imei/ folder create a file named "keystr", then open it, type ON in it, save, reboot.
OR
in terminal emulator / adb type
You need to be rooted.
Click to expand...
Click to collapse
Will try it and will report back tomorrow. Thanks!
Edit: I checked my /efs/ime/ and looked for keystr but there was no such file in it. Currently running now on miui and lock screen is working as of now. But anyway hope that nothing bad will happen when I try it on stock ROM.
Edit:
It worked! Thanks!
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.