[Q] Wifi MAC Fix? - G2 and Desire Z General

Solved: See post #4
Obviously for those with a modded kernel and broken MAC.
If we knew the real MAC address for the specific device, couldn't we set the module's MAC to our real one?
Or just a MAC spoofer? But more like an un-spoofer..

Im looking for the answer as well...
I have been through every oc kernel so far, only stock/insmod seems to keep the mac addy. This might be the best option until a proper solution is found, if anyone has an idea on how to insmod on startup that would be good.
I also tried ipconfig eth0 hw ether, but got an invalid argument.

tijuanacartel said:
Im looking for the answer as well...
I have been through every oc kernel so far, only stock/insmod seems to keep the mac addy. This might be the best option until a proper solution is found, if anyone has an idea on how to insmod on startup that would be good.
I also tried ipconfig eth0 hw ether, but got an invalid argument.
Click to expand...
Click to collapse
Can't you setup a script that insmod's and set that up to run on startup?
I'm sure there is somewhere in the ROM where a script can be added for it to run on boot, or at least a boot time Android one...
init.rc perhaps?

Okay i found it... there is a file called /bootcomplete.rc that calls
/system/xbin/busybox run-parts /system/etc/init.d
so, on stock kernel with oc-dz.ko:
Code:
# cd /system/etc/
# mkdir init.d
# cd init.d
# echo insmod /system/lib/modules/oc-dz.ko pll2_l_val=74 > overclock
# chmod 0755 overclock
will load the module at boot. wifi mac is correct

Okay I've been using this for most of the day and just had a hard crash on level 99 of robo defence(F7U13!) Looking into it, it seems this kernel module only seems to step up from 700 straight to 1497! I'm disabling it for now.
Apparently cyanogen is quite a lot faster than the stock Sense, even without overclock. As soon as it hits RC2, I'm gonna give it a shot.

tijuanacartel said:
Okay i found it... there is a file called /bootcomplete.rc that calls
/system/xbin/busybox run-parts /system/etc/init.d
so, on stock kernel with oc-dz.ko:
Code:
# cd /system/etc/
# mkdir init.d
# cd init.d
# echo insmod /system/lib/modules/oc-dz.ko pll2_l_val=74 > overclock
# chmod 0755 overclock
will load the module at boot. wifi mac is correct
Click to expand...
Click to collapse
EDIT
Trying from a Terminal I get: "undable to chmod overclock: Read-only file system"
I tryed from ADB and all commands were accepted, file was created and chmod processed, but after reboot the OC module is not loaded
What ROM are your using ??

Obviously you should remount your system partition rw

tijuanacartel said:
Obviously you should remount your system partition rw
Click to expand...
Click to collapse
OMFG I really need to sleep a little
What ROM are you using ?? Have you changed the Kernel ??

at the time i was using stock.. currently using virtuous from rom manager

I've been strugglin with that command line for days, trying to find a way t make it stick from boot (and not typing it from a console), I finaly made it today via updater script (update.zip).
I also included the stock radio module and the stock kernel (rooted) to the package, so it can serve as a "rescue kit" for other users stuck with the MAC WiFi shizz. I shared it @ devs forum.

Related

[EXPERIMENTAL]-PROJECT JIT-(Just in time)EXPERTS ONLY |Aug 13th|

