[Q] Can't access ReLunch settings and TestCenterService - Nook Touch General

Hi! I don't know how it happened, I was customizing the screen buttons behaviour in ReLaunch settings and was very careful doing it. And it worked fine. But now I can't access ReLaunch settings menu when I tap on it, the screen flashes and goes back to previous screen(Relaunch file manager). The same thing happens when I tap on TestCenterService app; It was working fine before; don't know how to fix this; if someone could help please?

Use ADB and do a logcat.
That will tell you what is screwed up.

ReLaunch Settings menu disabled
Dexnet said:
... I can't access ReLaunch settings menu when I tap on it, the screen flashes and goes back to previous screen(Relaunch file manager). The same thing happens when I tap on TestCenterService app; It was working fine before...
Click to expand...
Click to collapse
Hi, I have the very same problem as mentioned: "Can't access ReLunch settings and TestCenterService". I tried a couple of things to fix it: e.g. I reinstalled ReLaunch v.1.3.8 and Nook Touch Mod Manager v.0.4.0 , I reset the button's functions to default, nothing helped...
Following Renate's advice, I used ADB and did a logcat. Unfortunately, I have no idea what is the reason. I would appreciate it very much to get some more help to understand what could happen and how to cure ReLaunch of my nook Simple Touch.... I attached the created logcat, and its alphabetically ordered version, too (logcat.7z).
Best regards, Balint.
(Budapest, Hungary)

Sorry, I don't see any unhandled intents or exceptions in your logcat.
It seems to mean that the problem is completely internal to the application.
I have no experience with this application.

ReLaunch Settings missing
Renate NST said:
Sorry, I don't see any unhandled intents or exceptions in your logcat.
It seems to mean that the problem is completely internal to the application.
I have no experience with this application.
Click to expand...
Click to collapse
Thank you very much for answernig so quick.
One more info, that yesterday I installed ADW.Launcher, and it has a Settings menu icon (I was happy).
However it neither works! Instead it returns a message, that no Settings apk is available in this device...
Have a nice week, best regards, Balint

bjuh said:
no Settings apk is available in this device...
Click to expand...
Click to collapse
Oh, well that is simple enough.
Do you see the Settings icon in the "application drawer"?
Does it do anything?
Can you ADB shell in and see:
Code:
# ls -l /system/app/Set*
-rw-rw-rw- root root 2084682 2012-12-22 13:04 Settings.apk
-rw-rw-rw- root root 39973 2012-12-22 13:04 SettingsProvider.apk
(Your dates, sizes and permissions could be different but you should see both.)

still nook settings...
Hi,
thank you again for your message.
I am still needed a little more help.
In the "application drawer" I do not have a Settings icon, instead on the ADW Config palette there is one. If I tap on it, it returns:
"Application is not installed on your phone"
All the files in my app dir have same rights like these:
-rw-r--r-- root root 1620660 2008-08-01 14:00 Settings.apk
-rw-r--r-- root root 34031 2008-08-01 14:00 SettingsProvider.apk
I tried to change, however I couldn't:
# pwd
/system/app
# chmod 666 Settings.apk
chmod 666 Settings.apk
Unable to chmod Settings.apk: Read-only file system
# cd ..
cd ..
# pwd
pwd
/system
# ls -l
ls -l
drwxr-xr-x root root 2000-01-01 05:39 lost+found
drwxr-xr-x root root 2000-01-01 05:39 etc
-rw-r--r-- root root 1248494 2008-08-01 14:00 recovery-from-boot.p
drwxr-xr-x root root 2014-07-04 00:44 app
drwxr-xr-x root root 2000-01-01 05:39 assets
drwxr-xr-x root shell 2014-07-04 00:25 bin
-rw-r--r-- root root 2279 2014-07-04 00:44 build.prop
...
(You might see, I am not a Lx expert, although I have some practice in C, LabVIEW, etc.)
Best regards, Balint

/system is normally mounted read-only
To modify anything you will have to remount it.
ADW "Settings" button does this:
Code:
I/ActivityManager( 1055): Starting activity: Intent { act=android.settings.SETTINGS flg=0x10200000 c
mp=com.android.settings/.Settings }
If you can't see Settings in the drawer then something is screwed up.
You should run a logcat and see what exactly the error is.
You can also try:
Code:
C:\>adb shell am start -n com.android.settings/.Settings

