Hi!
I have installed the [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes, but I have no WiFi.
In a previous version was included by default Debugging tool which would allow a terminal to be launched in order to copy the wifi-nvram file from the SD card towards the /data folder.
How to get the Debugging Tool / Terminal in this version ?
Any help welcome !
Thanks,
JM
jsalsa said:
Hi!
I have installed the [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes, but I have no WiFi.
In a previous version was included by default Debugging tool which would allow a terminal to be launched in order to copy the wifi-nvram file from the SD card towards the /data folder.
How to get the Debugging Tool / Terminal in this version ?
Any help welcome !
Thanks,
JM
Click to expand...
Click to collapse
Unfortunately you can't. Use ConnectBot from the Market.
For the wifi-nvram.txt trick why don't you just use the user.conf file to bind mount it? That way you wouldn't ever have to do it again... Do it once, then never worry about it again...
Thanks !
For ConnectBot, this is a SSH client. how to connect locally: localhost I presume, But which login/password?
For user.conf file, I did not know its existence . have added the "cp /sdcard/wifi-nvram.txt /data/wifi-nvram.txt" at the end, let's see if this works at next reboot.
Thanks again !
jsalsa said:
Thanks !
For ConnectBot, this is a SSH client. how to connect locally: localhost I presume, But which login/password?
For user.conf file, I did not know its existence . have added the "cp /sdcard/wifi-nvram.txt /data/wifi-nvram.txt" at the end, let's see if this works at next reboot.
Thanks again !
Click to expand...
Click to collapse
ConnectBot works locally. Instead of SSH, choose "Local"...
Let me know if you need help with the user.conf command. Should work, haven't tried it myself...
Thanks once more.
the user.conf trick did the trick already.
Many thanks !
JMS
jsalsa said:
Thanks once more.
the user.conf trick did the trick already.
Many thanks !
JMS
Click to expand...
Click to collapse
np. Figured that is the easiest method for fixing this... now you can just leave the file on your SD card and user.conf will always mount it for you .
arrrghhh said:
ConnectBot works locally. Instead of SSH, choose "Local"...
Let me know if you need help with the user.conf command. Should work, haven't tried it myself...
Click to expand...
Click to collapse
can u tell me how does user.conf work ? what do i have to do ?
the show stopper said:
can u tell me how does user.conf work ? what do i have to do ?
Click to expand...
Click to collapse
Boot back to WinMo, edit the froyo.user.conf file (in the 'conf' folder on your SD card, where Android is...)
I like editing these files with Notepad++ but I think Wordpad will handle the enter keys correctly (regular Windows Notepad won't!)
At the bottom, you'll see a "CustomCommands" section. Within the braces ({}) add a line -
Code:
ln -s /sdcard/wifi-nvram.txt /data/wifi-nvram.txt
Make sure it's on its own line, look at some of the other commands for an example (look at the rm command...)
That's the skinny... hopefully it works! This assumes the wifi-nvram.txt file you created (with your MAC address in it) is at the root of the SD card (look at the command, /sdcard/wifi-nvram.txt... if it's in a 'mods' folder which is at the root of the SD, then the path would be /sdcard/mods/wifi-nvram.txt...)
? Purpose
arrrghhh said:
Boot back to WinMo, edit the froyo.user.conf file (in the 'conf' folder on your SD card, where Android is...)
I like editing these files with Notepad++ but I think Wordpad will handle the enter keys correctly (regular Windows Notepad won't!)
At the bottom, you'll see a "CustomCommands" section. Within the braces ({}) add a line -
Code:
ln -s /sdcard/wifi-nvram.txt /data/wifi-nvram.txt
Make sure it's on its own line, look at some of the other commands for an example (look at the rm command...)
That's the skinny... hopefully it works! This assumes the wifi-nvram.txt file you created (with your MAC address in it) is at the root of the SD card (look at the command, /sdcard/wifi-nvram.txt... if it's in a 'mods' folder which is at the root of the SD, then the path would be /sdcard/mods/wifi-nvram.txt...)
Click to expand...
Click to collapse
What is the result of moving this file what does this do,fix,solve? P.s. sincere?Not being sarcastic just curious.
Phatboyj420 said:
What is the result of moving this file what does this do,fix,solve? P.s. sincere?Not being sarcastic just curious.
Click to expand...
Click to collapse
What is this, I don't even...
If you're asking what this fixes, it's for wifi problems. I think someone tried this trick, and it didn't work. You actually have to place the .txt file instead of symlinking.
Related
I didn't see a thread for this anywhere and it's not included in the rooting documentation so i figured I'd make one.
This will allow you to install apk files directly from the device, no need to adb them over. Just get the apk from the web or whatever source you want and install. Of course this is all assuming you have completed the current root process and have adb access already.
Thanks to godsfilth for finding these directions for the origninal nook.
1. Open a command prompt and navigate to your sdk tools folder
2. Run the following commands
Code:
C:\android-sdk-windows\tools>adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
C:\android-sdk-windows\tools>sqlite3 settings.db
sqlite> update secure set value=1 where name='install_non_market_apps';
sqlite> .q
C:\android-sdk-windows\tools>adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
3. Reboot
4. Install apps from NC without ADB.
You might have to restart your homescreen for the apps to show up, but i've had sucess with every app i've tried that is known working on the NC.
This was done on a Windows 7 x64 machine, although i'm sure it's the same or similiar for Linux and MUC OSx.
Also, sqlite3.exe was already in my sdk tools folder, if it's not for you then you can download from here.
Yep, and you can ADB install a file manager app, then just use the file manager to install anything else, from the SD card.
Bimboy said:
Yep, and you can ADB install a file manager app, then just use the file manager to install anything else, from the SD card.
Click to expand...
Click to collapse
So...the nook doesn't stop apps from deing installed if Iinstall them manger astro file Manger?
What is the command in sqllite to see if the db entry has been changed?
I copied & pasted your commands and after a reboot still get "Can't install downloaded apk"
I did the same - even adapted the commands because the folder name wasn't the same, etc.
However, I'm trying to use SlideMe to install APKs and it keeps coming up with "Install Blocked" - any ideas?
sudermatt said:
So...the nook doesn't stop apps from deing installed if Iinstall them manger astro file Manger?
Click to expand...
Click to collapse
Once you enable this it will allow you to install the apps, it doesn't have anything to do with astro per se. You can just use astro to navigate to apks stored on your sd card. I use estrongs file manager myself and have installed apks from my sd card, dropbox and downloads from dolphin browser hd.
I'm getting the same error as everyone else.
I made the edits per your first post and pushed the file back to the NC. Then I rebooted. Placed an apk in the NC and tried to open it using Root Explorer. I try to install it and I get the "Installation of donwload apks is not supported" error.
barrosd12 said:
I did the same - even adapted the commands because the folder name wasn't the same, etc.
However, I'm trying to use SlideMe to install APKs and it keeps coming up with "Install Blocked" - any ideas?
Click to expand...
Click to collapse
Slideme works perfect for me so you did something wrong. Not sure what though, I would just redo it.
lovelacer said:
What is the command in sqllite to see if the db entry has been changed?
I copied & pasted your commands and after a reboot still get "Can't install downloaded apk"
Click to expand...
Click to collapse
just use
Code:
sqlite3 settings.db ".dump"
and then scroll down and look for INSERT INTO "secure" VALUES(4,'install_non_market_apps','1'); you want a 1 there at the end.
barrosd12 said:
I did the same - even adapted the commands because the folder name wasn't the same, etc.
However, I'm trying to use SlideMe to install APKs and it keeps coming up with "Install Blocked" - any ideas?
Click to expand...
Click to collapse
look in your tools folder for the settings.db file and check the modified by time and make sure the change you are making is made.
To clarify if there's a misunderstanding the path info and text before the > in the commands is just what you would see in your command prompt. the actual commands are after the >. These are the actual commands.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update secure set value=1 where name='install_non_market_apps';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
What command did you have to alter?
also, maybe try
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
to push... I didn't have any problem with the other command and both appear to work for me.
Oh none, your commands worked awesomely, I just had to yank the folder designations that were there, which you've now done for everyone, so thanks!
I think it might be a problem somewhere else, I'm re-doing everything right now, I'll let everyone know
Ran these commands again with the additional adb push and still no dice. I checked to see that the db entry had been updated and it correctly has the install non market apps set to 1. I'm using root explorer as well I'll try estrongs as you have. Thanks for the help.
lovelacer said:
Ran these commands again with the additional adb push and still no dice. I checked to see that the db entry had been updated and it correctly has the install non market apps set to 1. I'm using root explorer as well I'll try estrongs as you have. Thanks for the help.
Click to expand...
Click to collapse
Confirmed now that SlideMe is not the issue - the settings are all correct on the PC, I can't confirm these settings for the NC. I tried re-adb-pushing and still no cigar here either. I'm getting app rejections from any source, downloaded on the NC and the SD card. Any idea what could be wrong?
Ok, definitely isolated the problem now.
I pull the settings from the NC, modify them, and everything works great, then it refuses to push it back, but says it succeeds, or something to this effect, because whenever I pull the file back from the NC, it says value=0
barrosd12 said:
Confirmed now that SlideMe is not the issue - the settings are all correct on the PC, I can't confirm these settings for the NC. I tried re-adb-pushing and still no cigar here either. I'm getting app rejections from any source, downloaded on the NC and the SD card. Any idea what could be wrong?
Click to expand...
Click to collapse
Not sure, I've got it working using this method on 3 different NCs myself. The only thing i can think of is that i had already installed estrongs file manager and a few other games before doing it. Maybe try using adb to install estrongs or astro and see if it will let you then.
estrongs i'm using: www mediafire com ?sxw6adfzvyp250m
astro: www mediafire com ?05scsbrnx2wfw4v
Novaglarion said:
Not sure, I've got it working using this method on 3 different NCs myself. The only thing i can think of is that i had already installed estrongs file manager and a few other games before doing it. Maybe try using adb to install estrongs or astro and see if it will let you then.
estrongs i'm using: www mediafire com ?sxw6adfzvyp250m
astro: www mediafire com ?05scsbrnx2wfw4v
Click to expand...
Click to collapse
Thanks for the file links - I'll give them a try, I really think the problem though is that the NC keeps resetting the value I push back for the non-market apps. I have no idea why it's doing this...
barrosd12 said:
Thanks for the file links - I'll give them a try, I really think the problem though is that the NC keeps resetting the value I push back for the non-market apps. I have no idea why it's doing this...
Click to expand...
Click to collapse
try pulling it back right after pushing the modified one, before rebooting, and see if it's even pushing correctly at all. If it is then being reset on reboot i don't know what the issue is.
Novaglarion, I am not able to do it either.
When you say "reboot", is that the same as power off and on?
boret said:
Novaglarion, I am not able to do it either.
When you say "reboot", is that the same as power off and on?
Click to expand...
Click to collapse
yes, the same.
make sure you're pushing the modified db file to /data/data/com.android.providers.settings/databases not to /data/data/com.android.providers.settings
it needs to be in the databases folder so it overwrites the original
bular211 said:
make sure you're pushing the modified db file to /data/data/com.android.providers.settings/databases not to /data/data/com.android.providers.settings
it needs to be in the databases folder so it overwrites the original
Click to expand...
Click to collapse
DAMN YOU!!!! such a simple thing and i missed it! You are correct. I'll update the original commands. Thanks for the good catch there.
It is a wise idea to backup the /pds partition of your Atrix. It is /dev/block/mmcblk0p3. It holds very important information unique to the phone, like the wifi and bluetooth mac addresses. We still don't fully understand it, but it can resolve issues with the touchscreen not taking input properly. This has happened to a number of people, and now that everyone can have the unlock, I am sure people will do things that will cause the same problem.
Steps:
1. Pick your favorite method: adb, ssh, terminal emulator, etc
2. Become root if not already, REQUIRED
3. dd if=/dev/block/mmcblk0p3 of=/tmp/pds.img
4. Pick your favorite method to get the file off the phone: scp, sd card, etc
The file should be about 2mb. Keep it in a safe place.
edgan said:
It is a wise idea to backup the /pds partition of your Atrix. It is /dev/block/mmcblk0p3. It holds very important information unique to the phone. We still don't fully understand it, but it can resolve issues with the touchscreen not taking input properly. This has happened to a number of people, and now that everyone can have the unlock, I am sure people will do things that will cause the same problem.
Steps:
1. Pick your favorite method: adb, ssh, terminal emulator, etc
2. Become root if not already, REQUIRED
3. dd if=/dev/block/mmcblk0p3 of=/tmp/pds.img
4. Pick your favorite method to get the file off the phone: scp, sd card, etc
The file should be about 2mb. Keep it in a safe place.
Click to expand...
Click to collapse
Everyone can't have the Unlock... Bell is denied for now.
This is sweet though. Thanks for the tip.
Can Root Explorer be used to do this?
no pds is mounted but root exp sees an empty partition, btw would be possible to know which files exactly are in the directory?
me and others messed up this partition using tenfar's recovery, now we have problem with temp throttling, i guess (cpu reaches only 50% of max freq)
Once you go through steps 1 to 3, you can go to /tmp in root explorer and copy pds.img file to sdcard or wherever you want to copy the pds file
Uhhh, is this still possible to back up after unlocking and flashing the 2.3.4 build?
Sent from my MB860 using XDA App
neer2005 said:
Uhhh, is this still possible to back up after unlocking and I flashing the 2.3.4 build?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I don't see any reason why you wouldn't be able to.
Screwed up my PDS on my old Atrix. Made sure to immediately back mine up when I got a new one too lol
Backed up the pds file to my ext-sd card using adb shell and got a 2.00mb file. Is this right?
Thanks for the info!
yes
now share it
Thanks I just make a backup image... but how do you restore it?
dd if=/tmp/pds.img of=/dev/block/mmcblk0p3
edgan said:
It is a wise idea to backup the /pds partition of your Atrix. It is /dev/block/mmcblk0p3. It holds very important information unique to the phone. We still don't fully understand it, but it can resolve issues with the touchscreen not taking input properly. This has happened to a number of people, and now that everyone can have the unlock, I am sure people will do things that will cause the same problem.
Steps:
1. Pick your favorite method: adb, ssh, terminal emulator, etc
2. Become root if not already, REQUIRED
3. dd if=/dev/block/mmcblk0p3 of=/tmp/pds.img
4. Pick your favorite method to get the file off the phone: scp, sd card, etc
The file should be about 2mb. Keep it in a safe place.
Click to expand...
Click to collapse
i cant seem to find the file once i created it!
ok, seems simple enough, but stupid question... can someone explain the commands "dd=" and "of=".
I was able to see the file @ dev/block with winscp but how do I convert it to a .img file, etc.
Thanks for your help.
samcripp said:
i cant seem to find the file once i created it!
Click to expand...
Click to collapse
It's in /tmp.
I suggest people use this command:
*MicroSD Installed*
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
*No MicroSD Installed*
dd if=/dev/block/mmcblk0p3 of=/sdcard/pds.img
These commands will create the pds.img file in the root directory of your MicroSD or your Internal SD card respectively.
What is pdf partition?
I believe and if I am wrong I am sure someone will correct me but
dd = I'm not sure
if = input file
of = output file
dd essentially takes a disk and copies it.
Sent from my MB860 using Tapatalk
Not to sound newbish, but I am, I keep getting Cannot Open for Read: Permission Denied
Could someone assist? Thanks.
Realized:
SU is what I needed to type, methinks...will try.
Worked:
Yeah, once I put SU and got that done, it worked out.
_Dennis_ said:
I believe and if I am wrong I am sure someone will correct me but
dd = I'm not sure
if = input file
of = output file
dd essentially takes a disk and copies it.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
From Wikipedia: "dd is a common Unix program whose primary purpose is the low-level copying and conversion of raw data............. dd can also be used to copy regions of raw device files, e.g. backing up the boot sector of a hard disk, or to read fixed amounts of data from special files like /dev/zero or /dev/random.[4]"
So, I am a n00b on using adb (etc..) so I will explain the way I did it using adb.
1. Make sure you have adb.exe installed on your computer and connect the phone to the computer. (I got my adb.exe from the Gladroot script. Here is a link: http://goo.gl/jHiJc)
2. Open a command window
3. Browse to the directory where the adb.exe is and type the following (press enter after each line):
adb shell
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
Now, if you DON'T have a SDcard in your phone, take out the "-ext" from that last line.
The file (pds.img) should now be in either the internal sdcard or on your physical sdcard, as nexxusty described.
I hope that helps some as it took me a while to learn this.
Sorry if this is too noob for some, but I started from zero knowledge of this
garekinokami said:
Not to sound newbish, but I am, I keep getting Cannot Open for Read: Permission Denied
Could someone assist? Thanks.
Click to expand...
Click to collapse
Only thing I can think of is if you didn't give ADB superuser permission. You have to physically click allow on the phone after you type "su". Could that be it?
wirednix said:
Only thing I can think of is if you didn't give ADB superuser permission. You have to physically click allow on the phone after you type "su". Could that be it?
Click to expand...
Click to collapse
Lol Yes. 10 Char.
Aye I know what it IS....not what dd MEANS lol. Thank you for the guide.....I completed this in terminal emulator.
hi
im very new in the forum thats my first post
i tried to install an app that required a rebbot in my gt-i9300, i rebooted and i got an pop-up window said that factory mode has crashed.
i searched for days in the internet and i found this thread: http://forum.xda-developers.com/showthread.php?t=1762204&page=53
i did all but my galaxy says that its unable to chmod /efs/FactoryApp/factorymode: no such file or directory
then i realised that i have no efs directory and that i can download one from here http://forum.xda-developers.com/showthread.php?t=888193
so' my question is,
if i will flash it with odin, will the error will dissapear?
and if the answer is yes,
i understand that some people flash it because they have no imei and the phone dont recognize their sim card.
and my fear it can happen to me if ill flash it
some help please?
What app did you try installing?
slaphead20 said:
What app did you try installing?
Click to expand...
Click to collapse
the swapsd app.
but theres no matter what app i installed
i just want to know if i can install the efs directory without problems
so please help me everyone!
You have a backed up EFS on your phone ???
jje
JJEgan said:
You have a backed up EFS on your phone ???
jje
Click to expand...
Click to collapse
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
arimal199 said:
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
Click to expand...
Click to collapse
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
familyguy59 said:
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
Click to expand...
Click to collapse
wow
thanks man ill try it
arimal199 said:
wow
thanks man ill try it
Click to expand...
Click to collapse
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
arimal199 said:
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
Click to expand...
Click to collapse
Check out the links in my description. (Win8 help - ADB etc. etc. ...) that works with Windows Vista, 7 and 8. If you need the ADB binaries, in that same thread, you can donate a bit of money to me and I'll license you a program (Always with updated binaries) that installs ADB and fastboot to your system's root. With the click of a button
Lg
Edit: You can also download my universal Android tool kit and with the next update, all the Samsung Galaxy S III variants will be supported and you can easily backup/restore your /efs partition from there (With the Pro version, that is)
spocky12 said:
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
Click to expand...
Click to collapse
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
arimal199 said:
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
Click to expand...
Click to collapse
no i understood' i wasnt at factory mode at all!
all the time i had imei and call function , the only problem was that factory test has stopped.
so, i downloaded titanum backup pro and turned factory test app off.
now my galaxy went back to normal all works as well!
thanks for trying to help guys!
Hello
Some of application such as Sygic, Aptoid, Waze and others cannot access to sdcard unless I reboot.
When verffying with Root Explorere I have noticed that the default access to Sdcard is R/O. As soon as I change that to Read/Write every thing goes right.
The problem is R/O keeps come back and apps cannot run until I do modification again.
Anyone can help please as to fix permenantly this issue.
Thanks
samaliset said:
Hello
Some of application such as Sygic, Aptoid, Waze and others cannot access to sdcard unless I reboot.
When verffying with Root Explorere I have noticed that the default access to Sdcard is R/O. As soon as I change that to Read/Write every thing goes right.
The problem is R/O keeps come back and apps cannot run until I do modification again.
Anyone can help please as to fix permenantly this issue.
Thanks
Click to expand...
Click to collapse
There are two ways
1 the easy way is an app from playstore to do that at every boot
Are many can do this
2 the hard way is a script
You can paste it to init.d folder or script manager execute at every boot
Do you have gtab?
And sd card should not have sysrw option
Something wrong with install of rom
samaliset said:
When verffying with Root Explorere I have noticed that the default access to Sdcard is R/O. As soon as I change that to Read/Write every thing goes right.
The problem is R/O keeps come back and apps cannot run until I do modification again.
Click to expand...
Click to collapse
Peculiar problem. Will have to do some tests and look at some logs to find out the cause.
1. Can you create or delete files/dirs. on the SDcard, and do these changes persist after a reboot? Or do they vanish--like the changes never happened?
2. What's the output of this command right after a reboot?
Code:
$ [B]mount[/B]
rajeevvp said:
Peculiar problem. Will have to do some tests and look at some logs to find out the cause.
1. Can you create or delete files/dirs. on the SDcard, and do these changes persist after a reboot? Or do they vanish--like the changes never happened?
2. What's the output of this command right after a reboot?
Code:
$ [B]mount[/B]
Click to expand...
Click to collapse
Thanks for your reply,
1- I realy need some more details about this point. Some more explaination will be highly appreciated.
2- After typing this line and enter, the output is : /system/bin/sh:
Code:
$: not found. Moreover,after reboot, wh
ile launching Waze, I get the message : "Wazecan't access your sd card. Make sure it isn't mounted".
geowolf1000 said:
There are two ways
1 the easy way is an app from playstore to do that at every boot
Are many can do this
2 the hard way is a script
You can paste it to init.d folder or script manager execute at every boot
Do you have gtab?
And sd card should not have sysrw option
Something wrong with install of rom
Click to expand...
Click to collapse
Thanks fro your reply.
1- May know which app I should use.
2- Sure it looks hard for me to do that.
Yes I do have a Gtab 7.7 with JB.
The rest of the message needs more explaination if possible.
samaliset said:
Thanks fro your reply.
1- May know which app I should use.
2- Sure it looks hard for me to do that.
Yes I do have a Gtab 7.7 with JB.
The rest of the message needs more explaination if possible.
Click to expand...
Click to collapse
Sd card always alow read/write permission is not part of root
Type mount to terminal and post the result so rajeevvp give you his knowledge
samaliset said:
Yes I do have a Gtab 7.7 with JB.
Click to expand...
Click to collapse
There is no such device as a gTablet 7.7. Is this the tablet you have?
1. Use the standard file manager app and create or delete some files and directories on the SDcard. Reboot the gTablet. Verify that the changes you made remain after the reboot.
2. The $ character is just a prompt, used to indicate that the commands that follow can be executed by any user. Don't type that into the Terminal emulator app. Type in only the stuff shown in bold.
3. Setup adb (see the sticky threads) to make entering commands and collecting logs easier.
4. From now on post the exact error or diagnostic messages that you see. Or, make screenshots and post them.
I am very sorry to post my message here by mistzke.
Anyway I would like to thank all for your help and would like to inform you that the probme had been solved in installing a new tom.
Thanks znd sorry again
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.