New as of Saturday August 8th
I will update the files every time I find a problem​
WARNING PLEASE READ:
Project JIT is highly highly experimental! If you are to do this, MAKE A NANDROID BACKUP IN ROM MANAGER OR RECOVERY! There are always chances of something going wrong. I nor anyone else is responsible of what happens.
Experienced users please know the possible risks:
Boot Looping, requiring a restore
Constant FC's
Wiping everything
These are just the risks, please note it is not 100%​
JIT stands for Just in time compiler. It does not like Touchwiz, so download ADW.Launcher or LauncherPro before starting and set it as default.
This whole process is in ADB. If you dont know how, or what it is, DONT DO IT!
Things to do before you start:
-Download a different launcher than TouchWiz
-Make a backup in recovery or Rom Manager
-Did I mention DO A BACKUP!
-If you have an external SD card, pull it out
-Download the vmlibs file
What I expect you to know before you start:
-ADB
-What JIT is
-How this will effect the performance
-The risks
-How its not my fault if you screw your phone over
-How experimental this is
-How to make a nandroid backup
-How to make a nandroid restore
Remember, this is experimental and I cannot guarantee for it to completely work.
Download This- vmlibs.zip
Then follow these steps:
-Make a backup!!!
-Create 2 folders on your internal sdcard: “jit” & “dalbk”
-Extract the vmlibs.zip to the “jit” folder on your sdcard
-Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad, text edit or similiar program.
-Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Edit the following line:dalvik.vm.startheapsize=8m
to: dalvik.vm.startheapsize=12m
-Save the changes
-Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit, but if your phone boot loops, thats why you have A BACKUP!
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
While in recovery, wipe the dalvik cache, this will prevent it from boot looping.
To Disable
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
If that fails, that is why you have a backup. To restore, go to recovery, click on nandroid, and restore from your backup.
Reserved for future posting
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
LGSilva said:
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It didn't here. Not sure if that is due to other fsckup or the fact that I was running I9k rom with my kernel and sdcard hack...
Restoring to stock to give this a whirl
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
hansmrtn said:
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
Click to expand...
Click to collapse
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
NukaCola said:
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
Click to expand...
Click to collapse
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
hansmrtn said:
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
Click to expand...
Click to collapse
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
NukaCola said:
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
Click to expand...
Click to collapse
Yeah, thats why I had to fix some stuff lol. I noticed that it wouldnt go past the att screen. Now it should work correctly. The worst that could happen now is it boot loops on the Galaxy S screen
Haha I was just about to post the same problem, downloading new file and trying it again!
Zilch25 said:
Haha I was just about to post the same problem, downloading new file and trying it again!
Click to expand...
Click to collapse
Hey, when you edit the build.prop to add the dalvik vm line, can you look for the vm heap size and change it from 48 to 32? I am about to test doing that, and I would like more feedback
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Zilch25 said:
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Click to expand...
Click to collapse
Dont worry, I will try it
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Zilch25 said:
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Click to expand...
Click to collapse
Do you know how to run a logcat?
Its gonna take a while because its re writing the dalvik cache
That I do not, but I'm willing to try it if you can give me a quick crash course
Zilch25 said:
That I do not, but I'm willing to try it if you can give me a quick crash course
Click to expand...
Click to collapse
Well I am looking at my logcat now, and it is just repeating boot animation.
A logcat is useful, so how you do it is adb logcat.
I changed a couple things to test around with here is what I did-
I added all of this to the build.prop-
#JIT
dalvik.vm.execution-mode=int:jit
and changed:
dalvik.vm.heapsize=48m
to
dalvik.vm.heapsize=32m
Right now I am resorting to try the older vmlibs with the new settings
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Zilch25 said:
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Click to expand...
Click to collapse
No thanks for the feedback. Its only worked for me once, and then when I rebooted it got stuck in a boot loop.
Whats a device thats running android 2.1, and has a jit hack that is extremely similar to the Galaxy S series?

Wifi "error"

ok so to try and not sound redundant ( prob not gonna happen) i had the cm7 release running perfectly no issues ... then i decided to install faux's OC UV kernel which was great ... everything was speedy and working fine up until last night where my phone froze and i had to pull the battery ... after once booted up everytime id try and turn on wifi it wouldnt and i would just recieve a message that says error ... tried rebooting , wiping and reflashing .. tried flashing royals new GB rom exactly the way the instructions said too ... still nothing ... anybody know what might be causing this issue ... ive tried 3 diff roms with different kernels and still no wifi ... could this be hardware ????
bump.
Ive tried wiping everything including /system and davlik and still cant get the wifi to work ... i was told that i might have a bad module so i pushed on from the kernel i was currently using and still nothing ... anybody have any type of advice ?
bump .... im willing to donate !
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Faux my name is neidlinger and I get assfucked by you and other homos.
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Nice to get help from the master himself
Sent from my HTC Glaciee using XDA Premium App
Double post by mistake. my bad
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Sigh ... no luck. I used your GB kernel with the Royal Ginger 1.6 rom ... rafyvitto thinks it might be my hardware so i was prob gonna have somebody take a look at it sometime this week .. what a bad one !
For what ever reason if i am at home, i have to use static ip address to get on my router, no other devices on the network have this issue, including my old phone. its probably not related to your problem but worth trying.
[via XDA premium]