Nook settings
Renate NST said:
/system is normally mounted read-only
To modify anything you will have to remount it.
ADW "Settings" button does this:
Code:
I/ActivityManager( 1055): Starting activity: Intent { act=android.settings.SETTINGS flg=0x10200000 c
mp=com.android.settings/.Settings }
If you can't see Settings in the drawer then something is screwed up.
You should run a logcat and see what exactly the error is.
You can also try:
Code:
C:\>adb shell am start -n com.android.settings/.Settings
Click to expand...
Click to collapse
Dear Renate, thanks for all your help. Finally, I gave up fixing my Nook's system.
I re-installed my backed up system then rerouted it. Now everything works again normally.
Best regards, Balint (from Budapest, Hungary)

bjuh said:
Dear Renate, thanks for all your help. Finally, I gave up fixing my Nook's system.
I re-installed my backed up system then rerouted it. Now everything works again normally.
Best regards, Balint (from Budapest, Hungary)
Click to expand...
Click to collapse
I wonder what actually happened.

Related

Velocity Cruz Tablet modding

The cruz tablet has android 2.0, no market pre-installed. I'm attempting to load the market on to it by tracking down .apk files for the market (vending.apk?) I havent had any success with adb installing it. I can use adp for just about every thing else it seems. I'm very new at this thus far. Any suggestions?
Whenever i run adp install vending.apk i get an error failure [install_failed_older_sdk] any idea what this means? maybe the vending.psk is intended for newer versions of android? I've tried another vending.psk (supposidly for pre-froyo items and it gave me the error missing libraries)
Thoughts? Ideas? Thanks
your doing it wrong, first you have to have root, next you need to flash a gapps update. If you can't flash you can unzip the update and push the files to their right system directory using adb.
Sent from my HTC Vision using XDA App
my device is rooted, but I'm having a hard time finding the zip file on step 2 there, i have build eclair 2.0-r1.1
Interestingly enogh i still cant delete files or uninstall much, is this something related to CHMOD or similar?
(on second thought I access shell (#) through adb and i can delete at will. I'm learning quickly but still can't figure out the steps to throw the market on this thing. If anyone can help me with more of a step by step or point me somewhere, i would really like to add to the lackluster modding community for the cheap velocity
If i can just somehow package the marketplace in to a rom for this thing (i used to do roms for windows mobile) I think the device interest will grow
I actually made a bunch of progress the other night, ill share my progress tomorrow in detail but it went something like this:
boot with power and volume - (down)
then you can chmod the /etc/permissions. ( and other dies) - from what I could tell this was only way to change system partition to writable?
then you can copy xmls, jar, and install all. the apk's with adb
that's as far as I got, market would run, but never got any pages to show up or was able to login (if that was a feature in 2.0) I would be more interested in an upgrade to 2.1? (if that's even possible?)
Which market APK did you use?
I think? for a 2.1 we would have to take the source 2.1 and go from there, I have no clue how to do that or where to start but I would like to take a shot.
Ideas?
I am actually quite happy with what I have right now, I picked it up for 170 at best buy and have most of the apps I want (with the exception of angry birds ) The tablet has seemed to speed up as time has gone on and 2.1 would be great!
From the get go with this tablet you can adb shell and you get the # meaning rooted.
I used the Market APKs from some phone ROMs AOSP 2.4 release that I found on communityforum.com
Here are the steps (from my notes) that I used. Note the FAILED, but could be a good starting point for you: Keep in mind this is from my first 8 hours of trying to learn Android, my first ADB session, etc, I am NOT an expert at this, just dangerous given all the other information others have shared, most of this comes from other device/forums for people trying to install the android market. Got my starting point from a post that stated that to install Android Market you had to:
Install:
1) GoogleApps.apk
2) SetupWizard.apk
3) TalkProvider.apk
4) Vending.apk
5) GoogleCheckin.apk
6) gtalkservice.apk
and copy and locations below:
/system/etc/permissions/com.google.android.datamessaging.xml
/system/etc/permissions/com.google.android.gtalkservice.xml
/system/framework/com.google.android.gtalkservice.jar
/system/lib/libgtalk_jni.so
------------------------------------------------------------------
HERE IS AS FAR AS I GOT:
------------------------------------------------------------------
Power up and Vol - (together - not sure if this was necessary but for some reason I couldn't ADB SHELL in and make modifications originally - although it might have been a skill thing on my part)
ADB REMOUNT
ADB SHELL
CD /SYSTEM/ETC
ls -l shows: drwxr-xr-x root root 2010-12-15 15:40 permissions
chmod 775 permissions
ls -l shows: drwxrwxr-x root root 2010-12-15 15:40 permissions
exit
exit
adb push com.google.android.datamessaging.xml /system/etc/permissions
0 KB/s (829 bytes in 1.000s)
adb push com.google.android.gtalkservice.xml /system/etc/permissions
52 KB/s (832 bytes in 0.015s)
ADB SHELL
CD /system/etc/permissions
ls -l
-rw-r--r-- root root 1139 2010-11-05 15:38 required_hardware.xml
-rw-r--r-- root root 8188 2010-11-05 15:38 platform.xml
-rw-rw-rw- root root 829 2011-01-10 23:20 com.google.android.datamessaging.xml
-rw-rw-rw- root root 832 2011-01-10 23:20 com.google.android.gtalkservice.xml
cd ..
chmod 755 permissions
ls -l
drwxr-xr-x root root 2011-01-11 01:43 permissions
cd ..
ls -l
drwxr-xr-x root root 2010-12-15 15:41 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxr-xr-x root root 2010-12-15 15:40 framework
chmod 775 framework
chmod 775 lib
drwxrwxr-x root root 2010-12-15 15:41 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxrwxr-x root root 2010-12-15 15:40 framework
exit
adb push com.google.android.gtalkservice.jar /system/framework
1698 KB/s (27139 bytes in 0.015s)
adb push libgtalk_jni.so /system/lib
29 KB/s (9460 bytes in 0.312s)
ADB SHELL
cd /system/
chmod 755 lib
chmod 755 framework
drwxr-xr-x root root 2011-01-11 01:47 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxr-xr-x root root 2011-01-11 01:47 framework
exit
ADB INSTALL
SetupWizard.apk
GoogleApps.apk
TalkProvider.apk
REBOOT
vending.apk
gtalkservice.apk
GoogleCheckin.apk
GmailProvider.apk
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb install Gmail.apk
2472 KB/s (710975 bytes in 0.280s)
pkg: /data/local/tmp/Gmail.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
GoogleContactsSyncAdapter.apk (success)
GooglePartnerSetup.apk
GoogleSettingsProvider.apk
At some point during the APK install and a device reboot the devices comes to complete crap and you need to use the VelocityMicro.com Cruz firmware update.zip to 'restore' the device to it's original state - so I would suggest being careful with what I've done above because your likely to make your device extremely unstable. My GUESS is it's somewhere after the first three APK installs and the reboot (after the first reboot it comes back fine, all steps after that cause failure, reboot, GUI starts acting all funky, can't swipe to login, etc and it's done)
If I get a chance, I'll try to play with it some more tonight.
The Attached SUCCESS.ZIP contains the files from the AOSP2.4 download I used to get this far...
I cant seem to get mine in to the pre-boot enviornment
Anywho i did everything with the device on and completed. It seems stuck in a reboot loop, probably from the setup wizard i'm assuming? Have you tried not installing as many apk's? Maybe something is trying to run and causing it. Can it be done without the wizard?
I've created some scripts that install good apps that work well with the tablet thus far and a script that will auto-uninstall bloat shortcuts and programs that it ships with
If you take the update.zip from the velocitymicro.com website firmware update for the cruz, and load it (power and Vol +) it'll recover the system (can't say i didn't warn you!
It's something AFTER this step that screws it up.
ADB INSTALL
SetupWizard.apk
GoogleApps.apk
TalkProvider.apk
REBOOT
I found this today and am going to dig into it a bit more to play with it, to see if it leads somewhere:
http://www.slatedroid.com/velocity-...-vm-cruz-(testers-needed!)/msg63584/#msg63584
and this:
http://www.slatedroid.com/pandigita...ment/easy-market-hack-for-bpdn-e-reader-help/
might lead to something?
tried item at first link. the batch corrupted the rom and i had to run the update.zip again
yes i did have adb installed and set up. I've been trying something similar to this for a while, just the manual way
I was able to get some apps installed via the handango.com market. Select the T-mobile G1 and you can download/install gmail, google reader, gdocs, google apps, maps, etc but as of now none of them work.
discovered 'adb bugreport' which seems to show issues with installed app. just did a clean reinstall of update.zip and am going to start from scratch one app at a time to see if i can make any headway there instead of blindly installing a bunch of crap and hoping that it works.
when i enter
>adb shell
I keep getting "access denied"
any ideas what I may be doing wrong?
are you mounting the device first? 'adb remount' if you have multiple USB devices it maybe confused, make sure your mounting the right device.
tullywork said:
are you mounting the device first? 'adb remount' if you have multiple USB devices it maybe confused, make sure your mounting the right device.
Click to expand...
Click to collapse
My tablet is the only USB device attached to the pc. It is the T301
i get all the way to the android-sdk-windows\tools directory (there is more to the directory i just didn't type it all.
from there i try
>adb shell
>adb mount
>adb remount
and each time I get 'access denied'
I've been hoping activity would pick up for modding the Velocity Micro Cruz Tablet T100 series. Glad to see good old XDA has taken a bite as I've been following the Cruz Tablet on Slatedroid which recently split the Cruz into Reader and Tablet forums.
I've been playing with the Android SDK and ADB under Lubuntu Linux. http://www.slatedroid.com/index.php?topic=14771.0 I have a system.img that someone in the cloud created that has the Market but it doesn't have access to protected apps. I used a modified build.prop with a ro.build.fingeprint... for another device and can get a more complete Market with access to protected apps. From there I am able to install apps from the Market with the AVD and move them to Cruz Tablet for installation.
But I haven't had success connecting to the Cruz using ADB under Linux. I have not located the USB device id for the Cruz Tablet. The ADB devices command shows the AVD fine but the Cruz shows up with question marks. Windows and Macs just work but Linux requires a USD device ID. If anyone knows the ID for the Cruz Tablet T100 series please post.
:8
I think my tablet is going back to best buy tomorrow. 170 was a great deal but too many issues with it. I wasnt really impressed with the battery life and nothing over android 2.0 is a major bummer. I need my tether! RIP Cruz
Agreed. I actually returned mine last week. The biggest killer was no Android Market or Google Apps. Had it at LEAST had Google Apps, I would have kept it, shame because the look/feel/etc was nice and I thought it had promise, but limited Apps obviously made it a brick (to me). I kept my Viewsonic GTablet, lots more work on the black market for that device, so it suits my needs (although I'm not a huge fan of the long 10" form factor, something closer to 8 or 9 inch and a 4:3 ratio seems to be my personal preference, definitely looking forward to checking out the Xoom.
I think mine is going back as well. Lack of Market is a killer. I can't even use appslib.

[Q] droid x download permissions issue

so im stuck and can not figure this out. for some reason the permissions for the download folders on my sd card do not have any user permissions checked. i can not download anything at all but the market is fine as it is on the internal memory i suppose. the only reason i came across the user permissions issue was because i found another post where someone had the same problem with downloading and corrected the issue by using root explorer and manually adding user permissions to any folder he used for downloading. now... here is my problem... i used root explorer and when i try to add user permissions to these folders, the settings that changed do not stick. i check mark the 3 boxes and accept the changes but if i go back into that folders specific permissions, they are unchecked once again. how can i get it to not revert back or better yet how can i just resolve the issue in whole so i dont have to keep fixing folder permissions on the sd card for app that downloads? i dont see why the sd card of all places would start having these permission issues. the guys post i came across tried to tie this issue to the fix permissions option in rom manager saying it may have caused the problem but i didnt use rom manager to fix permissions until this problem started. i was on liberty 1.5 rom then reverted back to rooted stock where i still have the problem with all downloading except the market again. any help would be greatly appreciated!
58 views and not a single response? wow.... so very shocking to see that, i bet if i had post this in the dev forum i would have gotten 15+ responses just to say that im in the wrong section then anther 30 for people to argue back and fourth on how everyone is being rude or that this is the reason devs stay in irc...
Give this a try if you have the sdk and adb set up.
from a command prompt:
1) adb devices (make sure that your phone shows up)
2) adb shell
3) su (assuming you have rooted your phone)
4) cd /mnt/sdcard/download (or whatever the folder on your sdcard for downloads is called)
5) chmod 777 /mnt/sdcard/download (or whatever your download folder is called)
this should change the permissions on your sdcard to have full permissions.
thanks for your reply! im grateful, but wouldnt that only change the permissions for the "download" folder? which is mostly only a default location for apps such as the browser?
The way sysadmin-x is suggesting makes the permissions way different than they are by default, I wouldn't recommend doing it that way.
If you want to change permissions on the entire sd card to what they are by default, try running(as root)
Code:
chown -R system:sdcard_rw /mnt/sdcard && chmod -R 075 /mnt/sdcard
Edit: that code messes up the permissions on one folder, after running that you should also run
Code:
chown -R root:root /mnt/sdcard/.android_secure && chmod -R 000 /mnt/sdcard/.android_secure
Just do this: download a terminal emulator from the market. Open the app. Type su and press enter. Give it root access. Type chmod 777 /sdcard and press enter.
Please note you need root to do this

