Problem with Samsung Galaxy s2 GT-I1900
Hi all, I am facing big problem with galaxy s2 I tried all new jelly bean official roms and also try to fix it using (keystr ... ON) as mentioned in this forum and didn't get any result. So, if any one have this problem please, tell me what is the solution.
I did factory reset before and after. Also no result
What else do I need to do?
you have to deep clean your S2. I mean, FULL WIPE and ics or jb STOCK (ODEXED) firmware install via odin, without the PIT file (DON'T use PIT).
If that doesn't work, well, it's serious.
najija said:
Problem with Samsung Galaxy s2 GT-I1900
Hi all, I am facing big problem with galaxy s2 I tried all new jelly bean official roms and also try to fix it using (keystr ... ON) as mentioned in this forum and didn't get any result. So, if any one have this problem please, tell me what is the solution.
I did factory reset before and after. Also no result
What else do I need to do?
Click to expand...
Click to collapse
I have the same problem, nothing fix the problem
Did you find a solution?
Someone can help??
---------- Post added at 06:28 PM ---------- Previous post was at 06:07 PM ----------
Problem fixed!! give read write permissions for user/group/others to the keystr file.
the spanish rom has this bug.....
which rom are you trying to flash
Have a look here.
Thank You! problem solved.
xaurion said:
Thank You! problem solved.
Click to expand...
Click to collapse
Good for you! :thumbup:
Please add [SOLVED] to the title of ur post.
"To err is human, to forgive is divine"
Sent from my SGS II
!!! Important: Set permissions to r/w !!!
Hi,
many thanks for the helpful hints!
We had the same problem on some of our SGS2 (Provider: Tre/Italy). The keystr "ON" had been fixed, but the most important hint was to SET THE PERMISSIONS for the keystr, factorymode etc. files in the efs and/or factoryapp folders.
The "fix permissions" option in some custom recoverys did NOT solve this issue. You have to set them manually to R/W with linux commands in a terminal OR with a root explorer.
It seems to happen if you update a very old android GB version directly to 4.x.x.
Hope this helps some.
[SOLVED]lock screen and power option problem (SHW-M250s)
Honzze said:
Hi,
many thanks for the helpful hints!
We had the same problem on some of our SGS2 (Provider: Tre/Italy). The keystr "ON" had been fixed, but the most important hint was to SET THE PERMISSIONS for the keystr, factorymode etc. files in the efs and/or factoryapp folders.
The "fix permissions" option in some custom recoverys did NOT solve this issue. You have to set them manually to R/W with linux commands in a terminal OR with a root explorer.
It seems to happen if you update a very old android GB version directly to 4.x.x.
Hope this helps some.
Click to expand...
Click to collapse
Thanks to this forum and all the guys who are doing their best. thumzz upp !!
I solved this issue by using this guide on my SHW-M250s ...the reason it wasn't working was the issue of permissions actually.
Thanks
dwie said:
Have a look here.
Click to expand...
Click to collapse
Many many thanks to you for the link. And of course to to OP of the tutorial. I thought I can no longer see the lockscreen on my SGSII. :good:
problem solved
Herea my experience , tried everything, but nothing worked for me , then I found a s2 with working power menu and everything .. noted its firmware .. searched on net (link given below) and flashed everything(pit, tar file etc) in package .. everything is running as it should .. Sharing it coz I didnt find proper solution for me anywhere . (I flashed everything as this tutorial says)
http://www.trickytweaks.com/i9100xxlsj-4-1-2-galaxy-s2-i9100-jelly-bean-update-tutorial.html
Worked!
This procedure is very risky and unsafe, I accept suggestions of another permission level to apply. Do at your own risk.
In my case I used the terminal emulator and gave the following commands:
Code:
# Chmod 777 factorymode
Code:
# Chmod 777 FactoryApp
Code:
# Chmod 777 keystr
It worked very well for me, returned to work without me needed if you want to restart
Honzze said:
Hi,
many thanks for the helpful hints!
We had the same problem on some of our SGS2 (Provider: Tre/Italy). The keystr "ON" had been fixed, but the most important hint was to SET THE PERMISSIONS for the keystr, factorymode etc. files in the efs and/or factoryapp folders.
The "fix permissions" option in some custom recoverys did NOT solve this issue. You have to set them manually to R/W with linux commands in a terminal OR with a root explorer.
It seems to happen if you update a very old android GB version directly to 4.x.x.
Hope this helps some.
Click to expand...
Click to collapse
There's another method that doesn't require root.. pretty simple. There's a video on youtube about it. I can't post links since I'm a newbie.. but if you search on youtube for this "3wYU0fu6s6E" the video will show up in the results.. it was pretty easy, the guy explained to simply input a code in the dialer and the menu started showing up.
I'd post it here but I think since he made it public he should at least get the views.. I guarantee you, it will be worth your time.. no terminal or root required at all and it solves the problem.. you'll take longer watching the vid than actually doing the procedure..
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
Why?
init.d allows to run scripts at system startup (reboot) of Linux and Android devices. On the Sony Tablet S it is not supported on "stock" ROM. Therefore it is not possible to execute shell scripts at the boot process.
For what?
As mentioned above, primarily for startup scripts. It can be used for 'mounting ext.sdcard to int. sdcard' for example or it is also possible to integrate kernel modules or system tweaks boot time.
How?
This requires copying the files in the enclosed zip archive to the corresponding points and to change the permissions right. Firstyou must create the folder 'init.d' at '/system/etc'.
But now "Step-by-Step":
Requirements:
You need to use Root Explorer, adb or something else. I do not want to explain each step in detail. If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems.
Everything is done at your own risk.
Step-by-Step Instructions:
1. Create in '/system/etc' a 'init.d' folder
2. Change the access rights to '777'
3. Copy the file 'sysinit' into folder '/system/bin'
4. Change the access rights to '755'
5. Copy file 'install-recovery.sh' into folder / system / etc '
6. Change the access rights to '777'
7. Copy file 'run-parts' into folder '/system/xbin'
(If 'run-parts' already existing, you can skip Step 7 and 8. In my case it was already on the Tablet S)
8. Change the access rights to '777'
9. Copy file '99test file' into folder '/system/etc/init.d'
10. Change the access rights to '777'
Now finished .... it should work !
After next reboot take a look into the folder 'data/local/tmp'. You should find a file 'init.d_log_test.txt', created by the test script. If so, everything works fine and now you can put there your own scripts under 'init.d'. Now you can delete the test script or if you like adjust it for your own tests.
Have fun with the new 'init.d' support and apologize for my weak English !!
Special thanks to DooMLord for the idea and first implementation.
Source: http://forum.xda-developers.com/show....php?t=1431134
am I missing something here, or where is the zip-file?
the link doesn't work at the bottom.
Thanx for a nice "how-to"
Seems simple and straightforward enough
Sorry for that and thank you for the hint. I was 100% sure that I enclosed the zip ... but it looks like I am getting old. ;-)
Now you should find the zip on the end of first post.
Sorry - how do you gve the 777 file permissions?
SWFlyerUK said:
Sorry - how do you gve the 777 file permissions?
Click to expand...
Click to collapse
Via the chmod unix command, or if you are using root explorer just enable read/write/execute permissions for owner, group, and others. For 755 give owner all permissions and only read/execute to group and others.
Whoops, my device is in a bootloop lol
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
What does it mean? Did you set wrong file permissions and reboots system? On all files or only on one specific? Did you changed build.prob and downloaded system update for boot loop prevention before?
obicom said:
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
Click to expand...
Click to collapse
Doh! Thanks
SWFlyerUK said:
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
Click to expand...
Click to collapse
Not permissions fault. Mine didn't bootloop
obicom said:
Special thanks to DooMLord for the idea and first implementation.
Click to expand...
Click to collapse
yep, DooMLord's great work.
got finished autoinstall tool for init.d as I said to you on thursday.
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
obicom said:
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
Click to expand...
Click to collapse
hah not important, just good to see that there are some people who are working on making our devices better and better the more of us = more of cool tab stuff
auto-install up, try it, tested so far only on one device.
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Can't follow your comment ...
Nothing is wrong with the information regarding permissions.
I did exactly the same on my Tab and one hour ago via Teamviewer on a second one.
I am not responsible if you did something wrong. Specially if you did not follow my hint to do first all regarding "boot loop prevention"
If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems. Everything is done at your own risk.
Click to expand...
Click to collapse
SWFlyerUK said:
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Click to expand...
Click to collapse
I wrote in many threads about 'rescue-backdoor', why havent you made it?
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
That was the background regarding 'did you changed build.prob' and not as a reproach. I can not understand why someone try something out, without a backup or rescue strategy. Oh damn !!
-- Edit --
Rolled the build.prop increment value back
Click to expand...
Click to collapse
Does it mean now you have the original value or the lower value?
If first case , that was a fault.
SWFlyerUK said:
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
Click to expand...
Click to collapse
The key to 'rescue' is to leave modified build.prop. It fakes that you've got older firmware than zip (zip=device the same versions). Then you get in recovery, and got opportunity to reflash the same version!
Hello.
I had searched for answer for last two days. But nothing found, only answers for rooted phones.
The problem is, when I push power on/off button it locks, but when push it to unlock it doesn't show any slide lockscreen, pattern lock or smtn. + when I hold power button, it just shutdowns, without any airplane mode etc.
Hope, u'll help me.
P.s. The only answer for this is, I've to root phone again, change that one file and unroot it back to stock? If it's possible..
Sent from my GT-I9100 using XDA
officialKKM said:
Hello.
I had searched for answer for last two days. But nothing found, only answers for rooted phones.
The problem is, when I push power on/off button it locks, but when push it to unlock it doesn't show any slide lockscreen, pattern lock or smtn. + when I hold power button, it just shutdowns, without any airplane mode etc.
Hope, u'll help me.
P.s. The only answer for this is, I've to root phone again, change that one file and unroot it back to stock? If it's possible..
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
edit keystr file inside /efs/imei (if it's not there create it), then type ON inside it and reboot, that should do it
LegendK95 said:
edit keystr file inside /efs/imei (if it's not there create it), then type ON inside it and reboot, that should do it
Click to expand...
Click to collapse
As I said, I can't edit it cuz my phone isn't rooted(phone doesn't give access to Root Explorer.apk)
Sent from my GT-I9100 using XDA
That is the fix. You will have to root to do it. If you don't want to root, then you won't be able to fix it, and should flash back to a Gingerbread firmware.
Its going to need one a factory reset and two if that fails a re download of the firmware .
Probable that either flash was not 100% or firmware file not 100% .
You dont have any other choice staying in the non XDA dev world as you are restricted .
jje
same probs bro!!!
I have d same prob... I think i bcos for i choosed "phone efs clear" in odin during installing ICS. Pls help me from basic..
I tried to return to my official base rom.. but after installation passed, it gives many error while phone start up with red letters and goes to recovery screen.
Anybody knows the perfect solution.. Thn pls help me out..
Thanks..
dev_ks said:
I have d same prob... I think i bcos for i choosed "phone efs clear" in odin during installing ICS. Pls help me from basic..
I tried to return to my official base rom.. but after installation passed, it gives many error while phone start up with red letters and goes to recovery screen.
Anybody knows the perfect solution.. Thn pls help me out..
Thanks..
Click to expand...
Click to collapse
no lie, clearing your phone efs was probably the dumbest thing you could do. especially if you have no backup. in no instructions i have seen do they tell you to clear efs which contains all the phone's information (imei, mac address, etc).
if you don't have a backup of your efs folder, you're done. have to send it back to samsung
akusokuzan said:
no lie, clearing your phone efs was probably the dumbest thing you could do. especially if you have no backup. in no instructions i have seen do they tell you to clear efs which contains all the phone's information (imei, mac address, etc).
if you don't have a backup of your efs folder, you're done. have to send it back to samsung
Click to expand...
Click to collapse
But I'm not cleared any efs folder.. The problem started from unrooting my phone to Gingerbread 2.4.4(some time ago)
Sent from my GT-I9100 using XDA
officialKKM said:
But I'm not cleared any efs folder.. The problem started from unrooting my phone to Gingerbread 2.4.4(some time ago)
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
We know your thread has been hijacked by a poster who wiped efs and his keyboard .
I would .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery ( root and cwm kernel required )
Mounts and Storage
Format cache data system and sd card .this will wipe the lot .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware GB version only this will wipe root .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
jje
LegendK95 said:
edit keystr file inside /efs/imei (if it's not there create it), then type ON inside it and reboot, that should do it
Click to expand...
Click to collapse
I have the power button problem, have rooted, but:
- Sorry for asking, but how do I create this file mentioned above? I googled but answers are all leading to java or programming etc.
I thank so much anyone who can help.
PS: I did go to the folder in my Android, but the file is not there
mbernstein said:
I have the power button problem, have rooted, but:
- Sorry for asking, but how do I create this file mentioned above? I googled but answers are all leading to java or programming etc.
I thank so much anyone who can help.
PS: I did go to the folder in my Android, but the file is not there
Click to expand...
Click to collapse
http://www.google.com/search?q=/efs/imei/keystr+fix
ctomgee said:
http://www.google.com/search?q=/efs/imei/keystr+fix
Click to expand...
Click to collapse
Thanks!
To make it even easier for other people (from this post: http://forum.xda-developers.com/showpost.php?p=22103709&postcount=5):
Tools Needed:
1. Root Explorer
Steps:'
1. Using root explorer locate the /efs/imei/ folder. In that folder there should be a file called keystr. In my case the file was missing which is why the home-button, power button and the lock screen was missing and was causing my problems.
2. using root explorer create a new file called keystr
3. also in root explorer open the file keystr in text editor and type ON
6. make sure you save the file.
7. reboot.
mbernstein said:
Thanks!
To make it even easier for other people (from this post: http://forum.xda-developers.com/showpost.php?p=22103709&postcount=5):
Tools Needed:
1. Root Explorer
Steps:'
1. Using root explorer locate the /efs/imei/ folder. In that folder there should be a file called keystr. In my case the file was missing which is why the home-button, power button and the lock screen was missing and was causing my problems.
2. using root explorer create a new file called keystr
3. also in root explorer open the file keystr in text editor and type ON
6. make sure you save the file.
7. reboot.
Click to expand...
Click to collapse
Hello,
only need to type "on" without quote ?
Rahul-Bhutani said:
Hello,
only need to type "on" without quote ?
Click to expand...
Click to collapse
Yes, no quotes, just ON
Face unlock ~ PIN problem
Hello,
My problem is that I have face unlock which unlocks fine and everything is perfect, but if it fails to recognise me it takes me to enter a PIN. I can put in a PIN, in fact any PIN no matter how long or short it is. I have attempted to put in the PIN that I remember it was and am pretty sure it is the one I have set. Also this happened suddenly and I don't know why.
Things I have tried:
>Format cache & Dalvik
>Fix permissions
>Attempted to change it (Via settings)
>Edited the file "efs/imei/keystr" to "OFF" and "ON"
Things to consider when solving this problem?
>I do not want to deleteany of my data
>Says "Android is upgrading..." after every boot
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[SOLVED]
To do the following you must've this app already INSTALLED and CONFIGURED in your phone!
I have used an app called cerberus app, previously configured in my phone steps to this if it ever happened is:
1) login Cerberus app online
2) select "LOCK" from dropdown list and type in any number as PIN>"SEND COMMAND"
3) unlock phone and go to settings>security
4) screen lock> type in the code you have set before>"NONE"
5) back on Cerberus online select "UNLOCK" from dropdown>"SEND COMMAND"> repeat step 4 just incase
6) set up a different password
This helped for me!
solved
Root + terminal required:
ref: http://forum.xda-developers.com/showthread.php?t=1750146
On terminal emulator:
FIRST:
su
echo -n ON > /efs/imei/keystr
reboot
Click to expand...
Click to collapse
SECOND:
su
chmod 644 /efs/imei/keystr
Click to expand...
Click to collapse
Fix without root
officialKKM said:
Hello.
I had searched for answer for last two days. But nothing found, only answers for rooted phones.
The problem is, when I push power on/off button it locks, but when push it to unlock it doesn't show any slide lockscreen, pattern lock or smtn. + when I hold power button, it just shutdowns, without any airplane mode etc.
Hope, u'll help me.
P.s. The only answer for this is, I've to root phone again, change that one file and unroot it back to stock? If it's possible..
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
For lock sreen solution type tis *#87976633#
I've rooted my galaxy Pocket GT S5300.
SU app - Appears.
Install Titanium Backup - It's working.
Install Root Explorer - It's working.
Install Data Usage Defender - Data usage count working, App blocking (White list/Black list) is not working.
Install Droidwall -App blocking (White list/Black list) is not working.
Message appears from Droidwall when I tried to activate the rules:
"Exit Code: 11 - iptables: No
chain/target/match by that name"
Is that something wrong with blocking internet connection from apps?
What to do?
Many thanks
hi, you need iptables to run it. the attachment is all the network module and iptables. sorry this can not flash in recovery mode,but you have to manually copy the file inside following the file structure in the zip. galaxy pocket still dont have cwm recovery,so i can not create flashable zip for you. remember to set the permission to 777 for all the module and file.:fingers-crossed::fingers-crossed:
jamestts said:
hi, you need iptables to run it. the attachment is all the network module and iptables. sorry this can not flash in recovery mode,but you have to manually copy the file inside following the file structure in the zip. galaxy pocket still dont have cwm recovery,so i can not create flashable zip for you. remember to set the permission to 777 for all the module and file.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hi there.. I haven't try it yet but will soon, I will let you know how it goes then.
Thanks for the help
jamestts said:
hi, you need iptables to run it. the attachment is all the network module and iptables. sorry this can not flash in recovery mode,but you have to manually copy the file inside following the file structure in the zip. galaxy pocket still dont have cwm recovery,so i can not create flashable zip for you. remember to set the permission to 777 for all the module and file.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Nothing work.. still the same error message. But thanks anyway.
By the way I found something here: http://code.google.com/p/droidwall/wiki/FAQ I think it has something to do with the kernel.
doodlerdroid said:
Nothing work.. still the same error message. But thanks anyway.
By the way I found something here: http://code.google.com/p/droidwall/wiki/FAQ I think it has something to do with the kernel.
Click to expand...
Click to collapse
u can try internet firewall from play store.
Sent from my GT-I8150 using xda app-developers app
Try avast anti virus
Double as a call blocker too
As well as anti theft
Swyped on my blade
More details please.
jamestts said:
hi, you need iptables to run it. the attachment is all the network module and iptables. sorry this can not flash in recovery mode,but you have to manually copy the file inside following the file structure in the zip. galaxy pocket still dont have cwm recovery,so i can not create flashable zip for you. remember to set the permission to 777 for all the module and file.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hi jamestts. I have the same issue as the original poster (and many others from what I have seen around the net). Being new to android and quite 'paranoid' about doing things on my phone that I dont understand, can you maybe explain this in more detail? What does the files you linked actually do and how do you set the permission to 777 and what does it mean? Any help will be greatly appreciated.
Thanks
*I already rooted my phone (galaxy pocket).
hi,the iptables is from ubuntu. i just copied from the source and paste in phone using ROOT EXPLORER. and from the ROOT EXPLORER, u will see 'rw-r--r--' , thats the permission i'm talking about. set all the iptables file that u have paste to rwxrwxrwx(this is 777 permission,press the file that u wanna set permission until a menu came out and select permission. after that new column will appear again,do tick all the 9 box in middle,the bottom box just ignored it). this is how we set for permission.
and the most important is our device is only support until 1.18.4 busybox,thats why some of the user having problem with the iptables. our device still cant support higher busybox version 1.19 . i'm not a developer,but i like paying around with the droid.my iptables work,but some of the user claim that not working. remember try on ur own risk. but no big deal, u can flash back to default by using odin. fyi,this device cant flash using single file,if u download from samfrmware, u need to split it to parts and flash it. otherwise u get softbrick.
sorry about my english,hope u understand what i'm talking about. have a nice day.:laugh:
thirdchance said:
Hi jamestts. I have the same issue as the original poster (and many others from what I have seen around the net). Being new to android and quite 'paranoid' about doing things on my phone that I dont understand, can you maybe explain this in more detail? What does the files you linked actually do and how do you set the permission to 777 and what does it mean? Any help will be greatly appreciated.
Thanks
*I already rooted my phone (galaxy pocket).
Click to expand...
Click to collapse
jamestts said:
hi,the iptables is from ubuntu. i just copied from the source and paste in phone using ROOT EXPLORER. and from the ROOT EXPLORER, u will see 'rw-r--r--' , thats the permission i'm talking about. set all the iptables file that u have paste to rwxrwxrwx(this is 777 permission,press the file that u wanna set permission until a menu came out and select permission. after that new column will appear again,do tick all the 9 box in middle,the bottom box just ignored it). this is how we set for permission.
and the most important is our device is only support until 1.18.4 busybox,thats why some of the user having problem with the iptables. our device still cant support higher busybox version 1.19 . i'm not a developer,but i like paying around with the droid.my iptables work,but some of the user claim that not working. remember try on ur own risk. but no big deal, u can flash back to default by using odin. fyi,this device cant flash using single file,if u download from samfrmware, u need to split it to parts and flash it. otherwise u get softbrick.
sorry about my english,hope u understand what i'm talking about. have a nice day.:laugh:
Click to expand...
Click to collapse
Thank you for the info, I think I understand all that you said. I have not had time to try this yet, but will try to in the next day or two.
3G Network Connection After Rooting
thirdchance said:
Thank you for the info, I think I understand all that you said. I have not had time to try this yet, but will try to in the next day or two.
Click to expand...
Click to collapse
I rooted my Galaxy Pocket and Installed the new Mak-Droid ROM, it is definitely faster now but I have a big problem with setting the type of mobile network to connect to... Before rooting, Settings had an option to choose: Automatic WCDMA/GPRS, WCDMA Only and GPRS Only in Network Connections. Now, These choices were replaced with "Use Only 2G Networks".... I need to set the phone to connect to WCDMA Only. How can this be done?
---------- Post added at 05:36 PM ---------- Previous post was at 05:24 PM ----------
jamestts said:
hi, you need iptables to run it. the attachment is all the network module and iptables. sorry this can not flash in recovery mode,but you have to manually copy the file inside following the file structure in the zip. galaxy pocket still dont have cwm recovery,so i can not create flashable zip for you. remember to set the permission to 777 for all the module and file.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
What are the iptables for? Is it necessary?
jamestts said:
hi, you need iptables to run it. the attachment is all the network module and iptables. sorry this can not flash in recovery mode,but you have to manually copy the file inside following the file structure in the zip. galaxy pocket still dont have cwm recovery,so i can not create flashable zip for you. remember to set the permission to 777 for all the module and file.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
doesn't work
---------- Post added at 10:11 AM ---------- Previous post was at 09:16 AM ----------
flashing that kernel work for me
http://forum.xda-developers.com/showthread.php?t=1971119
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
pavitar said:
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
Click to expand...
Click to collapse
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
ricky310711 said:
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
Click to expand...
Click to collapse
Can you please tell me, how to apply a file permission? I tried checking the box which is not checked in the snapshot shared, but that too gives an error.Says "Operation failed"
pavitar said:
Can you please tell me, how to apply a file permission?
Click to expand...
Click to collapse
download mobile terminal from playstore
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
pavitar said:
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
Click to expand...
Click to collapse
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
iamareebjamal said:
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Click to expand...
Click to collapse
pavitar said:
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
Click to expand...
Click to collapse
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
iamareebjamal said:
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
Click to expand...
Click to collapse
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
pavitar said:
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
Click to expand...
Click to collapse
Try this
https://play.google.com/store/apps/...&utm_medium=organic&utm_term=universal+init.d