Fix Mobile Data drain.

After 2 days of testing i think i have a clean solution to fix the mobile data drain by setting the preferred network mode to 1 (GSM only). No need to delete or rename anything. Just update the db that is already there .
You need a rooted device for this.
Extract the sqlite3.zip and push to your device with the following commands:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell
su (to gain root permissions)
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
reboot
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
Sure, as long as you have some sort of terminal emulator installed.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
with root explorer and a terminal app (eg connectbot) you can do it.
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Thanks! Mine is done. I'll report back later after I charge and give it a go.
mrkrabs said:
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
_motley said:
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
Click to expand...
Click to collapse
couldn't describe it better
2g = only poll cell if request is made that needs cell, 3g = poll all the time, which means that if you change to only 2g then it should not check for cell if you are in wifi range.
I am sure thats how the tech works if i remember my time at nokia right LOL
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
kinnerc said:
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
Click to expand...
Click to collapse
Default value is 0 (zero).
agentdax5 said:
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Click to expand...
Click to collapse
It's not about what your stats say, but what your mA drain is. i loose only a couple of % in a night (sleep).
edgemaster191 said:
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
Click to expand...
Click to collapse
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
FTFY. 10char.
I am going to have to run some logs....just not seeing any drain that would justify doing this ....will definitely keep an eye out for it though
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
such things will be able with kernels that overwrite the default.prop
matguard said:
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
Click to expand...
Click to collapse
i was able to finally get it, i copied the splite3 to /system/bin using root explorer, ran chmod through terminal emulator then ran the final command from adb shell.
not ideal but it worked

Tweak init.rc

Is it possible to modify init.vedana.rc? I see some possibilities for tweaking in there...
maybe? in the prior devices i've used, init.rc usually resets itself on bootup.
minotauri said:
maybe? in the prior devices i've used, init.rc usually resets itself on bootup.
Click to expand...
Click to collapse
Yes init.rc seems to "reset" at startup.
Do you know any ways around that?
Or another way to insmod a kernel module at startup?
Cheers
lallare said:
Yes init.rc seems to "reset" at startup.
Do you know any ways around that?
Or another way to insmod a kernel module at startup?
Cheers
Click to expand...
Click to collapse
init.rc is in the boot.img, there's no way to mod this file atm cause we can't flash a new boot.
You may use /system/etc/install-recovery.sh to insmod your module(s).
vache said:
init.rc is in the boot.img, there's no way to mod this file atm cause we can't flash a new boot.
You may use /system/etc/install-recovery.sh to insmod your module(s).
Click to expand...
Click to collapse
Thanks for a fast reply!
No such file there, should I just add it?
init.goldfish.sh is there, but I don't see it trying to execute the insmod I added there.
The file is not located in root (where there is the init.rc), you have to navigate to /system/etc.
vache said:
The file is not located in root (where there is the init.rc), you have to navigate to /system/etc.
Click to expand...
Click to collapse
Yes, thanks. Still not there..
Rooted Iconia A500
/system/etc # ls
NOTICE.html.gz
apns-conf.xml
asound.conf
bluetooth
bootsound.wav
dbus.conf
dhcpcd
event-log-tags
firmware
gps
gps.conf
hosts
init.goldfish.sh
media_profiles.xml
nvram.txt
permissions
ppp
security
updatecmds
vold.fstab
wifi
/system/etc #
So create it and chmod it to 4755.
Try to insmod some module with it. (you can check with "lsmod")
vache said:
So create it and chmod it to 4755.
Try to insmod some module with it. (you can check with "lsmod")
Click to expand...
Click to collapse
Works perfectly!
Thanks!
very good people, can you explane for dumbs how to insmod in boot. It somewhere close but not cleare.
Thanks

