Just picked up three Gtablets yesterday, and immedialty loaded up Vegan 5.1; my question is how do I go about changing the kernal in order to overclock? I went over to this thread
[Kernel] 2.6.32.38 - OC-UV-VFP_FP (1.400GHZ) - Gtab/Zpad (Update 4/20/11);
and started reading up on it, but it gets to be a little confusing. Also, I see no guides on how to install a custom kernal. Do I just do it in CWM
I went to this link http://droidbasement.com/db-blog/, and it says to flash zip through recovery, but there are a ton of files on that site; than it says
To use one of the kernel modules:...do a bunch of stuff.
I am a bit confused here as to what I need to do to get a custom kernal with Vegan 5.1.1; Can someone point me in a direction?
VEGAn 5.1 is Froyo (Android 2.2) based, so you want to download this kernel from that page:
ViewSonic Gtab/Malata Zpad (Froyo):
boot-cm_2632.38-oc-uv-xtra-vfpv3_fp-042011.zip
Download: boot-cm_2632.38-oc-uv-xtra-vfp_fp-042011.zip
As to how to install it, you just flash it in clockwork mod, the same way you installed VEGAn 5.1 on your tablet (place the file on the "sdcard", go into clockwork mod, go to install zip from sdcard, then choose to install the kernel file).
For the stuff about the kernel modules, it requires knowledge of how to use adb shell, which is a little bit complicated, so I wouldn't worry about it. The modules aren't necessary, they just add a few additional functions and settings to the kernel. You'll still be able to overclock without installing the modules. Hope this helps.
Modules without ADB
Not that it matters completely, but you can push modules to the kernel without using ADB. If you have Root Explorer, you can mount the correct subdirectory as RW, copy the files there, then use terminal emulator to chmod and insmod per Pershoot's other instructions.
raphenucleus said:
VEGAn 5.1 is Froyo (Android 2.2) based, so you want to download this kernel from that page:
ViewSonic Gtab/Malata Zpad (Froyo):
boot-cm_2632.38-oc-uv-xtra-vfpv3_fp-042011.zip
Download: boot-cm_2632.38-oc-uv-xtra-vfp_fp-042011.zip
As to how to install it, you just flash it in clockwork mod, the same way you installed VEGAn 5.1 on your tablet (place the file on the "sdcard", go into clockwork mod, go to install zip from sdcard, then choose to install the kernel file).
For the stuff about the kernel modules, it requires knowledge of how to use adb shell, which is a little bit complicated, so I wouldn't worry about it. The modules aren't necessary, they just add a few additional functions and settings to the kernel. You'll still be able to overclock without installing the modules. Hope this helps.
Click to expand...
Click to collapse
Thanks for the quick reply....I feel like a noob.....do I need to wipe before or after install? And what program do you prefer for overclocking? And what settings?
michaeljwestii said:
Not that it matters completely, but you can push modules to the kernel without using ADB. If you have Root Explorer, you can mount the correct subdirectory as RW, copy the files there, then use terminal emulator to chmod and insmod per Pershoot's other instructions.
Click to expand...
Click to collapse
What are the benefits to the kernels?
PhilPan said:
Thanks for the quick reply....I feel like a noob.....do I need to wipe before or after install? And what program do you prefer for overclocking? And what settings?
Click to expand...
Click to collapse
When flashing new kernels, it's recommended to wipe the cache partition and wipe the dalvik cache before flashing the new kernel. I do this every time to be safe, but I don't know how important it really is. I've forgotten to do it on occasion and didn't notice any problems.
I use setcpu to set the cpu range and also use it to turn down the max cpu to 216 MHz when the screen is off to save battery. The range I use is 216 to 1000 MHz. I don't overclock, because I've found it to be fast enough without it and overclocking can decrease your battery life. But I'd say try out various frequency ranges and see what you like the best.
would nvflashing back to stock 3588 FW change the kernals back to original?
yes, flashing any rom will flash the kernel for that rom.
Related
Okay, so tried the Vibrant OC UV Kernel so I can overclock my Vibrant, but I get stuck in boot loop everytime. This is what I did;
-Installed Eugene's ROM 2.2 JK2 using Odin3 v1.7- Worked fine.
-Installed ROM Manager
-Flashed Recovery using ROM Manager
-Download "Vibrant OC UV Kernel v1.0"(which is a zip file) on PC and moved it to root of SD card
-Reinserted SD card into Vibrant and used ROM Manager to Reboot in Recovery Mode
-In Recovery I, selected reinstall packages, selected choose zip from sd card, selected external sd, selected "Vibrant_OC_UV_Kernel_v1.0.zip"
Now I don't know what I'm doing wrong but every time it finishes it gets stuck in a boot loop. The only thing I can think of is what JAC said about kernels:
NOTE:For compatibility with all phones this does not automatically OC to 1.2Ghz per Unhelpfuls idea as not everyone can handle 1.2Ghz. Use a user script in the init.d folder with
Code:
#!/system/bin/sh
echo 1200000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
or setCPU to OC the Kernel to 1.2Ghz. 9.8MFLOPS is about what these CPU's average in Linpack at this speed. I've had it in the 10's and that may be coming back as another option.
Download the Overclock script here and make sure you put it in the /system/etc/init.d folder (right click and save with no extension for Windows users)
Anybody have any ideas?
dverrette said:
Okay, so tried the Vibrant OC UV Kernel so I can overclock my Vibrant, but I get stuck in boot loop everytime. This is what I did;
-Installed Eugene's ROM 2.2 JK2 using Odin3 v1.7- Worked fine.
-Installed ROM Manager
-Flashed Recovery using ROM Manager
-Download "Vibrant OC UV Kernel v1.0"(which is a zip file) on PC and moved it to root of SD card
-Reinserted SD card into Vibrant and used ROM Manager to Reboot in Recovery Mode
-In Recovery I, selected reinstall packages, selected choose zip from sd card, selected external sd, selected "Vibrant_OC_UV_Kernel_v1.0.zip"
Now I don't know what I'm doing wrong but every time it finishes it gets stuck in a boot loop. The only thing I can think of is what JAC said about kernels:
NOTE:For compatibility with all phones this does not automatically OC to 1.2Ghz per Unhelpfuls idea as not everyone can handle 1.2Ghz. Use a user script in the init.d folder with
Code:
#!/system/bin/sh
echo 1200000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
or setCPU to OC the Kernel to 1.2Ghz. 9.8MFLOPS is about what these CPU's average in Linpack at this speed. I've had it in the 10's and that may be coming back as another option.
Download the Overclock script here and make sure you put it in the /system/etc/init.d folder (right click and save with no extension for Windows users)
Anybody have any ideas?
Click to expand...
Click to collapse
are you using the unnofficial rom? or the old froyo that doesent brick?
if your using the old one (Froyo that doesent brick) you might consider updating to Macnut R13 or The Unofficial.
and you might want to use a more up to date kernel as well.
I'm not familiar with the kernel you posted either... thats not Jac's kernel is it?
if so, it wont work with 2.2 roms.
I'd try one of eugene's if your on his rom. (make sure its a 2.2 kernel first though)
you may want to re-odin beforehand though just in case.
Im still fairly mew to this so how would I know if I have The Unofficial or Froyo that does not brick? This is what's in my settings,
Firmware 2.2
Sent from my SGH-T959 using XDA App
Baseband: T959UVJK2
Kernel: 2.6.32.7
Build: FROYO.UVJK2
Sent from my SGH-T959 using XDA App
Also this is the MD5 file I use with Odin, "Eugene_2E_JK2_Froyo.tar.md5"
So the question remains if this is the unofficial or the froyo that doesn't brick?
I've created a few flashable zip files to ease the eMMC dual boot setup. You can flash them using Clock Work Recovery.
Warning: Only specially packaged flashable dual boot ROMs like the ones I packaged below will flash to dual boot partition. Other flashable zips will overwrite your default boot.
Seems there is a problem flashing the zips from CWM on SD. See this post for a workaround, or use CWM on eMMC.
Just a word on booting into recovery. With the dual boot u-boot.bin, I have changed the button combo to VOL UP + VOL DOWN for recovery. So if you want to go to recovery, remember this is the key combo you need to hit. Not Power + n.
1. Prepare dual boot - http://dl.dropbox.com/u/20480343/prep-dualboot-0.1.zip
Flash this zip file will setup the dual boot partitions. If your NC is already setup using my previous dual boot script, there is no need to flash this again.
Note 1 - This does a resize of your /media partition. You data on /media should be intact. If you want to be safe, backup your /media before flashing.
Note 2 - /media partition will be resized to about 3.9 GB. If your existing data on /media is more that 3.9GB, you won't be able to flash this.
2. Remove dual boot - http://dl.dropbox.com/u/20480343/remove-dualboot-0.1.zip
If you want to revert to stock, simply flash this file.
3. Dual boot ROMs
Now the dual boot ROMs. These will be flashed to the dual boot partitions (partition 9 and 10) on eMMC. Hold 'n' button while powering up to boot into dual boot ROM.
My modified u-boot.bin based on B&N 1.2 source - Seems previous version is having compatibility issues with 2.6.32 kernel. This is updated base on B&N 1.2 source. Flash using CWM. It only overwrites the u-boot.bin on boot partition. Boot message should show "(multi)U-Boot v0.3 loading..." after flashing this zip.
Flashable dual boot Nookie Froyo v0.6.8
Flashable dual boot Honeycomb Preview v04
Flashable dual boot HC v04 with gapps - credit goes to pauljohnson75
Flashable dalingrin's 1.1GHz OC kernel for dual boot HC - credit goes to dalingrin for the oc kernel, and pauljohnson75 for creating the dual boot flashable
Flashable zip to move your stock Eclair to dual boot partition v02 - This is not really a ROM strictly speaking. To avoid infringing B&N IP, no file from stock ROM is included in this zip. Scripts in this zip simply copies your stock ROM partitions and make the necessary adjustment to ramdisk. After flashing this, you will have an identical ROM setup on your dual boot partition. You are free to do whatever to your default ROM. For example, you can flash other ROMs to overwrite your default ROM. You will still be able to boot into stock eclair by holding 'n' button. Only thing to note is if the other ROMs you flash overwrites u-boot.bin, you will lose the dual boot capability.
Flashable dual boot CM7 nightly (cm_encore_full-22)
Note 1 - You can flash this using CWM 3.0.0.5. Newer version of CWM not required.
Note 2 - This will convert secondary /system and /data partitions to ext4. They will not be compatible with other dual boot ROMs any more. You need to flash remove-dualboot-0.1.zip, then prep-dualboot-0.1.zip, before flashing other dual boot ROMs.
Note 3 - This will wipe your dualboot data partition.
Link not longer working
unknown.soul has packaged dalingrin's OC kernels for dual boot. Get them below. thanks unknown.soul
Eclair
Froyo
CM7
Honeycomb
Also gapps
Google Apps
Credits
cicada for Nookie Froyo. My update scripts are also based on his NF flashable.
deeper-blue for Honeycomb.
cm7 dev team for porting CM7 to NC
other xda developers who have contributed to NC community.
Holy Crap! How am I supposed to get any REAL work done today?
This is crazy awesome. I'm downloading everything right now. i will let you know how it goes.
Thank you!!!
Wow, this makes dual booting so much easier! thanks man!!
For real though, I have a deadline today and you come along and release this! You sir are awesome!!! Gonna flash it right now and then hopefully I can get some work done.
I see CM7 was just released. Would I be able to flash this to my dual boot partition?
racks11479 said:
For real though, I have a deadline today and you come along and release this! You sir are awesome!!! Gonna flash it right now and then hopefully I can get some work done.
I see CM7 was just released. Would I be able to flash this to my dual boot partition?
Click to expand...
Click to collapse
Normal flashables will flash to default partitions. That will overwrite your default boot OS. I have to package these flashable zips specifically to flash to dual boot partition. They are not compatible.
rookie1 said:
Normal flashables will flash to default partitions. That will overwrite your default boot OS. I have to package these flashable zips specifically to flash to dual boot partition. They are not compatible.
Click to expand...
Click to collapse
Yeah, I'd figured as much.... was hoping and wishing that under some miracle way it would have been possible. Thank you again for your hard work on this. It's pretty much made my day.
This is awesome downloading now. Are these just the base Roms or do they include any of the Google apps?
No gapps included.
get it here http://forum.xda-developers.com/showthread.php?t=917660
Is it possible to overclock this? If so, how?
racks11479 said:
No gapps included.
get it here http://forum.xda-developers.com/showthread.php?t=917660
Is it possible to overclock this? If so, how?
Click to expand...
Click to collapse
how does one push gapps and oc kernel in context of dual bootsetup?
rookie1 said:
I've created a few flashable zip files to ease the eMMC dual boot setup. You can flash them using Clock Work Recovery.
Click to expand...
Click to collapse
If I want to use this but keep oc 1100 for both froyo and eclair how do i do that. also if I want to install gapps on the froyo part of dual boot what mount commands do i need to push it to right place in adb?
Canadoc said:
If I want to use this but keep oc 1100 for both froyo and eclair how do i do that. also if I want to install gapps on the froyo part of dual boot what mount commands do i need to push it to right place in adb?
Click to expand...
Click to collapse
Not sure about the overclocking. I would really like to know how as well.
But with gapps. I didn't use adb. I just placed the unzipped gapps folder on my sdcard and installed it through terminal emulator in dev tools on my nook.
su
mount -o remount,rw /system
cp -r /sdcard/gapps/system/* /system
exit
Thats about it!
racks11479 said:
Not sure about the overclocking. I would really like to know how as well.
But with gapps. I didn't use adb. I just placed the unzipped gapps folder on my sdcard and installed it through terminal emulator in dev tools on my nook.
su
mount -o remount,rw /system
cp -r /sdcard/gapps/system/* /system
exit
Thats about it!
Click to expand...
Click to collapse
thanks will try this
what type of quadrant scores u getting on 800?
Just ran a quadrant of 969.
racks11479 said:
Not sure about the overclocking. I would really like to know how as well.
But with gapps. I didn't use adb. I just placed the unzipped gapps folder on my sdcard and installed it through terminal emulator in dev tools on my nook.
su
mount -o remount,rw /system
cp -r /sdcard/gapps/system/* /system
exit
Thats about it!
Click to expand...
Click to collapse
Can we access sdcard from either booted rom?
I flashed the NF one, and yes I'm able to mount and access my sdcard
Did anyone have any problems installing? I followed the instructions and I can get Nook Honey to boot but Nookie Froyo gets stuck at the Android_ screen, before the OS actually starts loading. I've tried reverting back to stock and starting over, and still no luck. Any suggestions would be greatly appreciated.
Awesome
Not sure how I did this but I didn't do a wipe or any formats before I installed all three zips. I installed all three at once from inside clockwork. Anyway my nookie froyo that I had setup perfect is still there just like I left it inculding the overclocked kernel. And if I hold down the n key and boot it boots right into Honeycomb not sure how I did this but its awesome. Thanks rookie1, now I just need to get gapps onto Honeycomb.
For oc kernels remember the file name is uFImg for the second boot. For those of you pushing an OC kernel to the alternate boot.
pauljohnson75 said:
Not sure how I did this but I didn't do a wipe or any formats before I installed all three zips. I installed all three at once from inside clockwork. Anyway my nookie froyo that I had setup perfect is still there just like I left it inculding the overclocked kernel. And if I hold down the n key and boot it boots right into Honeycomb not sure how I did this but its awesome. Thanks rookie1, now I just need to get gapps onto Honeycomb.
Click to expand...
Click to collapse
Why did you flash all 3 zips? You can only install one ROM on the new partition. I believe that this doesn't touch your original setup at all. It only flashes the rom on the new partition that was created.
Ok if someone can please help.
I have dual boot set up with eclair as stock boot and my n boot gives me froyo.
used titanium backup and have my froyo mostly back up and running though some apps caused soft reboots during the reinstall from TB.
Froyo seems to be running fine with what is installed so far. Flash is workig but since only getting quadrants in the 900-960 range it is kinda choppy. Was hoping there was a way to get the oc kernel onto the froyo boot as it is still present on the original eclair boot. The only real advantage for me of Froyo is that it should be faster and flash. But since it is not overclocked.....
Any ideas how to get the froyo oc kernel to the right place?
Upon searching through various XDA forum threads, many youtube videos and other Android based websites. I finally decided to actually make a thread to help gain a better insight into what I want to do.
So, as I'm posting in this particular forum you can imagine I have a Galaxy Tab 10.1 Wifi Only [GT-P7510] Running Android Version 3.1 and I would assume I'm running the stock kernel.
I've already rooted the tab, using Odin and CWM of which are probably the only things I am a little bit familiar with. Im only really following instructions with next to no knowledge of the Android OS. I essentially want to maximise the use of my tablet but as there's so many different resources with custom roms and kernels. It's hard to figure out whats best and why it's better than another to fully utilise my tablet.
I want to run ICS on my tab, and I've been told "Pershoots" ' is the 'best' kernel around. Though how I do this, I really don't know. So, if you don't mind, here are my questions ;
-In order to put a different Rom & Kernel onto my tablet, Do I need to have them both flashed through Odin at the same time for it to work?
-Does the kernel and rom have to be specifically compatible with eachother or can you essentially mix and match them?
- Will certain kernels work across different Android devices?
- Are the Custom Rom builds specific to 3g versions (Or would they work on the device as a whole regardless of 3g/wifi?)
- Will I need to put it into downloading mode to put them onto the tab, and recovery after through CWM to use them like I did for the rooting process?
Thanks in advance for your time!
Sam, Android Novice.
Flash in recovery.
Download the latest SetCPU from this thread:
http://forum.xda-developers.com/showthread.php?t=505419
Launch it, accept root allowance and select autodetect.
ondemand will be the default governor
To install kernel modules:
Use Winrar (windows) or tar with the z option and unpack lib-2636.4.tar.gz
Push any module you desire to /data/local/modules (this is created by the update.zip)
Then, insmod it (you can do this via adb, in a gscript, or on the device in terminal.
Note:
-If you want to enable usb charging:
adb shell echo 1 > /sys/class/power_supply/battery/force_usb_charging
To disable:
adb shell echo 0 > /sys/class/power_supply/battery/force_usb_charging
Flash in recovery.
Download the latest SetCPU from this thread:
http://forum.xda-developers.com/showthread.php?t=505419
Launch it, accept root allowance and select autodetect.
ondemand will be the default governor
http://droidbasement.com/db-blog/
@Sam,
I too am new to the SGT, and looking for a clear path to ICS.
I have done a boatload of reading and feel I have a pretty decent understanding of how to do this, I can give you some answers to your questions to the best of my knowledge, but would also greatly appreciate some outside clarification.
A: To put a new ROM on your device:
There are two ways to get zip files on your device. 1. Download a file on your computer and connect the tab with the usb cable and drag/drop it onto the root of the device. or 2. Download the file using the SGT directly from the site, in this case you will want to move the file from the download folder to the root of the sd so you can find the zip easily once in CWM
Download the ROM you would like to install, make sure it is for the same android version you are currently on. (don't use a HC 3.2 ROM if you are on HC 3.1) Back up your apps with Titanium Backup > Boot your device into CWM (this is NOT download mode, you will not be connected to a computer) > Make a nandroid backup of your current ROM setup, just in case something goes wrong, you will be able to go back into CWM and restore your device with this back up > next do all the appropriate wipes per the Dev's instructions. > Go to install zip > Choose zip > Navigate to the zip file you want to intall > Install zip >Reboot > Sign in and set up your device on your new ROM
A: Kernels: Some ROMS will already have a custom kernel built into the ROM. Some will use the STOCK kernel.
You may NOT mix and match kernels at will, make sure the kernel you want to use is compatible with the ROM you are using.
You can then flash the kernel in CWM through the install zip process.
I don't think you can use kernels across different devices, but I am not sure.
A: Odin: As I understand it, You will only use Odin to install different CWM Recoveries or to flash a stock ROM if for some reason you have borked your device and can't get to CWM through the power menu
My Questions for a path to ICS
Q: 1. I am running Galaxy Task 13.1 Rom with Pershoot kernel. In order to Flash ICS I need to be using the latest CWM 5.0.2.7 correct?
2. In order to flash the new recovery, do I need to revert back to the stock kernel? If so, can I use the stock kernel found in the second post of the Task thread and flash in CWM the same as when I did Pershoot's
3. Would I be better off just restoring my stock rooted nandroid, and then ODIN flash the CWM 5.0.2.7 to that and then Flash ICS from there.
4. Once on new recovery, I will not be able to restore any nandroids from previous version and should I then want to go back to Task, I will have to just flash the ROM as a fresh install and then create new nandroids to use from there on?
Thanks
D
dxh3378 said:
@Sam,
My Questions for a path to ICS
Q: 1. I am running Galaxy Task 13.1 Rom with Pershoot kernel. In order to Flash ICS I need to be using the latest CWM 5.0.2.7 correct?
2. In order to flash the new recovery, do I need to revert back to the stock kernel? If so, can I use the stock kernel found in the second post of the Task thread and flash in CWM the same as when I did Pershoot's
3. Would I be better off just restoring my stock rooted nandroid, and then ODIN flash the CWM 5.0.2.7 to that and then Flash ICS from there.
4. Once on new recovery, I will not be able to restore any nandroids from previous version and should I then want to go back to Task, I will have to just flash the ROM as a fresh install and then create new nandroids to use from there on?
Thanks
D
Click to expand...
Click to collapse
ok guys....flashing ICS can be done on top of anything...don't need root either.
1. Get the ICS and Gapps zip on the tablet
2. Flash CWM (unless you already have it)
3. wipe data
4. flash both
5. done
nothing really too complicated
no version requirements nothing.
hope this helps
as for nandroid things
yeah made a nandroid backup on whatever recovery you are on now..nothing will change after you flash ICS...you will still be able to restore anything.
To install kernel modules:
Use Winrar (windows) or tar with the z option and unpack lib-2636.4.tar.gz
Push any module you desire to /data/local/modules (this is created by the update.zip)
Then, insmod it (you can do this via adb, in a gscript, or on the device in terminal.
Note:
-If you want to enable usb charging:
adb shell echo 1 > /sys/class/power_supply/battery/force_usb_charging
To disable:
adb shell echo 0 > /sys/class/power_supply/battery/force_usb_charging
Click to expand...
Click to collapse
That stuff went right over my head, I imagine less jargon would be helpful too haha.
Can anyone point me to a kernel that i can use with galaxy task 14 custom rom that has cifs/nfs built in?
Ive searched around and can only find ics kernels, and i can safely say that flashing one of those via cwm doesnt work for task14!
Thanks, zip prefered if anyone has a kernel to hand, makes cwm easier!
geekyhawkes said:
Can anyone point me to a kernel that i can use with galaxy task 14 custom rom that has cifs/nfs built in?
Ive searched around and can only find ics kernels, and i can safely say that flashing one of those via cwm doesnt work for task14!
Thanks, zip prefered if anyone has a kernel to hand, makes cwm easier!
Click to expand...
Click to collapse
This is the last HC kernel from pershoot with cifs support: http://droidbasement.com/db-blog/?p=2479
Select the right version and download the modules (in the same link, lib-2636.4_ux_hc32.tar.gz)
Thanks, from what i can see i need to flash the zip, extract the tar file then adb in and insmod?
Im happy with the flashing and tar extraction, butbwhats the insmod about?
geekyhawkes said:
Thanks, from what i can see i need to flash the zip, extract the tar file then adb in and insmod?
Im happy with the flashing and tar extraction, butbwhats the insmod about?
Click to expand...
Click to collapse
You don't need to do it with adb, use a terminal (command line) application like this one: Android Terminal Emulator, grant root (in the terminal execute su) permissions and run something like this (change the path to fit your case):
Code:
insmod /system/lib/modules/cifs.ko
You'll have to execute the command to mount your share too.
Or an easier way is using CifsManager, in the options you can set the path to your module and you can mount the share. I'm not sure if this one also works with NFS, it says so, but I never tried it.
Other way is with a script, using Script Manager or load the module at boot
Sweet, worked a treat thanks, once i worked out i needed to make /system readwrite and not just read onky.
Thanks alot for your help, i dont understand why cifs isnt just built in from scratch with android really, but sorted now. Just my phone to sort next!
Edit: how to i get my digicam pictres to show in the android gallery?
They are in te followinndirectory : /sdcard/nas/digi cam/
I can browse them in astro fine, but skifta and gallery dont show them / the directory.
Cheers
You're welcome.
Try using something like Rescan SD Card! or Rescan Media (personally, I use the "SD refresh toggle" widget from Elixir 2 - Widgets)
Oddly none of the as card refreshing tools updates the gallery app to.show the pics off my nas? It's mounted correctly I can see the files ok in astro.
What have I missed?
Questions go in the Q&A section
I am trying to go back to stock ROM and use the Bares' Init.d Scripts Using Stock Kernel (V3).
I reflashed the stock GB ROM using flashtool, rooted and installed xrecovery 0.3. After that, I installed Bares' INIT-D-RUNNER-TWEAKS-V3.zip using xrecovery and rebooted. When ever I try to use wifi I get "Error" just below the toggle to turn it on and i does not work.
It seems like someone else had this problem, but Bares says tha wifi errors shouldn't happen, see:
http://forum.xda-developers.com/showthread.php?t=2174564&highlight=wifi
I tried reinstalling three times (install original ROM and after that apply the Init.d scripts) in an unlocked bootloader X10. I then relocked the boot loader and tried again and I still get wifi problems.
Anyone else having problems like this? Is there a work around?
Obs: I could not post in the original threas as I am a newbie here and I am not allowed to post in the development section.
pjssilva said:
I am trying to go back to stock ROM and use the Bares' Init.d Scripts Using Stock Kernel (V3).
I reflashed the stock GB ROM using flashtool, rooted and installed xrecovery 0.3. After that, I installed Bares' INIT-D-RUNNER-TWEAKS-V3.zip using xrecovery and rebooted. When ever I try to use wifi I get "Error" just below the toggle to turn it on and i does not work.
It seems like someone else had this problem, but Bares says tha wifi errors shouldn't happen, see:
http://forum.xda-developers.com/showthread.php?t=2174564&highlight=wifi
I tried reinstalling three times (install original ROM and after that apply the Init.d scripts) in an unlocked bootloader X10. I then relocked the boot loader and tried again and I still get wifi problems.
Anyone else having problems like this? Is there a work around?
Obs: I could not post in the original threas as I am a newbie here and I am not allowed to post in the development section.
Click to expand...
Click to collapse
Hi bro, we need to edit install-recovery.sh script inside zip to include wifi module, please refer to HERE.
So, please use this zip, just flash it through Xrecovery, then it should be fine.
FYI
Regards
It didn't work out
Bares said:
Hi bro, we need to edit install-recovery.sh script inside zip to include wifi module, please refer to HERE.
So, please use this zip, just flash it through Xrecovery, then it should be fine.
FYI
Regards
Click to expand...
Click to collapse
First, thanks Bares for ansewring fast. But I am sorry to say that I did not succeed. First, I tried to simply add the line
insmod /system/lib/modules/wifi.ko
in the middle of install-recovery.sh and it didn't work out. I thought the reason was that I did not add the wiki.ko file to /system/lib/modules in the generated zip and started to look for it. I found the following the stock wifi modules from here. I got the modules from the x10_gb_stock_wifi_modules.zip file and added them to my tweaked INIT.D zip but it didn't work out. Anything that I am missing?
pjssilva said:
First, thanks Bares for ansewring fast. But I am sorry to say that I did not succeed. First, I tried to simply add the line
insmod /system/lib/modules/wifi.ko
in the middle of install-recovery.sh and it didn't work out. I thought the reason was that I did not add the wiki.ko file to /system/lib/modules in the generated zip and started to look for it. I found the following the stock wifi modules from here. I got the modules from the x10_gb_stock_wifi_modules.zip file and added them to my tweaked INIT.D zip but it didn't work out. Anything that I am missing?
Click to expand...
Click to collapse
Hmmm..., this problem could be happened if the rom wasn't settled properly too.
So, please try these steps (exactly) :
- Revert back to stock and setup the phone.
- Root it with the latest Flashtool and choose SuperSU !!!
- Install Xrecovery and let the rom settled first !!!
- Check an everything including wifi !!!.
- If its all working good then flash my script (see the thread for the latest one) through xrecovery and dont get rush on the first 2~3 reboot.
- And check the result.
Regards
It still does not work
Bares said:
Hmmm..., this problem could be happened if the rom wasn't settled properly too.
So, please try these steps (exactly) :
- Revert back to stock and setup the phone.
- Root it with the latest Flashtool and choose SuperSU !!!
- Install Xrecovery and let the rom settled first !!!
- Check an everything including wifi !!!.
- If its all working good then flash my script (see the thread for the latest one) through xrecovery and dont get rush on the first 2~3 reboot.
- And check the result.
Regards
Click to expand...
Click to collapse
I tried as you suggested and it didn't work. I tried both with your V4 scripts and with my modified version to include the "insmod /system/lib/modules/wiki.ko". Both did not work after some time to settle the original ROM (with 3 reboots) and some time to settle the modified ROM (3 more reboots).
I have also tried your new STOCK-GB-MOD-RELOAD.zip update file, but it didn't work either.
One thing I noticed is that your original update files delete the wifi.ko module from the /system/lib/modules directory that exists in the stock ROM. I even copied wifi.ko to my computer and cried an small zip that can be flashed by xrecovery to restore that file, but it is not enough to get it working. I tried to read your INIT-D-RUNNER-TWEAKS-V4 to see what it was doing but I did not understand how it changes wifi (I could not even find out where wiki.ko wasw being deleted).
It is a really shame, as your new STOCK-GB-MOD-RELOAD.zip looks exactly as what I wanted.
Anything else I should try?
pjssilva said:
I tried as you suggested and it didn't work. I tried both with your V4 scripts and with my modified version to include the "insmod /system/lib/modules/wiki.ko". Both did not work after some time to settle the original ROM (with 3 reboots) and some time to settle the modified ROM (3 more reboots).
I have also tried your new STOCK-GB-MOD-RELOAD.zip update file, but it didn't work either.
One thing I noticed is that your original update files delete the wifi.ko module from the /system/lib/modules directory that exists in the stock ROM. I even copied wifi.ko to my computer and cried an small zip that can be flashed by xrecovery to restore that file, but it is not enough to get it working. I tried to read your INIT-D-RUNNER-TWEAKS-V4 to see what it was doing but I did not understand how it changes wifi (I could not even find out where wiki.ko wasw being deleted).
It is a really shame, as your new STOCK-GB-MOD-RELOAD.zip looks exactly as what I wanted.
Anything else I should try?
Click to expand...
Click to collapse
Hi bro,
The last options is by remove these 2 lines below from instal-recovery.sh script inside zip provided (STOCK-GB-MOD-RELOAD.zip) :
HTML:
#init.d runner
busybox run-parts /system/etc/init.d/
BUT, ... the problem is : you will lost init.d runner for Stock Kernel, and it cause all tweaks will not run for sure.
The result is the rom will feel a bit slower than it should be.
Note : To be honest, i'm little bit confusing here, because everything should be fine.
OR : Use custom kernel for Locked Bootloader ( Doomkernel V6 for Locked Bootloader).
OR :
Just simply unlock the bootloader (it's really safe, but you have to follow the proper procedure on this), the simply procedure is :
- Revert back to Stock Rom using PC Companion or SEUS or Flashtool (Download the latest Flashtool Version (see the thread about how to unlock for more detail info, read it carefully!!!)., and then unlock your bootloader using this Flashtool.
Note :
Don't assume if got doubt about this.
- Flash custom kernel using above Flashtool (DoomKernel V6 integrated Bootmanager V2 Auto Rooted by Championswimmer is my recommendation) , because it's using Original Sony's boot splash logo.
- Flash above zip (STOCK-GB-MOD-RELOAD.zip) through Xrecovery.
- Finally you have to flash wifi modul for above kernel (find it on DoomLord's Thread).
Hope this help
Regards
Intalling another kernel does not work...
Hi,
I had a version with a prestine Stock + STOCK-GB-MOD-RELOAD.zip[/B] through Xrecovery. And I installed championswimmer kernel on top of it (thinking it would restore wi-fi) and it didn't work. That is realluy strange. I am starting to fear that the problem is with my X10 (it has some odd behaviors, like it always become slow when using a Ferakernel).
I'll try your first suggestion (turn off init.d scripts) and let you know how it went here.
Anyhow, great thanks!
Improvement
pjssilva said:
Hi,
I had a version with a prestine Stock + STOCK-GB-MOD-RELOAD.zip[/B] through Xrecovery. And I installed championswimmer kernel on top of it (thinking it would restore wi-fi) and it didn't work. That is realluy strange. I am starting to fear that the problem is with my X10 (it has some odd behaviors, like it always become slow when using a Ferakernel).
I'll try your first suggestion (turn off init.d scripts) and let you know how it went here.
Anyhow, great thanks!
Click to expand...
Click to collapse
I tried to turn off init.d scripts and it didn't work!
It was getting into my nerves. So I decided to look inside your INIT-D-RUNNER-TWEAKS-V4.zip file to see if something was weird to me. I am an old Linux desktop user and it looked very strange a line in the update-script script inside META-INF/com/google/android:
delete_recursive SYSTEM:etc/init.d
This woudl delete the whole /etc/init.d directory, somthing that looks very dangerous from a desktop user. So I just commented it and created a new zip file (allowing the copy of your custom init.d scripts, just avoid the full deletion before hand). I was sure it would not work, but it did... Wifi is working after I install this new zip.
I plan now to take a close look at exactly what files are being deleted to find out what should remain in order to keep wifi working in my phone. I'll let you know when I get it right. Now I have to leave as real life is calling me!
I found a solution
I found the problem an the solution.
Just after installing the stock rom, rooting, and installing xrecovery, there is a single file in /system/etc/init.d. It is called 00modules (see attachment). It looks like it create symlinks from the currect kernel modules to /system/lib/modules. This file is essential to get wifi working in my X10.
Since Bare's mods, like STOCK-GB-MOD-RELOAD.zip, delete all the files in there I end up without wifi after installing them.
The solution is simple. Just add this file to STOCK-GB-MOD-RELOAD.zip in "system/etc/init.d". It will them be copied back after being erased. Wifi works and I get Bare's mod fully functional.
Thanks Bares fo your mod!
pjssilva said:
I found the problem an the solution.
Just after installing the stock rom, rooting, and installing xrecovery, there is a single file in /system/etc/init.d. It is called 00modules (see attachment). It looks like it create symlinks from the currect kernel modules to /system/lib/modules. This file is essential to get wifi working in my X10.
Since Bare's mods, like STOCK-GB-MOD-RELOAD.zip, delete all the files in there I end up without wifi after installing them.
The solution is simple. Just add this file to STOCK-GB-MOD-RELOAD.zip in "system/etc/init.d". It will them be copied back after being erased. Wifi works and I get Bare's mod fully functional.
Thanks Bares fo your mod!
Click to expand...
Click to collapse
Oooops, OMG i really really... forgot to include it, i though i was .
Really sorry, will update my script immediately, thanks you so much bro :good:.
Best Regards
[email protected]
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
pjssilva said:
I tried to turn off init.d scripts and it didn't work!
It was getting into my nerves. So I decided to look inside your INIT-D-RUNNER-TWEAKS-V4.zip file to see if something was weird to me. I am an old Linux desktop user and it looked very strange a line in the update-script script inside META-INF/com/google/android:
delete_recursive SYSTEM:etc/init.d
This woudl delete the whole /etc/init.d directory, somthing that looks very dangerous from a desktop user. So I just commented it and created a new zip file (allowing the copy of your custom init.d scripts, just avoid the full deletion before hand). I was sure it would not work, but it did... Wifi is working after I install this new zip.
I plan now to take a close look at exactly what files are being deleted to find out what should remain in order to keep wifi working in my phone. I'll let you know when I get it right. Now I have to leave as real life is calling me!
Click to expand...
Click to collapse
I create this line below :
delete_recursive SYSTEM:etc/init.d
Just to make sure no additional tweaks on init.d (and this is for users that don't want to fresh install the rom) , so the rom will 100% run with my files, just is't.
BTW, thanks a lot for the finding bro :good:. I have update my script to the FINAL one (see my thread), and it seem will be no more update after this one.
FYI
Best Regards