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?
Related
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....
can anyone send me the names of the init.devicename.rc and the unvented.device.rc? they are located in the kernel ramdisk
alex1301 said:
can anyone send me the names of the init.devicename.rc and the unvented.device.rc? they are located in the kernel ramdisk
Click to expand...
Click to collapse
Hi, here are the contents of the folder:
http://i.imgur.com/bxbK3.png
And attached is latest boot.img (kernel 3.0.8 from dzo's Aurora ICS) and the decompressed files if you need that...
i am quite ready with the rom. only thing is i have this problem.
[email protected]:~/Desktop/BootScripts$ sudo perl repack-bootimg.pl /home/ubuntu/Desktop/BootScripts /home/ubuntu/ramdisk /home/ubuntu/Desktop
1891 blocks
sh: mkbootimg: not found
repacked boot image written at /home/ubuntu/ramdisk-repack.img
but there is no file when i repack the kernel
alex1301 said:
i am quite ready with the rom. only thing is i have this problem.
[email protected]:~/Desktop/BootScripts$ sudo perl repack-bootimg.pl /home/ubuntu/Desktop/BootScripts /home/ubuntu/ramdisk /home/ubuntu/Desktop
1891 blocks
sh: mkbootimg: not found
repacked boot image written at /home/ubuntu/ramdisk-repack.img
but there is no file when i repack the kernel
Click to expand...
Click to collapse
Can you post the un packed files? I could try to repack them
I think I know what the problem is, you need to have mkbootimg... Here it is, put it in /bin and then rerun the repack script
EDIT: for some reason, attachments are always corrupt... but here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=475249&d=1293574570
http://www.mediafire.com/?y5ur5lc4q7d5148
http://www.mediafire.com/?vl44nay131u8ofz
sent them please repacked back
alex1301 said:
http://www.mediafire.com/?y5ur5lc4q7d5148
http://www.mediafire.com/?vl44nay131u8ofz
sent them please repacked back
Click to expand...
Click to collapse
Here it is.
But your error was because you probably didn't have mkbootimg on your system
are you ready?
alex1301 said:
are you ready?
Click to expand...
Click to collapse
I've posted the boot.img right now
I hope there's nothing wrong with it... to repacked the files, I put all the files from your both zip files in one folder, then run repack-bootimg.pl script over boot.img-kernel as argument, is this correct?
yes man thanks. i will give you credits in the rom section.
do you know if i can use the updater script form aurora?
alex1301 said:
do you know if i can use the updater script form aurora?
Click to expand...
Click to collapse
I guess yes, the script, if I'm not wrong, only formats partitions and copies the ROM files to the appropriate locations and sets permissions... try using it, or post the ROM here and I'm sure someone can work it out if it doesn't work...
Cheers
Sent from my U8800
i will release it in a couple of minutes. so when the script is not working, someone other can fix it
have i also to replace the updater-binary?
I don't think that's needed, the binary I assume is the same for different ROMs, only the script changes... but I would to be sure good luck!
Sent from my U8800
i can't sign this bull**** apk
alex1301 said:
i can't sign this bull**** apk
Click to expand...
Click to collapse
What do you mean? I was hoping for a release today :-( good luck man...
Tomorrow I'll try posting from desire z... can you post a link for a guide? Thank you...
Sent from my U8800
Edit: bootloop, partitions are not mounting.
nagato.fm said:
I'm trying to port an X5PRO rom to regular X5 and facing an issue of unworking wi-fi and USB mass-storage. All data I have: it's all right with IMEI, wi-fi and bluetoth MAC's are missing, serial number is missing, wi-fi toggle in settings is inactive (I mean it can't be turned on and if I try to turn it on directly from wi-fi settings it says "an error occured" and goes inactive again), when I'm connecting my phone to computer and trying to turn on storage I get message of dismounting SD card and the storage stays turned off.
I've already tried to change the kernel (this ROM is running 3.0.8 PRO kernel and I've used Dzo's v5.0u17 kernel) and it haven't fixed my problems. Changing of /system/libs/hw/ to the Aurora's resulted in non-bootable rom.
Have you any ideas of how to solve it? Or is there any threads about x5pro to non-pro porting I could miss? (I've tried to google anything about problems with my port and about porting from U8800PRO and found... nothing)
Click to expand...
Click to collapse
I have no ideal to give you because i'm not a DEV, but in the whole 4rum, you can easy find out the solution to help you.
http://forum.xda-developers.com/showthread.php?t=1941239
Those so called tutorials are pretty much useless, they will help you get the base on, but no more.
So, since U8800+ has a different Wi-Fi, you should first replace /system/lib/libhardware_legacy.so, /system/bin/wpa_supplicant with the dzo ones. Then copy over the /system/lib/modules directory, it contains Wi-Fi modules needed.
If it does not work out, try to modify the init.huawei.rc or init.rc and replace service wpa_supplicant and related configs with dzo ones. Note that you will have to modify boot.img, because it contains the init files. So use a boot.img unpacker, modify it, then repack it again.
Try to get me the logs too .
Blefish said:
Those so called tutorials are pretty much useless, they will help you get the base on, but no more.
So, since U8800+ has a different Wi-Fi, you should first replace /system/lib/libhardware_legacy.so, /system/bin/wpa_supplicant with the dzo ones. Then copy over the /system/lib/modules directory, it contains Wi-Fi modules needed.
If it does not work out, try to modify the init.huawei.rc or init.rc and replace service wpa_supplicant and related configs with dzo ones. Note that you will have to modify boot.img, because it contains the init files. So use a boot.img unpacker, modify it, then repack it again.
Try to get me the logs too .
Click to expand...
Click to collapse
The problem is that I've changed the kernel using abootimg package in Ubuntu because none of the scripts for unpacking/repacking boot.img found on this forum worked for me, also I couldn't unpack ramdisk so I think I can't modify init.rc at this moment. I'll try to get some logs and do all that you've mentioned.
Also there is another problem: no mobile network at all. When I turn on the phone the indicator goes gray and nothing seems working (can't phone someone and etc.). When trying to change mobile operator via settings I get a VERY strange menu asking me for PIN code (I actually don't have one - I've disabled it years ago).
Also I need to ask for some tutorials or knowledge bases about how android works and how core parts of android work (I mean EVERYTHING I can get) because I actually don't know ANYTHING about android and there's no noob-friendly tutorials or FAQ's over the internet. I've checked xda-university and it didn't helped either.
Anyway thanks for your help, Blefish!
After following your instructions system hangs on boot. When first flashed it started to "updating android:setting applications..." and then it rebooted. Then it said "updating... 1 of 1" and another reboot. Seems like framework-res isn't starting because it hangs on bootanimation and hardware buttons lights are constantly flashing. Installing SDK now, will try to get some logs.
Try to do it step-by-step so first replace one thing, reboot, then try another. That will help us understand what makes the phone hang.
For modifying kernel or init.rc I attatched boot.img unpacker-repacker with README, check it out. I am not sure if you need a Linux box for it, but I use that tool and it works well.
MIUI-XJ (my ROM) is a ported u800pro ROM. But it is a gingerbread ROM.
First of all,you need change all init files in /system. You can found this files in system/etc (example;init.qcom.wifi.sh).And I think the mass stroage problem causing by init.qcom.usb.rc (It can found in boot.img) but I'm not sure.
You should change gralloc files for a better GPU performance. It can found in systen/lib/hw. I think You don't need change other hw files.
u8800 needs system/bin/netd - system/lib/modules/*(anything in this folder) - system/bin/wpa_supplicant - system/lib/liboem_rapi.so - system/lib/libreference-ril.so - system/lib/libhardware_legacy.so - system/etc/init.qcom.wifi.sh - system/etc/firmware/wlan/*(anything in this folder) for turn on WiFi
and also u8800 needs system/etc/init.qcom.bt.sh - system/bin/hci_qcomm_init - system/bin/qmuxd (I'm not sure about this file) - system/bin/sdptool - system/bin/hciattach for turn on BT
And also,you need change init.rc and init.huawei.rc files in boot.img for turn on WiFi and BT.
forumber2 said:
MIUI-XJ (my ROM) is a ported u800pro ROM. But it is a gingerbread ROM.
First of all,you need change all init files in /system. You can found this files in system/etc (example;init.qcom.wifi.sh).And I think the mass stroage problem causing by init.qcom.usb.rc (It can found in boot.img) but I'm not sure.
You should change gralloc files for a better GPU performance. It can found in systen/lib/hw. I think You don't need change other hw files.
u8800 needs system/bin/netd - system/lib/modules/*(anything in this folder) - system/bin/wpa_supplicant - system/lib/liboem_rapi.so - system/lib/libreference-ril.so - system/lib/libhardware_legacy.so - system/etc/init.qcom.wifi.sh - system/etc/firmware/wlan/*(anything in this folder) for turn on WiFi
and also u8800 needs system/etc/init.qcom.bt.sh - system/bin/hci_qcomm_init - system/bin/qmuxd (I'm not sure about this file) - system/bin/sdptool - system/bin/hciattach for turn on BT
And also,you need change init.rc and init.huawei.rc files in boot.img for turn on WiFi and BT.
Click to expand...
Click to collapse
Thanks a lot! Will try it all now!
Okey, now it's a bootloop on splash screen.
Edit: a bootloop was caused by some error in boot.img repack. Will try to repack it again now.
How to enable ADB when booting? On Aurora I could get kernel messages via ADB using adb shell cat /proc/kmsg. And now I really miss this feature.
Okey, great news! Wi-fi turned on, but the phone will fastreboot if I turn it off (framework crash I think) and wont turn on again until a full reboot. Also it isn't really working: no networks found.
No changes at all except Aurora kernel + setprop persist.sys.wifimac mac_param in terminal. After that wi-fi turned on, but even with that prop I have no wi-fi mac.
From that I understand all my problems are from some RIL or hardware libs that don't load or load with mistakes. So I need to know what exactly it can be and what libs are for what. Also I think it can be because of unedited init.rc's in ramdisk so I need to know what to edit in them. I've tried to look through them but I don't understand anything in it.
nagato.fm said:
Okey, great news! Wi-fi turned on, but the phone will fastreboot if I turn it off (framework crash I think) and wont turn on again until a full reboot. Also it isn't really working: no networks found.
No changes at all except Aurora kernel + setprop persist.sys.wifimac mac_param in terminal. After that wi-fi turned on, but even with that prop I have no wi-fi mac.
From that I understand all my problems are from some RIL or hardware libs that don't load or load with mistakes. So I need to know what exactly it can be and what libs are for what. Also I think it can be because of unedited init.rc's in ramdisk so I need to know what to edit in them. I've tried to look through them but I don't understand anything in it.
Click to expand...
Click to collapse
Which ROM are you fixing? Isn't CM10?
Nope, it's some desire z jb rom.
Code:
[email protected]:~# adb shell dmesg
- exec '/system/bin/sh' failed: No such file or directory (2) -
That's what I'm getting now. Already tried to fix this issue with some methods from google, no results. Even tried to adb-push bash from 4pda to system/bin and make symlinks, no results. Phone is in bootloop. Any ideas?
P.S.: sh is actually in both xbin and bin, so the problem is somewhere in the boot.img, right?
Have tried all kind of sorcery, still bootloops and exec '/system/bin/sh' failed: No such file or directory (2). Don't know why this is happening. Either /system mounts on boot in some wrong poing or init.rc is completely messed up. But I've checked everything connected to mounting partitions in all init files (except binaries) and gained nothing. I really need some explanation of what are these files for and what they do and what they MUST do.
If someone can give me answers or advices, please, do it now. Because all my ideas are over and I simply don't know now what to do.
EDIT: with aurora boot.img (no changes at all) results are the same except the message in terminal is now "/system/bin/sh: no such tool"
The system/bin/sh error is caused by not mounting /system properly. Check the init.rc files, it could also be in init.emmc.rc if it's a CM rom.
Find out where the on emmc-fs trigger is; if you can't find it, add it into one of the init.rc files.
Code:
on emmc-fs
# mount mmc partitions
wait /dev/block/mmcblk0p12
mount ext4 /dev/block/mmcblk0p12 /system rw barrier=1
wait /dev/block/mmcblk0p13
exec /system/bin/e2fsck -p /dev/block/mmcblk0p13
mount ext4 /dev/block/mmcblk0p13 /data nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p6 /cache nosuid nodev barrier=1
Not sure that I am following this thread properly. I am just starting out with android devel in Fedora. Have you recompiled the WLAN module?
eyeconic said:
Not sure that I am following this thread properly. I am just starting out with android devel in Fedora. Have you recompiled the WLAN module?
Click to expand...
Click to collapse
Nope, I have no proper skills for that, sorry.
I still need some information
Mostly completely rewrote init. files and still no results.
According to this: (http://forum.xda-developers.com/showpost.php?p=30458679&postcount=1)
The Android Boot Process
Bootloader – In HD2’s case, Magldr or cLK – loads the kernel based on how you have configured the phone.
Kernel – The kernel (zImage) is loaded into RAM along with an initial ramdisk (initrd.gz), which initializes various devices (IO, memory, GPU, etc.), interrupts, and mounts the root file system (/). After this, the first user-space process called init is started.
Init – this is a binary file that is contained within the initrd.gz. The init binary processes init.rc and init..rc , along with other .rc files that are called by these two .rc files. Some of the key functions (from this thread’s perspective) in the order of their initialization/ execution are:
The init process follows the instructions in the init.rc and init.xyz.rc files and creates empty directories including /data. It then mounts the storage devices (partitions in the internal NAND (MTD)) to these empty directories. The NAND partition for system is mounted to /system, followed by the partitions specified for data, cache, etc. The directories for dalvik-cache (/data/dalvik-cache) are also created by the init process after mounting the specified device to /data.
The init process then starts various services including adb, service manager, Volume Daemon (vold) for media like SD Card (FAT partition). Most importantly, the zygote service which initiates the Dalivk-Cache is loaded in this sequence.
As we all know, Android is based on Linux. The boot sequence described above is common for all Linux machines – until the zygote stage. Core Android file like core, framework, services, IME, policy, etc. are executed from the Dalvik-Cache and hence Initialization of the Dalvik Cache is pretty much where Android comes into the picture
The sysinit/ run-parts part, which runs scripts from the /system/etc/init.d later the Zygote stage. No matter how this is done, Android has already started loading by the time the boot process comes to executing scripts in /system/etc/init.d
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the error is in mounting nand partitions, but how can it past to starting adb when it fails on mounting system partitions? I don't understand this.
Hello,
Sorry, I have to post this workaround here because I'm new on xda and I can't post an answer on the development forums. So if someone see that, please post a link to this thread on PAC ROM or pink kernel topic
It seems there is a new file in the modules directory which is a symbolic link named wlan.ko. As an easy workaround, simply replace this file (/system/lib/modules/wlan.ko) by this one: /system/lib/modules/pronto/pronto_wlan.ko (move this file to the parent directory and rename it). Then reboot, you should have the WiFi working now
PS: I guess it's maybe better to modify the symlink or load the correct module but it's harder to write command lines with a smartphone
According to some people, this bug should be fixed now.
Doesn't work!
Sadly, doesn't work on PA/C-RoM.
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Mycroft-Dev said:
Sadly, doesn't work on PA/C-RoM.
Click to expand...
Click to collapse
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
matttbe said:
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
Well, Wi-Fi still refuses to work after removing the symlink!
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Cheers, mate!
Mycroft-Dev said:
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Click to expand...
Click to collapse
No :-/
Maybe you can try to reinstall the latest nightly version of your rom (released after March 20th -- I think it's the case for C-RoM), reboot and check if the WiFi is working. If yes, don't disable it now then reinstall the latest version of Pink kernel.
But if the WiFi is still not working, it's annoying... You can reformat /system where kernel modules are installed but I think it's automatically done when installing a rom. Maybe they are not using the latest version of the kernel?
Mycroft-Dev said:
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Click to expand...
Click to collapse
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Clarification
matttbe said:
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Click to expand...
Click to collapse
As in, I repacked the kernel, and then flashed it.
I'll try tweaking a bit here and there, and let you know how it goes.
And yes, I flashed the latest C-RoM.
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.
I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.
atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?
lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.
New version won't install on Kit Kat
PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.
atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt
Are extracted files accessible in file system? I can't find them
levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM
PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...
It seems that the image you want to unpack it is not an android image.
atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img
Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img