CIFS for Retail Tab 10.1

I'd like to get CIFS working on my Tab 10.1. Has anyone got it working or have the module that will work for me?
Thanks!
muzicman82 said:
I'd like to get CIFS working on my Tab 10.1. Has anyone got it working or have the module that will work for me?
Thanks!
Click to expand...
Click to collapse
i could build this for you.
pull me:
/proc/config.gz
and
a uname -a output.
adb pull /proc/config.gz .
adb shell uname -a > my_uname
pershoot said:
i could build this for you.
pull me:
/proc/config.gz
and
a uname -a output.
adb pull /proc/config.gz .
adb shell uname -a > my_uname
Click to expand...
Click to collapse
Output says uname is not defined? Files are attached (zipped).
Thanks for the help!
I believe all I should have to do once the cifs.ko is built is put it in a folder (such as /system/lib/modules/) and tell CIFS Manager to load it?
muzicman82 said:
Output says uname is not defined? Files are attached (zipped).
Thanks for the help!
I believe all I should have to do once the cifs.ko is built is put it in a folder (such as /system/lib/modules/) and tell CIFS Manager to load it?
Click to expand...
Click to collapse
ah yes thats right. no uname in stock.
could you pls go to system settings or dload an app to get it?
you would put it in /data/local/modules (for ex) and let cifs manager load it in.
pershoot said:
ah yes thats right. no uname in stock.
could you pls go to system settings or dload an app to get it?
you would put it in /data/local/modules (for ex) and let cifs manager load it in.
Click to expand...
Click to collapse
Ok, you lost me.. do I need to set a uname, or is it actually there somewhere just not being reported?
Where would I find it in System Settings?
muzicman82 said:
Ok, you lost me.. do I need to set a uname, or is it actually there somewhere just not being reported?
Where would I find it in System Settings?
Click to expand...
Click to collapse
you cant do a uname. your stock retail does not come with the functionality.
get this to me some other way. either through system settings or even through setcpu (that will report that whole string).
pershoot said:
you cant do a uname. your stock retail does not come with the functionality.
get this to me some other way. either through system settings or even through setcpu (that will report that whole string).
Click to expand...
Click to collapse
Attached is the full output from "Under the Hood" app.
The Settings -> About tablet tab has the following:
Kernel - 2.6.36.3 | [email protected] #1
Build Number - HMJ37.UEKF3 P7510UEKF3
If none of those are it... redirect me.
Thanks!
muzicman82 said:
Attached is the full output from "Under the Hood" app.
The Settings -> About tablet tab has the following:
Kernel - 2.6.36.3 | [email protected] #1
Build Number - HMJ37.UEKF3 P7510UEKF3
If none of those are it... redirect me.
Thanks!
Click to expand...
Click to collapse
install setcpu and go to about, device, and under kernel, paste that whole output for me.
pershoot said:
install setcpu and go to about, device, and under kernel, paste that whole output for me.
Click to expand...
Click to collapse
"Linux version 2.6.36.3 ([email protected]) (gcc version 4.4.3 (GCC)) #1 SMP PREEMPT Mon Jun 6 08:59:10 KST 2011"
try this:
http://droidbasement.com/galaxy/kernels/2636/stock-modules/cifs.zip
unzip it.
adb shell mkdir /data/local/modules
adb push cifs.ko /data/local/modules
adb shell chmod 755 /data/local/modules
adb shell chmod 644 /data/local/modules/cifs.ko
adb shell insmod /data/local/modules/cifs.ko
adb shell dmesg <-- after running this, look at the end of the log, do you see it loaded in?
adb shell lsmod <-- if the above is true, do you see it in memory?
pershoot said:
try this:
http://droidbasement.com/galaxy/kernels/2636/stock-modules/cifs.zip
unzip it.
adb shell mkdir /data/local/modules
adb push cifs.ko /data/local/modules
adb shell chmod 755 /data/local/modules
adb shell chmod 644 /data/local/modules/cifs.ko
adb shell insmod /data/local/modules/cifs.ko
adb shell dmesg <-- after running this, look at the end of the log, do you see it loaded in?
adb shell lsmod <-- if the above is true, do you see it in memory?
Click to expand...
Click to collapse
On:
Code:
adb shell insmod /data/local/modules/cifs.ko
I get:
Code:
insmod: init_module '/data/local/modules/cifs.ko' failed (Operation not permitted)
muzicman82 said:
On:
Code:
adb shell insmod /data/local/modules/cifs.ko
I get:
Code:
insmod: init_module '/data/local/modules/cifs.ko' failed (Operation not permitted)
Click to expand...
Click to collapse
your not allowed to insmod.
youll need root access.
if you have an unlocked bootloader, flash in CWM, then push to your system at the bare minimum, su and superuser, then back to nvlfash and put back your stock recovery.
if you dont have an unlocked bootloader, then youll have to intrusively gain root.
pershoot said:
your not allowed to insmod.
youll need root access.
if you have an unlocked bootloader, flash in CWM, then push to your system at the bare minimum, su and superuser, then back to nvlfash and put back your stock recovery.
if you dont have an unlocked bootloader, then youll have to intrusively gain root.
Click to expand...
Click to collapse
what you can try is get CIFS manager, and load it in via that app. it may take.
try it, and see if it works out.
Finally, site is back up.
Ok, if I use CIFS Manager, tell it to load via insmod and set the correct path, kill the program, launch the program, then the end of dmesg reads:
Code:
<3>[ 160.853751] cifs: version magic '2.6.36.3-58 SMP preempt mod_unload ARMv7 ' should be '2.6.36.3 SMP preempt mod_unload ARMv7 '
If I do lsmod, I get:
Code:
dhd 225862 0 - Live 0xbf000000
Lastly, if I try to mount a SMB share, I get "No such device".
I thought I was already rooted... Or at least the superuser app works. And I am on CWM. Is there a reason to go back to stock?
Ill change the vermagic string in the module.
Ill repost tonight.
if you are using the kernal from pershoot, cifs manager simply will work with the module ... i was told so few days ago and i am using it. now .
see the link below
http://forum.xda-developers.com/showthread.php?t=1141307
Sent from my SHW-M110S using XDA App
rainby said:
if you are using the kernal from pershoot, cifs manager simply will work with the module ... i was told so few days ago and i am using it. now .
see the link below
http://forum.xda-developers.com/showthread.php?t=1141307
Sent from my SHW-M110S using XDA App
Click to expand...
Click to collapse
I'm just on stock kernel. Don't really want to overclock... I like my battery life.
unless i am wrong, i believe after flash the kernel..... if you do not install setcpu and overclock by using it, it runs at 1Ghz.
kernel flash also won't erase whatever installed on the 10.1 ..... just in case you will worry that as i originally did ...
muzicman82 said:
I'm just on stock kernel. Don't really want to overclock... I like my battery life.
Click to expand...
Click to collapse
pershoot said:
Ill change the vermagic string in the module.
Ill repost tonight.
Click to expand...
Click to collapse
try this:
http://droidbasement.com/galaxy/kernels/2636/stock-modules/cifs.zip
rainby said:
unless i am wrong, i believe after flash the kernel..... if you do not install setcpu and overclock by using it, it runs at 1Ghz.
kernel flash also won't erase whatever installed on the 10.1 ..... just in case you will worry that as i originally did ...
Click to expand...
Click to collapse
But you can flash the kernel only on tabs with an unlocked bootloader, isn't it?
So if your bootloader is locked you need cifs.ko for the stock kernel.

Categories

Resources