[Q] Help Needed Regarding Device Info

Can anyone help me with this ? Recently I got this update device info thing and I do not know what to do about it .
x3YoonYulSic said:
Can anyone help me with this ? Recently I got this update device info thing and I do not know what to do about it .
Click to expand...
Click to collapse
Factory mode is enabled
do this:
you must be rooted.
using root explorer or file explorer or what else,
open file "factorymode" in efs/factoryApp directory, it probabely says "off", change to "on" (yes "on" is the correct setting to turn it off), then save
reboot
sent from my Galaxy
samersh72 said:
Factory mode is enabled
do this:
you must be rooted.
using root explorer or file explorer or what else,
open file "factorymode" in efs/factoryApp directory, it probabely says "off", change to "on" (yes "on" is the correct setting to turn it off), then save
reboot
sent from my Galaxy
Click to expand...
Click to collapse
Samersh72,
I've seen you helping people with this problem, but mine is a bit different. My EFS folder is empity. I cannot follow theses steps you wrote because i got an error. Could you help me!?
PS: My IMEI is working fine, calls everything. Just the FactoryMode (Text on the main screen).
rlucasrn said:
Samersh72,
I've seen you helping people with this problem, but mine is a bit different. My EFS folder is empity. I cannot follow theses steps you wrote because i got an error. Could you help me!?
PS: My IMEI is working fine, calls everything. Just the FactoryMode (Text on the main screen).
Click to expand...
Click to collapse
you must be rooted
type in terminal emulator
Code:
su
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
samersh72 said:
you must be rooted
type in terminal emulator
Code:
su
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
Click to expand...
Click to collapse
I'm typing exactly as you put "mount /efs" but i'm getting the following sintaxe error: "Usage Mount...[-r] [-w] [-o option] [-t type] device directory"
And yes, i'm rooted, with CF Auto Root...
Just adding...
I was using ES Explorer app to check the efs folder, and it was giving me empty as response. I changed o Root Explorer App and EFS folder seems ok. Now i think will be easier to fix.
rlucasrn said:
I'm typing exactly as you put "mount /efs" but i'm getting the following sintaxe error: "Usage Mount...[-r] [-w] [-o option] [-t type] device directory"
And yes, i'm rooted, with CF Auto Root...
Click to expand...
Click to collapse
try without the 2 mounting commands.
what is your variant??
in es explorer you must set the root access as r/w
samersh72 said:
try without the 2 mounting commands.
what is your variant??
Click to expand...
Click to collapse
Man, its done... Many Thanks..
After i was able to see the EFS content on Root Explorer app, i tried to change the factorymode status, but it was denied. Then, on the terminal emulator i changed the file permissions (chmod) e put it ON. Reboot and everything is OK.
Again many thanks...
hi,i have the fix for you.
x3YoonYulSic said:
Can anyone help me with this ? Recently I got this update device info thing and I do not know what to do about it .
Click to expand...
Click to collapse
i was had problem like that but without that yellow box.but i was have red words that said(factor mode is on some features may not work...wifi is turned off...etc)...hidden menu was not working...but after play with permissions...althing work again normally.u
**you have four ways to fix your problem(the first one that a member tell you to use a terminal and change valuse)...two using my methode...three->
using a tool called best smart tool(i t can falsh your phone and write efs folder and imei(from under battrey) using your usb cable)...four--> using jtag
service.
first you should be rooted and you have installed es file manager and give it root permission:
*permission for efs folder:
permissions:
*FactoryApp folder permissions:
owner and group: root root
permissions:
*factormode file permissions:
*keystr file permissions:
*carrier folder permissions:
*HiddenMenu file perimissonshis wil turn on your hiddenmenu in dial phone)
*imei folder permissions:
*mps_code.dat permissions:
***this is permissions for files that affect factorymode and imei....if you need permissions for another files please tell me.
i have galaxy s4 verizon on android 4.4.2 (kitkat)

