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
Related
Hi everyone.
I apologize for my first post because it's not one helping, but one asking for help instead.
I have recently struggled with the problem of not being able to move apps to the SD card which you may already be aware of.
So I read somewhere about changing some things on /system/etc/permissions/platform.xml and I had the stupid idea to try to change it without really understanding it.
So I did some ****. Now I can't mount sd (internal or external) and I don't have permissions to restore platform.xml (I have a platform.xml.bak in the same directory which is identical to the original one).
So I was wondering if there could be any trick to restore it. Neither ES File Manager nor Terminal Emulator were capable of replacing the files or edit platform.xml's content (even with root access, su - with terminal emulator).
What could I do? I honestly don't think a factory reset would solve that.
My ROM is stock UBDLI2 (4.1.1) which I found kinda hard to find.
Since you haven't posted a log of your Android Terminal Emulator session, here's my guess at trying to resolve this:
Code:
su
mount -o remount,rw /system
mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
If you need it, chown root.root platform.xml && chmod 644 platform.xml.
similar problem with platform.xml
qwerty12 said:
Since you haven't posted a log of your Android Terminal Emulator session, here's my guess at trying to resolve this:
Code:
su
mount -o remount,rw /system
mv /system/etc/permissions/platform.xml.bak /system/etc/permissions/platform.xml
If you need it, chown root.root platform.xml && chmod 644 platform.xml.
Click to expand...
Click to collapse
I was trying to replace my platform.xml file with a modified platform.xml file and in doing so I moved the 0riginal platform.xml file to another folder (just in case I needed the 0riginal again), I changed the permissions of the permissions folder and rebooted for them to take affect without having the platform.xml file in there and boom I'm in never-never-bootloop land. Can anyone help me or does this phone need to be used for skeet shooting? Thanks in advance!
Reflash the same rom, no wipe.
boomboomer said:
Reflash the same rom, no wipe.
Click to expand...
Click to collapse
Thanks for the reply. I was rooted but still on stock since I had yet to successfully get a custom recovery on my phone (apparently SGH-I337 on the BN1 baseband is tough to get a custom recovery on)...so I only have the stock recovery which really doesn't offer many options. And everytime I have tried to flash anything via the custom recovery it fails due to it not being signed (or at least I think that is what it says). I'm open to try anything if you got more ideas.
Odin
Odin
boomboomer said:
Odin
Click to expand...
Click to collapse
I don't want to be "that guy" as described in your signature...so I want to first say I have searched on this, but I have only found various sections on Odin instructions for various versions of Odin typically pertaining to one specific topic rather than an actual manual/guide for how to use Odin to reinstall a file that was idiodically removed (that'd be me....the idiotical remover of pertinent files). So I hate ask you for more help, but I only can't seem to get anything I try flashing with odin to work, I'm not sure if I'm putting things in the wrong slot (BOOTLOADER, PDA, PHONE, CSC) or what, but I really need some guidance.
Go read the sticky thread in general forum, how to flash with Odin, you can only flash the whole firmware not one file.
I was trying to replace a file in /system/etc folder and it wouldn't let me paste one, so I changed the permissions to be able to paste a file, but what I did was remove the execute permission for /system , /system/etc , and /system/etc/paranoid.
Any way I can change them back somehow? I tried loading TWRP and opening terminal and typing "chmod 755 system" and "chmod 755 etc" and it went, but didn't help the phone boot.
I just can't boot and need help.
Edit: I fixed by reinstalling the ROM again without wiping.
Hi all
I have a problem with a clone (HDC model). That I did a factory reset and reformatted the storage. After that I suddenly don't have my bootanimation anymore. Instead it shows a silver grey "android" logo in the middle of the screen when I boot the phone, and the same when I shut it off.
I have checked my system/media folder and the phone actually have all the bootanimation.zip shutdownanimation.zip etc. in there, and they are also the original ones. But for some reason the phone don't use them by boot or shutdown.
Also I tried with "Boot Animations -root-" app from the Playstore, but it also don't change anything. I tried to place bootanimation.zip in data/local also but no change.
I checked the permissions of the files and they are also good. And tried all kind of codes on the phone, but none have worked so far.
So what the heck can be wrong?
s7yler said:
Hi all
I have a problem with a clone (HDC model). That I did a factory reset and reformatted the storage. After that I suddenly don't have my bootanimation anymore. Instead it shows a silver grey "android" logo in the middle of the screen when I boot the phone, and the same when I shut it off.
I have checked my system/media folder and the phone actually have all the bootanimation.zip shutdownanimation.zip etc. in there, and they are also the original ones. But for some reason the phone don't use them by boot or shutdown.
Also I tried with "Boot Animations -root-" app from the Playstore, but it also don't change anything. I tried to place bootanimation.zip in data/local also but no change.
I checked the permissions of the files and they are also good. And tried all kind of codes on the phone, but none have worked so far.
So what the heck can be wrong?
Click to expand...
Click to collapse
just delete bootanimation.zip
it will load the stock files if available
&
next time post in Q &A forum
Vaibhav Chauhan said:
just delete bootanimation.zip
it will load the stock files if available
&
next time post in Q &A forum
Click to expand...
Click to collapse
That don't help anything, I want it to display the bootanimation.zip in system/media (and currently it don't show that one at bootup!)
deleting it, just still shows the stock with android in silver at bootup.
It don't seem that you understand the problem.
s7yler said:
That don't help anything, I want it to display the bootanimation.zip in system/media (and currently it don't show that one at bootup!)
deleting it, just still shows the stock with android in silver at bootup.
It don't seem that you understand the problem.
Click to expand...
Click to collapse
i think the permissions for using custom animation is changed in your phone as you have reset the phone
Vaibhav Chauhan said:
i think the permissions for using custom animation is changed in your phone as you have reset the phone
Click to expand...
Click to collapse
Okay, but the phone is rooted and I have set the same permissions on the files.
Or how can it then be fixed? "permissions for using custom animation" where is that set?
s7yler said:
Okay, but the phone is rooted and I have set the same permissions on the files.
Or how can it then be fixed? "permissions for using custom animation" where is that set?
Click to expand...
Click to collapse
its not a name of permissions
please conform there is system/bin/bootanimation available
Vaibhav Chauhan said:
its not a name of permissions
please conform there is system/bin/bootanimation available
Click to expand...
Click to collapse
Yes it is there
s7yler said:
Yes it is there
Click to expand...
Click to collapse
try to flash the file in the thread
http://forum.xda-developers.com/showthread.php?t=2186155
&
replace the bootanimation.zip with yours
Vaibhav Chauhan said:
try to flash the file in the thread
http://forum.xda-developers.com/showthread.php?t=2186155
&
replace the bootanimation.zip with yours
Click to expand...
Click to collapse
Ok i flashed it with CWM, but now the bootup is just a blackscreen for 10 seconds.... tried to replace the bootanimation.zip with the original.
Still just a black screen at bootup. But at least it boots into the system still.
s7yler said:
Ok i flashed it with CWM, but now the bootup is just a blackscreen for 10 seconds.... tried to replace the bootanimation.zip with the original.
Still just a black screen at bootup. But at least it boots into the system still.
Click to expand...
Click to collapse
now replace your bootanimation.zip in system/media
Vaibhav Chauhan said:
now replace your bootanimation.zip in system/media
Click to expand...
Click to collapse
Already tried to replace it with the original bootanimation.zip, still just a black bootup. Also tried others that I download from Bootanimation app from the play store. Still just black, it is strange....
Ok I gave up fixing this manually, so I ended up restoring my whole phone from a previous CWM backup. So now I am back again and have the stock bootanimation. Never found out where or why it couldnt be fixed. But thanks for your time and answers.
s7yler said:
Ok I gave up fixing this manually, so I ended up restoring my whole phone from a previous CWM backup. So now I am back again and have the stock bootanimation. Never found out where or why it couldnt be fixed. But thanks for your time and answers.
Click to expand...
Click to collapse
:good:
Vaibhav Chauhan said:
just delete bootanimation.zip
it will load the stock files if available
&
next time post in Q &A forum
Click to expand...
Click to collapse
thanks, this worked for my problem, i didn't have any boot screen, and when I restarted or turned off my phone it didn't turn off... now it didn't show anything though but i just placed the files manually in there again, now it works again
Thanks!
Sorry for reviving this thread, I had the same issue and I managed to fix it, my steps:
1. you must change your /system folder to read-write mode, to do that you must execute the following command:
mount -o rw,remount /system
2. then, move your bootanimation.zip to, in my case, /system/media , it should be like: (if you execute ls -la command there)
dolphin-fvd-p1:/system/media # ls -la
total 94704
drwxr-xr-x 3 root root 4096 2019-05-02 16:35 .
drwxr-xr-x 17 root root 4096 1969-12-31 19:00 ..
drwxr-xr-x 6 root root 4096 2018-11-22 22:42 audio
-rw-r--r-- 1 root root 5588643 2018-11-22 22:42 bootanimation.bkp
-rw-rw---- 1 root root 572218 2019-05-02 16:35 bootanimation.zip
*Note about the read-write-execute the bootanimation.bkp has -rw-r--r-- and my customized bootanimation.zip has -rw-rw----
with that the android logo kept showing over and over...
Ok, enough talk, what I did was just to fix the permissions there, to do that execute the command:
chmod 644 bootanimation.zip
Do not forget to rollback the /system back to read-only mode, to do that execute the command:
mount -o ro,remount /system
I have with this answer I have helped someone that like me found this thread on google.
digoo said:
Sorry for reviving this thread, I had the same issue and I managed to fix it, my steps:
1. you must change your /system folder to read-write mode, to do that you must execute the following command:
mount -o rw,remount /system
2. then, move your bootanimation.zip to, in my case, /system/media , it should be like: (if you execute ls -la command there)
dolphin-fvd-p1:/system/media # ls -la
total 94704
drwxr-xr-x 3 root root 4096 2019-05-02 16:35 .
drwxr-xr-x 17 root root 4096 1969-12-31 19:00 ..
drwxr-xr-x 6 root root 4096 2018-11-22 22:42 audio
-rw-r--r-- 1 root root 5588643 2018-11-22 22:42 bootanimation.bkp
-rw-rw---- 1 root root 572218 2019-05-02 16:35 bootanimation.zip
*Note about the read-write-execute the bootanimation.bkp has -rw-r--r-- and my customized bootanimation.zip has -rw-rw----
with that the android logo kept showing over and over...
Ok, enough talk, what I did was just to fix the permissions there, to do that execute the command:
chmod 644 bootanimation.zip
Do not forget to rollback the /system back to read-only mode, to do that execute the command:
mount -o ro,remount /system
I have with this answer I have helped someone that like me found this thread on google.
Click to expand...
Click to collapse
So I'm having the same issue on my OnePlus 6T. I already have my bootanimation (flashable zip) in /system/media.
I ran the command "chmod 644 bootanimation.zip," which returned "chmod bootanimation.zip to 100644: read-only file system". I'm still getting the gray android word though.
(And thanks for reviving the thread )
clarkcant said:
So I'm having the same issue on my OnePlus 6T. I already have my bootanimation (flashable zip) in /system/media.
I ran the command "chmod 644 bootanimation.zip," which returned "chmod bootanimation.zip to 100644: read-only file system". I'm still getting the gray android word though.
(And thanks for reviving the thread )
Click to expand...
Click to collapse
If you're using Magisk then open it's settings and select "core only mode", reboot, then try again. Magisk has problems mounting the system properly when modules are enabled. Also, if your device is treble enabled, then your boot animation might be in /oem/media instead. My G6 play has one in /system/media and also /oem/media, but only the one in /oem gets used on my device. You might have something similar going on.
clarkcant said:
So I'm having the same issue on my OnePlus 6T. I already have my bootanimation (flashable zip) in /system/media.
I ran the command "chmod 644 bootanimation.zip," which returned "chmod bootanimation.zip to 100644: read-only file system". I'm still getting the gray android word though.
(And thanks for reviving the thread )
Click to expand...
Click to collapse
Look like you haven't done the very first step I have mentioned. if you are using adb and/or console you should get it by typing the mount command.
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.
Does anyone know how I can implement a custom ROM but have it urooted
I need an unrooted for work. I have tried rootcloak type applications but they don't do the trick. Plus, this is for work so, in order to comply with requirements I want to make sure phone is not rooted rather than just hiding root
Reason I want to use custom ROM is to get additional features such as dropdown menu on main page, remove unwanted app (malware) and have smallest footprint possible
wrong thread. post in q&a
Flash custom ROM.
Download Root explorer or any other root explorer app
Navigate to system.
delete
Code:
/system/app/Superuser.apk
Code:
/system/xbin/su
or
Code:
/system/bin/su
reboot the phone
That should do it.
karandpr said:
Flash custom ROM.
Download Root explorer or any other root explorer app
Navigate to system.
delete
Code:
/system/app/Superuser.apk
Code:
/system/xbin/su
or
Code:
/system/bin/su
reboot the phone
That should do it.
Click to expand...
Click to collapse
Thank you - will try and see how it goes
jean001luc said:
Thank you - will try and see how it goes
Click to expand...
Click to collapse
No good. Deleted system/bin/su and xbin/su but could not find system/apps/superuser
Rebooted device and still rooted
what ROM are you using ?
it could be
/system/app/superuser.apk
/system/app/Superuser.apk
/system/app/SuperSU.apk
/system/app/eu.chainfire.supersu.apk
/system/app/com.koushikdutta.superuser.apk
/system/app/com.noshufou.android.su.apk
in anycase ,you will need to reflash ROM or reflash superuser.
Technically the "Superuser" app is a front end for /system/bin/su...So you are unrooted, Just you need to remove that app..