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
Related
I hope, this is developent-related enough...
Some people don't switch from paul's MiniCM7Pro v21 to nobodyAtall's MiniCM7, because they don't want to Backup/Restore Apps, SMS a.s.o. only to make Wifi work.
After some testing arround, I found out that it's because of the file /data/misc/wifi/wpa_supplicant.conf
The wifi module in paul's ROM is handled different to that in nAa's, so you need a new version of this file.
After posting my results in nAa's thread Carpe-Dimi told me, that this file will be regenerated on boot, if it's missing.
So you only need to delete/move/rename the file, like I described here.
Summarized:
a)
- start an adb shell (there are enough tutorials in this forum, expaining this)
- type "mv /data/misc/wifi/wpa_supplicant.conf /sdcard/wpa_supplicant.conf" (without the ")
- reboot
Click to expand...
Click to collapse
You will notice, that there is the file "wpa_supplicant.conf" on your sdcard. If you saved some hotspots in the "old" ROM, there will be saved your SSIDs and passwords.
b)
If you don't really like adb shell, you can also use any Root Explorer:
- navigate to /data/misc/wifi/
- delete/move/rename wpa_supplicant.conf (you are a free human being, do what you want to)
- reboot
Click to expand...
Click to collapse
Enjoy your wifi!^^
Some people already confirmed that it worked for them.
Just trying to help.
Greez E4est
I recommend on doing this only if wifi doesn't work for you. If it connects and a.s.o. there's no need for this.
MiniPro Of Nobado is bug No full touch (don't touch edge of the screen)
h_pro9x said:
MiniPro Of Nobado is bug No full touch (don't touch edge of the screen)
Click to expand...
Click to collapse
it is not if you install these files (set permissions before copying!) --> http://forum.xda-developers.com/showpost.php?p=21288425&postcount=363
E4est said:
Summarized:
- start an adb shell (there are enough tutorials in this forum, expaining this)
- type "mv /data/misc/wifi/wpa_supplicant.conf /sdcard/wpa_supplicant.conf" (without the ")
- reboot
Enjoy your wifi!^^
Just trying to help.
Greez E4est
Click to expand...
Click to collapse
I assume Root Explorer would accomplish the same thing?
scook94 said:
I assume Root Explorer would accomplish the same thing?
Click to expand...
Click to collapse
I didn't even think of this option, because I don't like Root Explorer, but it should work the same. Will add this information in first post.
What will it do if i delete that conf file? Will there be an improvement or connection will be better? please add that in your first post.
It will be better to know that
Thank you!
Tim
Tommylee567 said:
What will it do if i delete that conf file? Will there be an improvement or connection will be better? please add that in your first post.
It will be better to know that
Thank you!
Tim
Click to expand...
Click to collapse
This conf file just contain all data information about wifi (access point, WEP key etc.).
Heh? Can you approve that method?
I don't believe this helps because I thought I did this and it did not work.
@tommylee: It will erase your configured hotspots you have to reconfigure them. alternatively you can read the configfile and reconfigure some spots...
Snoopo said:
Heh? Can you approve that method?
I don't believe this helps because I thought I did this and it did not work.
@tommylee: It will erase your configured hotspots you have to reconfigure them. alternatively you can read the configfile and reconfigure some spots...
Click to expand...
Click to collapse
I already tried this method and it worked for me. ^^
Tommylee567 said:
What will it do if i delete that conf file? Will there be an improvement or connection will be better? please add that in your first post.
It will be better to know that
Thank you!
Tim
Click to expand...
Click to collapse
I added, that I recommend on doing this only if wifi doesn't work.
Before deleting it's possible that the file is incompatible with your ROM. The file will be regenerated after reboot so you will have a new wpa_supplicant.conf that's compatible with your ROM.
Wifi device in paul's ROM is called wlan0 and in nAa's ROM it's tiwlan0, that's one reason why it's incompatible.
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!
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
I have another question, sorry but I don't want to make another thread.
SuperSU has an option "Survival Mode" that says that we must disable it before Nandroid Backup, what happends if I forgot to disable it ?
Thanks for your help, sorry if it was already asked (search results didn't help me).
For the installation paths, i dont really think it matters whether you put it in either of the above.
About survival mode, again i say it does not really matter whether you disable it or not. Your nandroid backup will go smooth.
Some developer can explain it to you in detail if any of the above really matters.
Sent from my LG-E730 using Tapatalk 2
Ok, thanks.
If anyone has more infos your welcome.
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
qwerty12 said:
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
Click to expand...
Click to collapse
Neither in htc wildfire nor in lg optimus sol disabling the survival is important. I have flashed and restored a hundred times but nothing happened..
Sent from my LG-E730 using Tapatalk 2
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
CNK80Q3MX said:
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
Click to expand...
Click to collapse
I am having the same question.. I have viewed each of the 4 directories using a root file explorer and noticed /bin /xbin and su/bin su/xbin all contain ifferent files so im not sure if doing that helped me o confused me more. Lol but im not sure it matters ,well im sure it makes differences but I cant find a difference other than some symlinks may be rewritten and handled by busybox instead of androids tool box.... Once again that means nothing to me without knowing what exactly androids tool.box is... I know a couple tool boxes but unfortunantly this is not one, ... So if anyone has a link to explain this or an educated opinion that would be great! Thanks..
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Shagerty said:
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Click to expand...
Click to collapse
UPDATING: I'm wondering that being MM, Busybox installer chooses su/bin path automatically (some suggest "su/xbin", which is not present in stock MM, hence installer su/bin choice) in order to make Busybox "systemless". SuperSu actually does the same. Though I'm pretty sure about this, I'm also looking for confirmation. Since this thread and its early answers even date back to 2012 when there was no MM and "systemless" stuff wasn't that popular (I assume) they point to install Busybox in "system/xbin" or "system/bin"...
babylonbwoy said:
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
Click to expand...
Click to collapse
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Mainak007 said:
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Click to expand...
Click to collapse
I think it's a little bit too late, thread is from 2012.
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
babylonbwoy said:
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
Click to expand...
Click to collapse
Why??.......do you frightened of bricking device??????
You can get all smartphone firmware Here
:highfive::fingers-crossed:
babylonbwoy said:
I think it's a little bit too late, thread is from 2012.
Click to expand...
Click to collapse
And I gave the answer for other who will visit the forum next time:angel:
Mainak007 said:
And I gave the answer for other who will visit the forum next time:angel:
Click to expand...
Click to collapse
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Doesn't matter..... Install anywhere and symlink to others
Mainak007 said:
Doesn't matter..... Install anywhere and symlink to others
Click to expand...
Click to collapse
Just install it to any folder in $PATH and execute it as any other command.
Code:
echo $PATH
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Banking / payment apps are looking in 3 mentioned paths to detect whether Android got rooted or not: hence best is to install BB to custom path.
BusyBox Pro says that it can is unsuccessful at installing in the /system/xbin folder on my Moto G Stylus 5G, I don't suppose anyone could explain to me why this keeps happening could they? Also, I don't have the option to install to /system/sbin either. The only options I have are /system/xbin, /system/bin, and custom. But when I install and reboot i have to reinstall BusyBox Pro again. I noticed in the settings tab that you can have busybox, on every boot, reinstall to /sbin....how is this possible if you install to /bin? also, how can I get it to install to /xbin? there is also another option that says busybox will, on every boot, be removed from /sbin as long as busybox has been installed to /bin or /xbin, but the feature I'm speaking of assists kernels that re-install busy box to /sbin on every boot.....OMG!!! Which option do I choose? Or should I not choose any, and just reinstall each time i boot up, which will be very tedious.....Please HELP!!!..... Also, should I choose Smart Install? Or just use install without the Smart Install option ticked? Sorry I see there are similar posts here, but I don't really understand where I would install if i chose to install to a custom path, which is why I'm asking such questions if it seems repetitive I apologize. Thanks in advance!
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
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Vaibhav Chauhan said:
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
Click to expand...
Click to collapse
can i use another rom's updater script in my rom which has same base??
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
es0tericcha0s said:
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
Click to expand...
Click to collapse
i tried to replace updater script but not working
i also have tried to compare set perms but i am unable to find fault in it
@es0tericcha0s
please tell me what to do??
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
es0tericcha0s said:
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
Click to expand...
Click to collapse
actually i am using android kitchen to make the rom
and when i use the cosmic rom's updater script in it the status 1 error was solved
but it stuck on boot animation
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Vaibhav Chauhan said:
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Click to expand...
Click to collapse
Not all phones have adb access while in a bootloop. But to do so you would need adb set up on your computer, change directories to the adb folder (or if it's enabled globally, then where ever), and type:
adb logcat
You'll want to save it somewhere like:
http://pastebin.com/
and upload the link.
I am not skilled at reading logcats, so not sure if I can be of any more help after that.
If you don't have adb set up already, then just use this one: http://forum.xda-developers.com/showthread.php?t=2317790