[Q] MAC Address Keeps changing

Everything was good until I started messing with the 4.4 roms. Now no matter what I do. Full Wipe, Factory Image restore, try different Roms/Kernels, etc, my MAC Address will reset after every reboot. This is an issues as I use Mac Filtering on my router. Any Ideas?
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
joaocadide said:
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
Click to expand...
Click to collapse
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
..
chainup said:
For me it's only the last 6 numbers/letters that keep changing on reboot. For both Wifi and Bluetooth. Is it the same for you guys?
Click to expand...
Click to collapse
Yeah first are always 11:22:33
Thank you, bandit97!
It's working fine now! =D
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
i came from your link too but this didn't work for me
anyone know why?
Hi. This has been driving me crazy! My Nexus 4 also gets a new Mac address on each reboot. My local WiFi hotspot thinks i am a new customer every time I visit (as it uses Mac address filtering) which is frustrating. I got onto Google about it but they said i should return the phone to the retailer (didn't get it on the Play store). I tried reverting the phone to Android 4.3, resetting etc but nothing works. I the phone was fine at first so I can only assume it is a hardware fault. Does anyone have any more incite into this or a solution?
Could someone explain how I run the commands in an adb shell? I'm familiar with adb and android toolkit etc. Many thanks! PS. I tried it using root explorer and it did not work
Sent from my Nexus 4 using xda app-developers app
Where is /persist directory?
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
You DO need to be rooted
ayonbaxter said:
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
Click to expand...
Click to collapse
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on Google Play).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found here.
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
furboom1240 said:
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on ).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found .
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
Click to expand...
Click to collapse
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Lack of Details
tommy0014 said:
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Click to expand...
Click to collapse
First of all, do you have Superuser-managed root access? In order for me to assist, you need to answer that. The /persist directory should certainly exist, as it was so on all devices I own, rooted or not. When browsing the filesystem, please be careful what you mess with. Even with root access, you must exercise judgment in what you modify.
As always, Root Responsibly.
Stay custom, my friends...

