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?
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.
Hi, I am having a problem installing Urukdroid 1.6 to my Archos 70H (250gb hdd). I have downloaded the UrukDroid?_1.6-Install.rar several times but I cannot find the initramfs and kernel image to install on the internal memory. When I go to the UrukDroid?_1.6-Install.rar file there is nothing to extract. What am I doing wrong? My device has been rooted and has SDE.Any help is appreciated.
If you can't see anything in the rar File, then you are using the wrong software to decompress that archiv.
fzelle said:
If you can't see anything in the rar File, then you are using the wrong software to decompress that archiv.
Click to expand...
Click to collapse
Thanks. I found out what the problem was. When I was attempting to extract the files with the windows option to extract nothing happened. I used 7-Zip and then I could then see the files.
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
Hello,
I have changed my handset and now have a spare SGS2 (I9100) for learning about the kernel.
I'm running the following stock kernel & rom downloaded from sammobile.com ...
I9100XWLSW_I9100XEULS5_XEU.zip
In order to teach myself more, I am trying to create a replica of my current stock kernel...
3.0.31-1211311
I've downloaded/ familiarized myself with Android SDK, NDK (r8e) and Samsung Open Source (GT-I9100_JB_Opensource.zip).
I've got as far as making a kernel from the Samsung Source, but I've got the following differences:
1. New zImage size is approx 4Mb original zImage (in boot.img from I9100XWLSW_I9100XEULS5_XEU.zip) is approx 8Mb
2. New zImage also compiled 4 Modules in /lib/modules, there are six in the original zImage
Clearly the two are different and this is where I am stuck.
If I unpack the original zImage, I get what looks like a disk image, /data, /dev, /proc etc, if I unpack the new zImage I get two directories /dev & /root both are empty.
The difference in modules is also worrying, makes me think that the config in the original zImage is different to that supplied when I run 'make u1_defconfig'
I've sifted through a lot of forums, tuts and docs to get this far, any dev's help with some pointers? Is it possible to compare kernels?
Thanks,
YYo
**Please save yourself some time by reading the following**
Do not answer with 'I don't know but...'
'...have you tried kernel/ Rom xyz'
'...don't modify your kernel, you'll most likely brick your phone'
'...leave kernel development to people who know how to do it'
'...I am nigerian businessman who has just inherited $2,000,000...'
Bump,... anybody got any ideas how I can find out what was included when the original kernel was compiled (without going back to Samsung)?
YYo