Database Users

[Script] AutoInstall new camera [Hastarin 8.5.1 + new cam libs]

Mods: If you think this should go in general section feel free to move it, thanks.
I built a script that will install the new camera (nexus based), it will replace all necessary files to get the camera working as well as hastarins 8.5.1 modules (to get wifi working and all) and finally liblights and libhtc_ril_wrapper (might be overkill, but it works)
Instructions: Unzip CamScript folder to SD Card (anywhere is fine) and then as su (adb shell or terminal emulator, anything you use to run bash scripts is ok) run cam_install.sh
Note: It will replace zImage in either /sdcard/HD2ONE or /sdcard/Android; it will not work if you have a kernel in a folder different to those so edit your startup.txt file if necessary.
Credit goes to hastarin for the kernel and camera files
-OCM
V1.5: Everything should work now, i've tested on stock HD2ONE_Latest. Backup versions of all modified files are saved in /data/cam_backups.

Good job
Sent from my HTC HD2

Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.

bobjbain said:
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
Click to expand...
Click to collapse
try chmod -R 777 /system/lib/*

bobjbain said:
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
Click to expand...
Click to collapse
Same problem here...i've tried your script on the HD2ONE 0.3.3 Rc2 version. I've followed all the instructions and now im stuck on the green HTC logo.....Can you please tell me how to Manually apply this script because i think it doesnt work properly....thanks

I don't think this fix is going to work with build that is based on cm6 .1 rc2 because it gets boot loops on the htc screen. I will still give this fix a try and report back....
Edit
Tried it and it did not work for me, black screen on the camera...

atoore said:
Those new builds that is based on cm6.1 rc2 wont work with any new kernels with the new drivers. I will try this fix and report back...
Click to expand...
Click to collapse
What do u mean??
ocm7 reported he succefully applied new camera drivers to the HD2ONE_latest build that is based on the cm6.1 rc2...

Any solutions????

Working on it, shouldnt take more than a few minutes

ocm7 said:
Working on it, shouldnt take more than a few minutes
Click to expand...
Click to collapse
Really thanks, anyway tomorrow (now its late night here) i'm going to reinstall the latest HD2ONE build and then applying your script again (still if you told me how to manually add all the stuff it would be better for me)

Uploaded the fixed version, worked on stock HD2ONE_Latest, so it *should* work on other builds but i cant guarantee this. If you're stuck on boot screen you can try running this new script and see if it works, if it doesnt replace system.ext2 with stock from your build then run the script. Sorry about the initial errors...

So, I used your 1.5 script and this time managed to reboot back into Android.
Everything seemed fine except that my camera still had a green tinge when used with the flash.
THEN I realised that I still had the root directory in the Android folder. So assumed/guessed that the libs were being oerwritten by those in the root folder.
So I renamed root to root_old, re-ran your script, rebooted.
Hung like a mule!!
Restoed original JDMS 1.5 system.ext2, rebooted fine.
Except now my accounts don't sync, my camera takes a picture then hangs
I will get it all back thanks to Titanium Backup
--
Looking at your script it's what I've always been doing to install new Kernels. The green tinge was there when I first tried Hasatrin 8.5.1
The only thing that you do different is include a build.prop file (which is wildly different from mine BTW).
So, my question, is it something in the build.prop that is stopping the grren tinge? If so, what??
TIA

as far as i know, this new lib file in CM or MIUI build make camcorder freeze..does it? or does it not?

I have a weird problem: when i'm in terminal emulator, then su (#), but when i try to type run cam_install.sh it says....run: not found......i think it doesnt recognize the run command..is it possibile??
Is there a way to avoid using this script and SIMPLY manually put all the needed files in the correct directories??
Thanks in advance!!!
P.S. I'm doing that in a HD2ONE stock unmodified latest build...

clockcycle4mobile said:
I have a weird problem: when i'm in terminal emulator, then su (#), but when i try to type run cam_install.sh it says....run: not found......i think it doesnt recognize the run command..is it possibile??
Is there a way to avoid using this script and SIMPLY manually put all the needed files in the correct directories??
Thanks in advance!!!
P.S. I'm doing that in a HD2ONE stock unmodified latest build...
Click to expand...
Click to collapse
Try
Code:
./cam_install.sh
there is no 'run' command in linux. Programs are executable and are run by just typing their name.
Of course the file has to be chmod'd to be executable too, but the ./ gets around that mostly.

It didn't work with HD2ONE-0.3.3.RC2
Just stuched in HTC welcome page

bobjbain said:
Try
Code:
./cam_install.sh
there is no 'run' command in linux. Programs are executable and are run by just typing their name.
Of course the file has to be chmod'd to be executable too, but the ./ gets around that mostly.
Click to expand...
Click to collapse
Thanks, i've done everything....android rebooted correctly but black screen on camera application...
ocm7 tell me how you made the camera application work properly....i tried and didn't work...

Mine says on every file "file not found" or something like that.

lesjaw said:
as far as i know, this new lib file in CM or MIUI build make camcorder freeze..does it? or does it not?
Click to expand...
Click to collapse
It does if you record on the highest setting (720p)
hhhawasly said:
It didn't work with HD2ONE-0.3.3.RC2
Just stuched in HTC welcome page
Click to expand...
Click to collapse
Worked perfectly for me on a stock system, are you sure all the files got copied right (no errors printed)?
clockcycle4mobile said:
Thanks, i've done everything....android rebooted correctly but black screen on camera application...
ocm7 tell me how you made the camera application work properly....i tried and didn't work...
Click to expand...
Click to collapse
Since everyone is having such a hard time getting it to work here are the manual instructions:
Replace your current kernel with hastarins 8.5.1
Replace Camera.apk in /system/app
Replace libcamera.so, liboemcamera.so, libOmxCore.so, libOmxVdec.so, libOmxVidEnc.so in /system/lib
Optional but recommended: replace lights.qsd8k.so in /system/lib/hw and rename or remove /system/lib/hw/lights.htcleo.so also replace libhtc_ril_wrapper.so in /system/lib
replace bcm4329.ko, tun.ko and cifs.ko in /system/lib/modules
place 99complete in /system/etc/init.d and chmod it to 755 (important!)
replace build.prop to fix green tint (I got it from the green tint fix thread and just replaced some lines to match CM6)
reboot
Also, i said these libs were nexus based so if your build is desire based it simply wont work

ocm7 said:
It does if you record on the highest setting (720p)
Worked perfectly for me on a stock system, are you sure all the files got copied right (no errors printed)?
Since everyone is having such a hard time getting it to work here are the manual instructions:
Replace your current kernel with hastarins 8.5.1
Replace Camera.apk in /system/app
Replace libcamera.so, liboemcamera.so, libOmxCore.so, libOmxVdec.so, libOmxVidEnc.so in /system/lib
Optional but recommended: replace lights.qsd8k.so in /system/lib/hw and rename or remove /system/lib/hw/lights.htcleo.so also replace libhtc_ril_wrapper.so in /system/lib
replace bcm4329.ko, tun.ko and cifs.ko in /system/lib/modules
place 99complete in /system/etc/init.d and chmod it to 755 (important!)
replace build.prop to fix green tint (I got it from the green tint fix thread and just replaced some lines to match CM6)
reboot
Also, i said these libs were nexus based so if your build is desire based it simply wont work
Click to expand...
Click to collapse
Well I've done every single step you wrote but still camera app is totally black after reboot.....this is very weird since i've used the same build you used (nexus based) but my result is so different from yours....

[Q] Some help with creating an Update.zip for my A7 please

I'd appreciate it if someone could give me some assistance. Basically the situation is that I wanted to get VPN working on the A7 which required tun.ko. I cross compiled the kernel and managed to get a tun.ko file and I added it to my device. Installing the module did not work, so I left it.
At some point my A7 shut off, and now it will not boot, it hangs at the ANDROID screen, before getting to the HC animation (dexmod 1.42). I am assuming at this point that my tun.ko is the issue so I created a patch update to remove the modules I had added to see if that would work.
Note: This patch is exactly the same as the ElocityMod 1.4.2 ad-hoc patch, I just changed the script actions and re-bundled.
The script only does this:
delete_recursive SYSTEM:lib/modules
delete SYSTEM:lib/tun.ko
I created the /system/lib/modules dir, so I know it exists, as does the /system/lib/tun.ko. When I try to run the update script I get the following error:
Installing Update
close from_child
E:Error in /sdcard/update.zip
(Status 6[1536])
Installation aborted.
I am trying not to flash back to the 1.4.2 as I have some investment and stupidly did not back-up before I started this venture. Any help would be appreciated.
Brad
As a side note, according to the /proc/config.gz on the tablet (kernel config) the TUN/TAP is compiled into the kernel, but not compiled as a module. For this reason I doubt VPN will work unless the apps can recognize the TUN device instead of failing because the module does not exist.

with specifics to an update script, the script desired should be as follows
Code:
run_program("/sbin/busybox", "mount", "-orw,remount","/system");
delete("/system/lib/tun.ko");
run_program("/sbin/busybox", "mount", "-oro,remount","/system");
you will need to remember to sign your update.zip after creation if you're not familiar with the process. searching on xda should turn up results for 'sign update.zip'.
i'd list the specific files and not do recursive deleting. though if introducing a kernel module caused you problems, i don't think it was merely copying/removing that had an effect, but wouldn't you have had to either issue an 'insmod' command manually or you added a call to that module using insmod added to the init.rc or a bash script. you need to remove that reference too if you did.
if your 'investment' is related to your /data folder (with your stored apps and app settings), you can use my cwm fakeflash recovery to backup and restore your /data contents (installed apps, and system settings) after a factory reset and reloading dexter's rom (using factory recovery).
alternative solutions; maybe if you were doing these kind of experiments you MIGHT have left the usb device setting on (for adb connectivity). if so, try to adb shell into the device to correct your problem by hand; type adb devices from a command prompt for fun to see if the device still lists (it did for me when softbricked once).
domito said:
I'd appreciate it if someone could give me some assistance. Basically the situation is that I wanted to get VPN working on the A7 which required tun.ko. I cross compiled the kernel and managed to get a tun.ko file and I added it to my device. Installing the module did not work, so I left it.
At some point my A7 shut off, and now it will not boot, it hangs at the ANDROID screen, before getting to the HC animation (dexmod 1.42). I am assuming at this point that my tun.ko is the issue so I created a patch update to remove the modules I had added to see if that would work.
Note: This patch is exactly the same as the ElocityMod 1.4.2 ad-hoc patch, I just changed the script actions and re-bundled.
The script only does this:
delete_recursive SYSTEM:lib/modules
delete SYSTEM:lib/tun.ko
I created the /system/lib/modules dir, so I know it exists, as does the /system/lib/tun.ko. When I try to run the update script I get the following error:
Installing Update
close from_child
E:Error in /sdcard/update.zip
(Status 6[1536])
Installation aborted.
I am trying not to flash back to the 1.4.2 as I have some investment and stupidly did not back-up before I started this venture. Any help would be appreciated.
Brad
As a side note, according to the /proc/config.gz on the tablet (kernel config) the TUN/TAP is compiled into the kernel, but not compiled as a module. For this reason I doubt VPN will work unless the apps can recognize the TUN device instead of failing because the module does not exist.
Click to expand...
Click to collapse

..alternatively alternatively i also did a update.zip of the latest factory rom that may assist with your issue, if the above solutions do not work. assuming your 'investment' isn't in the /system folder, it can format your /system folder and reinstall the /system files from the factory firmware with all correct permissions. a little examination of my update.zip could be used as a template for creating a similar one for dexter's rom, for these particular times when you'd like to re-do your /system folder and leave the rest of your partitions and data intact.
locatable, roundabout, from my twitter. same name as here.
oh. you could just write a script to execute a bash script (file.sh) thats got simple copy commands to copy your 'investment' to sdcard (/sdcard in recovery). that might be the simplest non creative approach that would allow you to continue on with a normal factory reset and reload of dexter's rom.
using bash scripts might also aid you in doing what you want without having to know or experiment with proper scripting syntax.
..oh, AND you could just edit dexter's rom update.zip to only install the system.img, and remove the rest of the files for installation, and DON"T do a factory reset..
that could help with restoring your system filesystem while leaving the rest of your data intact. didn't occur until this morning, that might be you EASIEST of the multiple suggestions listed.

Thanks for the response!
bestialbub said:
with specifics to an update script, the script desired should be as follows
Code:
run_program("/sbin/busybox", "mount", "-orw,remount","/system");
delete("/system/lib/tun.ko");
run_program("/sbin/busybox", "mount", "-oro,remount","/system");
Click to expand...
Click to collapse
This was actually what I did for my first try, with the same result.
bestialbub said:
you will need to remember to sign your update.zip after creation if you're not familiar with the process. searching on xda should turn up results for 'sign update.zip'.
Click to expand...
Click to collapse
I did not do this, I was not sure I had to.
bestialbub said:
i'd list the specific files and not do recursive deleting. though if introducing a kernel module caused you problems, i don't think it was merely copying/removing that had an effect, but wouldn't you have had to either issue an 'insmod' command manually or you added a call to that module using insmod added to the init.rc or a bash script. you need to remove that reference too if you did.
Click to expand...
Click to collapse
I did insmod it as well as modprobe, it gave me an error which was likely because (as I found later) the TUN is compiled into the kernel, which means a module could not possibly load.
bestialbub said:
if your 'investment' is related to your /data folder (with your stored apps and app settings), you can use my cwm fakeflash recovery to backup and restore your /data contents (installed apps, and system settings) after a factory reset and reloading dexter's rom (using factory recovery).
Click to expand...
Click to collapse
I'll have to take a look at that, I was no aware it existed.
bestialbub said:
alternative solutions; maybe if you were doing these kind of experiments you MIGHT have left the usb device setting on (for adb connectivity). if so, try to adb shell into the device to correct your problem by hand; type adb devices from a command prompt for fun to see if the device still lists (it did for me when softbricked once).
Click to expand...
Click to collapse
The issue with the A7 is that it's got USB host only which means I cannot connect it to my PC and adb it. This was a known issue before I bought the A7.

bestialbub said:
..alternatively alternatively i also did a update.zip of the latest factory rom that may assist with your issue, if the above solutions do not work. assuming your 'investment' isn't in the /system folder, it can format your /system folder and reinstall the /system files from the factory firmware with all correct permissions. a little examination of my update.zip could be used as a template for creating a similar one for dexter's rom, for these particular times when you'd like to re-do your /system folder and leave the rest of your partitions and data intact.
locatable, roundabout, from my twitter. same name as here.
oh. you could just write a script to execute a bash script (file.sh) thats got simple copy commands to copy your 'investment' to sdcard (/sdcard in recovery). that might be the simplest non creative approach that would allow you to continue on with a normal factory reset and reload of dexter's rom.
using bash scripts might also aid you in doing what you want without having to know or experiment with proper scripting syntax.
..oh, AND you could just edit dexter's rom update.zip to only install the system.img, and remove the rest of the files for installation, and DON"T do a factory reset..
that could help with restoring your system filesystem while leaving the rest of your data intact. didn't occur until this morning, that might be you EASIEST of the multiple suggestions listed.
Click to expand...
Click to collapse
In the end I went more heavy handed than all that and it worked out fine. I did this before I saw your response otherwise I would have tried to finesse it some more just for the fun of it.
I re-flashed with dexmod 1.41 but I did not reset or wipe anything first. Applying this over top got me booted again with all my apps. 1 quick 1.42 update (and annoying root FB upgrade) and I am back to pre-fail conditions. I backed up my stuff too.
Thanks again for all the useful tips. This type of event has happened a few times and my gut says I am getting some corruption on the NVRAM or something. Only time will tell.

adb connectivity works fine, the solution is buried in one of 5stronginos threads, maybe the cwm recovery one. google for USB_OTG.APK i think, its posted on xda w a download link.
..i also prepackage it in my firmware repack.. findable from my twitter.
Sent from my X10i using Tapatalk

bestialbub said:
adb connectivity works fine, the solution is buried in one of 5stronginos threads, maybe the cwm recovery one. google for USB_OTG.APK i think, its posted on xda w a download link.
..i also prepackage it in my firmware repack.. findable from my twitter.
Sent from my X10i using Tapatalk
Click to expand...
Click to collapse
I found this one, which looks right.
http://forum.xda-developers.com/showpost.php?p=12813894&postcount=36
I'll give it a shot. Thanks for the info.

[WINDOWS/ADB] (Busybox 1.19.4) Uncolored ls output! (compiled from source)

Hey!
I don't know if it has been posted before (and from what I can see in the "similar threads", it hasn't), but here it goes:
I've built, as my first ARM compilation, an uncolored ls output BusyBox (latest version, might I add) for you all .
Yes, I grew effin' tired of the whole garbage output when doing "ls" in busybox under Windows, and all of the solutions I saw in the interwebz (and XDA) were like, modify the CMD, use another command-line app (Console2 anyone?), put ANSI.SYS files on your path (Ewwww) and stuff like that. I had an out-of-the-box thought and said, hey, why don't I just fix the problem by recompiling busybox and setting --color as if it were --color=never.... always??
Well, I did, and here it goes. Enjoy.
It has been tested with my Nook Simple Touch, but YDMV (Your Device May Vary). I assume it could work in any, since I compiled it using codesourcery's ARM toolchain.
Take it easy on me though, I'm not very experienced in this ARM compiling stuff. If you guys are interested in the source, I'll post it. It's a small mod in coreutils/ls.c.
Enjoy

Hey, at least say thanks I wanna hear success stories and suggestions and stuff y'know! D: xD

can you make this flashable via cwm ?

I just figured out that I could replace the busybox link with one to toolbox to get rid of the color characters (ie. "ln /system/bin/toolbox /system/bin/ls) but I'll give this a try and if it works flawlessly, will include it in my ROM.

globula_neagra said:
can you make this flashable via cwm ?
Click to expand...
Click to collapse
Sure, give me this weekend to make a flashable update.zip file
Turge said:
I just figured out that I could replace the busybox link with one to toolbox to get rid of the color characters (ie. "ln /system/bin/toolbox /system/bin/ls) but I'll give this a try and if it works flawlessly, will include it in my ROM.
Click to expand...
Click to collapse
Hmm that's interesting, what does toolbox do in this case? is it somehow a stripped-down busybox of sorts?. Hehe, I'd love if you do use it though XD

Works on Micromax A70
Here is the flashable zip I made
Darkguy'sbusybox
If u get status 0 error while flashing then open the zip and go to this location
META-INF-->com-->google-->android and replace the update-binary with the one from any of your custom ROMs in same location
@darkguy2008
Good work
Add the flashable zip to OP

Thanks a lot mate! A very helpful contribution

Thanks buddy

Need help fixing Wifi in CM10.1

Hello.
As some of you know that I have ported CM10.1 from u8800pro to our device (u8800 non-pro).
However, there are three problems:
- no wifi
- no bluetooth (turns on but no discovery)
- no video recording
The first thing I am trying to fix is the Wifi, because that's what everyone is having problems with.
But, I cannot fix it alone. I have tried googling some solutions and have tried somethings myself, but still nothing.
Logcat says that the wifi 'Failed to Load Driver'
I think this is libhardware_legacy.so problem. I have even tried replacing that but then the phone doesn't fully boot up.
I need some solutions for this guys. I want help from developers to accomplish this task.
Thanks in advance.

This is indeed libhardware_legacy.so issue. libhardware_legacy.so loads the wifi modules.
In case of U8800+, it loads bcmxxx.ko module, and it will not work on U8800. For U8800, wifi module consists of two pieces - librasdioif.ko and wlan.ko (or libra.ko). Since there are changes to libhardware_legacy between JB and ICS, simply replacing won't work. I could send you my libhardware_legacy.so if you'd want. It's set up to load /system/lib/modules/librasdioif.ko and /system/lib/modules/wlan.ko. Also, when wifi is turned on, polling must be turned on for sdc3 (wifi sdio card).
I made my libhardware_legacy.so to report wifi.driver.status (maybe it's not correct) to report "loading" when it's loading wifi modules. From there, you can add an init.rc handler for that property "echo 1 > /sys/devices/platform/msm_sdcc.3/polling"
Please let me know if something is not clear.

Thanks
Blefish said:
This is indeed libhardware_legacy.so issue. libhardware_legacy.so loads the wifi modules.
In case of U8800+, it loads bcmxxx.ko module, and it will not work on U8800. For U8800, wifi module consists of two pieces - librasdioif.ko and wlan.ko (or libra.ko). Since there are changes to libhardware_legacy between JB and ICS, simply replacing won't work. I could send you my libhardware_legacy.so if you'd want. It's set up to load /system/lib/modules/librasdioif.ko and /system/lib/modules/wlan.ko. Also, when wifi is turned on, polling must be turned on for sdc3 (wifi sdio card).
I made my libhardware_legacy.so to report wifi.driver.status (maybe it's not correct) to report "loading" when it's loading wifi modules. From there, you can add an init.rc handler for that property "echo 1 > /sys/devices/platform/msm_sdcc.3/polling"
Please let me know if something is not clear.
Click to expand...
Click to collapse
Thanks for the reply Blefish. I was hoping that you would help.
I would be very pleased if you send me your libhardware_legacy.so
And while we're at it, can you please also answer this question:
the Bluetooth in the CM10.1 ROM turns on, but it isn't discovering devices and it is not even being discovered by other devices. Can you please explain to me what files are responsible for this so I can edit them? (or do I have to start a new thread for that?)
Thanks for the help. really appreciate it.

rqmok said:
I would be very pleased if you send me your libhardware_legacy.so
Click to expand...
Click to collapse
Alright, I added it in the attatchment. I built it upon the latest CM-10.1 source with these modifications.
Now, you need to add this init.rc handler:
Code:
on property:wlan.driver.status=loading
# When Wi-Fi driver starts loading, we will enable polling in SDC3.
write /sys/devices/platform/msm_sdcc.3/polling 1
I did not test this out myself, but it should work, let me know if it doesn't.
Note that this does not include MAC address, so you are likely to end up with 00:00:00:00:00:00 as MAC address. When I manage to fix my wifi, I will create a simple binary that will write it.
rqmok said:
the Bluetooth in the CM10.1 ROM turns on, but it isn't discovering devices and it is not even being discovered by other devices. Can you please explain to me what files are responsible for this so I can edit them?
Click to expand...
Click to collapse
Unfortunately I can't help you on this. I haven't even tried porting bluetooth yet.

Need some more help
Blefish said:
Now, you need to add this init.rc handler:
Code:
on property:wlan.driver.status=loading
# When Wi-Fi driver starts loading, we will enable polling in SDC3.
write /sys/devices/platform/msm_sdcc.3/polling 1
Click to expand...
Click to collapse
I'm kind of new to this android stuff. I can't find the file init.rc
Is it in boot.img?

rqmok said:
I'm kind of new to this android stuff. I can't find the file init.rc
Is it in boot.img?
Click to expand...
Click to collapse
Yes

rqmok said:
I'm kind of new to this android stuff. I can't find the file init.rc
Is it in boot.img?
Click to expand...
Click to collapse
It's in the boot.img, correct. You would need a boot.img unpacker, then you'd have to modify one of the init.huawei.rc or init.rc (does not matter) and add the handler I wrote in my previous post. Then you would have to repack it and boot it up.

rqmok said:
I'm kind of new to this android stuff. I can't find the file init.rc
Is it in boot.img?
Click to expand...
Click to collapse
Please report us if it's working. Thanks.

Of Course
Mlopik said:
Please report us if it's working. Thanks.
Click to expand...
Click to collapse
Yes, I will definitely report back if it works. It's just that I have a Chemistry assignment to finish first.

Help with unpacking boot.img
Hey.
I can't seem to be able to unpack boot.img
I tried the unpacking scripts, but some give me a permission denied error and some show no files at all after successfully extracting it.
Can one of you please help me with this?

I'm stuck so...
I am stuck at repacking the boot.img so I just added the libhardware_legacy.so and the lines in init.rc using Root Explorer in my phone. But the Wifi still doesn't turn on. Still unable to load wifi

Please help
I still don't want to give up trying to unpack and repack the boot.img
I have successfully unpacked the boot.img, but I can't see the files! The files are there, but I can't view them! Can anyone help me? I've tried googling the solution, but I couldn't find a solution! :crying:
I am using Ubuntu 11.10 64bit

Use terminal as superuser. Also set executable permission to your scripts: chmod -x "your script"
Sent from my U8800 using xda app-developers app

Is there any unpacking files that any of you can lend me?
I've tried heaps of them, but none of them seem to work.
Thanks
EDIT: Where can I download the source for CM10.1?

rqmok said:
I still don't want to give up trying to unpack and repack the boot.img
I have successfully unpacked the boot.img, but I can't see the files! The files are there, but I can't view them! Can anyone help me? I've tried googling the solution, but I couldn't find a solution! :crying:
I am using Ubuntu 11.10 64bit
Click to expand...
Click to collapse
If boot.img compiled in a Chineese computer,the ramdisk forces extract to / (root directory).

Thanks
forumber2 said:
If boot.img compiled in a Chineese computer,the ramdisk forces extract to / (root directory).
Click to expand...
Click to collapse
Hey! Thanks! I actually found the files to be under the root directory!
But I don't know which files belong to the boot.img! Is there a way I can put them in a folder when I extract boot.img? And when repacking, do I have to give reference to where I can see the files or where I originally tried to extract the files?

[GUIDE] official cm11 RIL on williams kernel V2

Hi guys,
Just a quick little guide on how to fix the wi-fi and bluetooth issues on the official cm11 nightlies!
You find the official cm11 a bit laggy? you thought it would be a great idea to install williams kernel V2? after installation you noticed that it runs so much better and are really happy with it till you notice that wi-fi and bluetooth aren't working? Well here is a simple fix for that!
Steps:
1: download these 2 files: https://www.mediafire.com/folder/4hs22pjkn03m6/CM11_Nightly_Modules_Wifi_&_Bluetooth (credit goes to @alcatraz999902)
2: navigate to system/lib/modules and delete wlan.ko and scsi_wait_scan.ko
3: copy the files you downloaded earlier (wlan.ko and scsi_wait_scan.ko) to system/lib/modules
4: change the permissions to rwrr:
A: you can use file explorers like es file explorer to change the perms (rwrr 644)
B: you can also open a terminal, mount your system as rw (mount -o rw,remount /system) and cd to /system/lib/modules then type these 2 commands:
chmod 644 wlan.ko
chmod 644 scsi_wait_scan.ko
5: reboot your device
6: Enjoy official cm nightlies with working wi-fi and bluetooth!

Wow many thanks, mate!! I didn't know what was happening to the wifi. Now I can even solve it.
By the way, when you update a nightly, you need to readjust options like in built kernel mpdecision or reinstall optimized qcom's and all that stuff?
Cheers!

It does not work CM11 Official

it must work, you did mistake somewhere

zepp40 said:
It does not work CM11 Official
Click to expand...
Click to collapse
It's actually work.
Read carefully what to do
Sent from me

I suppose that's not a fix for wpa problems?
(since a long time, wifi doesn't work on WPA in cyanogenmod... only work with wep or wpa2)
But anyway, thanks for sharing
PS: Saloperie de freeboxV5.

What about new NyakKernel? I tried it but it doesn't work. Official CM, latest nightly.

tnx so much
Sent from my Xperia SP using Tapatalk

nplezka said:
What about new NyakKernel? I tried it but it doesn't work. Official CM, latest nightly.
Click to expand...
Click to collapse
I think that kernel already has the correct modules
Sent from my Xperia SP using XDA Free mobile app

When I install CM11 with Williams Kernel, the blue screen appear, no boot.