[Q] How to disable change page buttons?

Hello,
my old Nook sometimes has faulty change page buttons, when i press them it's like they are constantly pressed and changes a lot of pages before it stops.
So I would like to disable them software side so that I can only use the touch screen (which works fine).
is it possible?
Also I have no way in settings to change the time, is it possible to do that maybe using terminal?
Thanks!
borzowsky said:
Hello,
my old Nook sometimes has faulty change page buttons, when i press them it's like they are constantly pressed and changes a lot of pages before it stops.
So I would like to disable them software side so that I can only use the touch screen (which works fine).
is it possible?
Also I have no way in settings to change the time, is it possible to do that maybe using terminal?
Thanks!
Click to expand...
Click to collapse
Which Nook model is this, exactly?
Hi sorry, it's the Nook Simple Touch (not the glowlight one, but the one without backlit)!
Thank you very much.
borzowsky said:
Hi sorry, it's the Nook Simple Touch (not the glowlight one, but the one without backlit)!
Thank you very much.
Click to expand...
Click to collapse
Alright, good.
To completely disable the four hard keys, all you have to do is navigate to /system/usr/keylayout using ES Fike Explorer (or something else), long-press on TWL4030_Keypad.kl, and change its permissions from rw- r-- r-- to --- rwx r-x. Then, after you reboot, your hard keys will not function anymore.
If for some reason you end up wanting your hard keys back, just change the permissions back to their original state.
Hope this helps!
ИΘΘK¡€ said:
Alright, good.
To completely disable the four hard keys, all you have to do is navigate to /system/usr/keylayout using ES Fike Explorer (or something else), long-press on TWL4030_Keypad.kl, and change its permissions from rw- r-- r-- to --- rwx r-x. Then, after you reboot, your hard keys will not function anymore.
If for some reason you end up wanting your hard keys back, just change the permissions back to their original state.
Hope this helps!
Click to expand...
Click to collapse
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
borzowsky said:
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
Click to expand...
Click to collapse
It probably is - I'm researching it right now. While you wait, though, here's the command for setting the time/date through ADB:
Code:
adb shell date -s YYYYMMDD.HHmmss
...in which "Y" is year, "M" is month, "D", is day, "H" is hour, "m" is minute, and "s" is second.
---------- Post added at 10:56 ---------- Previous post was at 10:45 ----------
borzowsky said:
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
Click to expand...
Click to collapse
Alright, I got it.
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
Then, a reboot will finalize the change, which can be done either straight from your Nook, or using this ADB command:
Code:
adb reboot
ok one last thing and I won't bother you no more!
to revert to working buttons, what is the corrisponding command to this one?
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
is the power button and the "N" button continue to work if i do the change, right?
That changes only the change page buttons, right?
borzowsky said:
ok one last thing and I won't bother you no more!
to revert to working buttons, what is the corrisponding command to this one?
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
is the power button and the "N" button continue to work if i do the change, right?
That changes only the change page buttons, right?
Click to expand...
Click to collapse
To revert the page buttons to working order, use this command:
Code:
adb shell chmod 644 /system/usr/keylayout/TWL4030_Keypad.kl
And yes, this modification will only turn off the side page-turn buttons, and not the "n" and power buttons (those are controlled by a different file, gpio-keys.kl).
Ok I tried the clock trick and it works, but this command:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
says read-only file system, how can i fix this?
edit: ok i put this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
in the shell, then quit the shell, gave the command and it didn't told me anything
then I did adb reboot and it rebooted, but the buttons to change page are still working.
borzowsky said:
Ok I tried the clock trick and it works, but this command:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
says read-only file system, how can i fix this?
edit: ok i put this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
in the shell, then quit the shell, gave the command and it didn't told me anything
then I did adb reboot and it rebooted, but the buttons to change page are still working.
Click to expand...
Click to collapse
Hmm. Let me look into this.
ИΘΘK¡€ said:
Hmm. Let me look into this.
Click to expand...
Click to collapse
yeah sure, take your time!
you've been really helpful so far
Did you manage to find a way?
borzowsky said:
Did you manage to find a way?
Click to expand...
Click to collapse
Sorry for not getting back to you - been pretty busy lately. Here's what I'm tryng to figure out how to do:
I have discovered in the past that if a system file's permissions are not rw- r-- r--, or 644 in numerical value, the OS will not recognize the file as usable. What I am trying to do here is use the chmod command (change mode) to change the permissions of TWL4030_Keypad.kl to something other than the default setting so that it will not get used, therefore making the side keys unusable.
The problem is, I need to actually find a permission setting that does keep the system from seeing the file, and then I have to translate it into a numerical value for the chmod command to work. I know that --- rwx r-x works, but I don't know if I translated it right.
I'll post again when I get something usable.
---------- Post added at 10:41 ---------- Previous post was at 10:12 ----------
borzowsky said:
Did you manage to find a way?
Click to expand...
Click to collapse
Alright, I have a solution! Use this command in ADB (after mounting /system as read-write [adb shell mount -o rw,remount /dev/block/mmcblk0p5 /system]):
Code:
adb shell chmod 000 /system/usr/keylayout/TWL4030_Keypad.kl
Then, after a reboot, you will be good to go.
I'll try this as soon as I get home.
thank you for your efforts.
great it worked, thank you very much!

Categories

Resources