Related
downloaded the gesture x8gesture-v004.zip and installed it,
downloaded update-floyo15-2011-03-26-rel-signed.zip and installed it,
checked all the relevant files (hw_config.sh- it had the necessary code in that file and the x8gesture.ko was in /system/lib/modules)
but it still didnt work. Am i missing something? i have baseband XXX015 and im using floyo. help?
dmcb123 said:
downloaded the gesture x8gesture-v004.zip and installed it,
downloaded update-floyo15-2011-03-26-rel-signed.zip and installed it,
checked all the relevant files (hw_config.sh- it had the necessary code in that file and the x8gesture.ko was in /system/lib/modules)
but it still didnt work. Am i missing something? i have baseband XXX015 and im using floyo. help?
Click to expand...
Click to collapse
Just read instructions again.. begin at the top.. maybe you missed something in the process.. ex. typo error.. because system work on me..
http://forum.xda-developers.com/showthread.php?t=1004740
I just re-read through the instructions and I have done it all correctly. I backed up a friends floyo (he has dualtouch) and restored it onto my phone and it still doesn't work
Sent from my X8 using XDA App
This happened to me too, using minicm rc1, Elelinux v3 and Nexus-x8 v2 also no luck to get it.
Minicm RC1 - using update-minicm2-2011-04-13-signed.zip (9.44 KB) after update,
no dualtouch, loose OC.
check with hw_config.sh, the code is at the bottom.
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
Install again 3 custom rom - minicm rc1, Elelinux v3 and Nexus-x8 v2
with factory reset
Manual Installation for the dualtouch and oc
I had added the code at the beginning
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
insmod /system/lib/modules/x8oc.ko # x8 overclock
As a result, Im only get the OC.
Edit: I had baseband 015, and i did adb shell command check also
adb shell
dmesg | grep X8Gesture
It returned a same output in the command prompt.
I had try with Multitouch Visualiser 2, always showing 1 touch
Add insmod line to the top of /system/bin/chargemon. I did that and it's working.
hi blagus, you mean add
insmod /system/lib/modules/x8gesture.ko at top of the line /system/bin/chargemon,
and how about the insmod /system/lib/modules/x8gesture.ko at the hw_config.sh,
leave it there or delete the command line?
lookingpost said:
hi blagus, you mean add
insmod /system/lib/modules/x8gesture.ko at top of the line /system/bin/chargemon,
and how about the insmod /system/lib/modules/x8gesture.ko at the hw_config.sh,
leave it there or delete the command line?
Click to expand...
Click to collapse
Remove insmod from hw_config and put it as the second line in chargemon.
In my case, chargemon looks like this:
Code:
#!/system/recovery/sh
insmod .../x8gesture.ko
insmod .../x8oc.ko
[...and so on...]
I think this is better method that hw_config because chargemon is the first thing executing on boot.
Hi blagus, my chargemon is start like this
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event 1 > /dev/keycheck&
sleep 3
Kill -9 $!
.... and so on ...
So i need to add like this ...
#!/system/bin/busybox sh
insmod /system/lib/modules/x8gesture.ko
insmod /system/lib/modules/x8oc.ko
/system/bin/charger
cat /dev/input/event 1 > /dev/keycheck&
sleep 3
Kill -9 $!
Edit: after test with Mr. Blagus method..the result still the same
OC worked but multitouch failed (I think is my hardware problem)
This didn't work for me either
Sent from my X8 using XDA App
I doubt that it's HW problem... I suggest you to flash baseband 015 again to make sure you have latest kernel.
blagus said:
I doubt that it's HW problem... I suggest you to flash baseband 015 again to make sure you have latest kernel.
Click to expand...
Click to collapse
this didnt work either :\ beginning to think it may well be a hw problem but i really dont understand how that could possibly be
No, it shouldn't be HW problem. When did you buy your phone?
ya..didnt work for me either, Im from malaysia, i also dont understand why will become like this..Now, only OC worked for me but i satisfied what i had now, actually the multitouch not very important for me, just curious to know what happened
About the phone last christmas
Sent from my X8 using XDA App
*I bought the phone last christmas
Sent from my X8 using XDA App
cool ill try it
dmcb123 said:
*I bought the phone last christmas
Sent from my X8 using XDA App
Click to expand...
Click to collapse
Me too, so it CAN'T be HW problem due to new revision... it's somewhere else.
First, chmod x8gesture to 777 (chmod 777 /path-to/x8gesture.ko)
If that fails...
Reflash stock FW (you can get it in my Mediafire folder), root, install xRecovery, then flash custom ROM, copy modules to /system/lib/modules and put insmod lines to chargemon.
blagus said:
Me too, so it CAN'T be HW problem due to new revision... it's somewhere else.
First, chmod x8gesture to 777 (chmod 777 /path-to/x8gesture.ko)
If that fails...
Reflash stock FW (you can get it in my Mediafire folder), root, install xRecovery, then flash custom ROM, copy modules to /system/lib/modules and put insmod lines to chargemon.
Click to expand...
Click to collapse
I had tried before using Root Explorer, tick all at the permission on x8gesture.ko, but dont know this step will be same as your method..will try later on. (Now im using minicm rc2,best rom atm only compass not work)
Edit: after chmod 777 - x8gesture.ko (rwxrwxrwx)
As a result - multitouch didint work, i lost root again (this is 2nd time, first time install floyo theme), now restore back RC2
Dont really want to go back to stock fw, ill wait a while for an update and then see about going back. Thanks anyway really appreciatedappreciated
Sent from my X8 using XDA App
To Blagus,
Reflash stock FW (From your Mediafire folder) and the Build 2.1.1.A.0.6 provided by mohakrastogi, is it the same method?
Testers no longer needed...turns out there is no improvement to the old version. Back to the drawing board.
Hello all,
I made a slight change to the PhoneWindowManager.smali and it seems to improve how quickly the orientation switches to portrait after a reboot (has been working immediately after first unlock for me). From my limited testing I also feel it will be less glitchy as sometimes weird things happened with the orientation in the current one. I am looking for a few others who would be willing to test and make sure everything is good.
The PhoneWindowManager.smali is attached
The instructions on how to install are here (Advanced users only)
Thanks for your help
Do you need to install the original portrait mod that you linked to to use this?
It's a smali script, it only relys on the original file to modify.
I'm willing to test for 191 if you make the edited policy.jar
marvin02 said:
Do you need to install the original portrait mod that you linked to to use this?
Click to expand...
Click to collapse
Don't need the original mod, just follow the same steps only use the smali file attached to this thread.
Sent from my Dell Streak 2.2.1 (339)
@jhotmann
I am stuck at the 10th point of ur instruction that is :
10. Put dexopt-wrapper into the correct folder with the correct permissions
> cd /system/bin/
> busybox cp /sdcard/dexopt-wrapper . (yes after dexopt-wrapper is a space and a period)
> busybox chmod 755 dexopt-wrapper
> cd /sdcard/
when i give 2 and 3rd command, it says
cant stst /sdcard/dexopt-wrapper: No such file or directory
Ok...........it was all done properly
But what result i got is . it now stucked in landscape completely and it looks really odd
waited but still its lanscape
yeah it seems to be still the same as the old one...the easiest way to get it out of being stuck in landscape is to open the camera app...Testers no longer needed as it is no improvement over the old version.
Testers
Hello jhotman
I'm sorry i saw this post too late, but if you need any testers in the future please PM me.
ATT 2.3.5 SystemUI
quickpanel_title_background.9 I Can not define
This is nice!
A few suggestions:
- Less icon spacing. Should fit at least 5 on the screen at once.
- No vibrate icon. It's unnecessary. Holding the power button works fine.
- Brightness control.
Thank you. Well done
Sent from my MB860 using Tapatalk
Hi can I install this on rooted locked atrix on 2.3.4!? I'm on UK retail. The thanks
Sent from my MB860 using XDA App
Wow. This is what I wanted.
Thank you
I'm on a rooted US ATT 2.3.4. How can I get this to install? I tried abd install, that didn't work...
--Q
EDIT: I think I figured it out. You have to go into /system/app and rename SystemUI.apk and SystemUI.odex to have .bak then copy the modified SystemUI.apk and then chmod 644 it. Rebooting now...will keep you posted!
EDIT2: Yep! Totally worked! GENIUS!! THANKS!
Do I really need to use adb or can do chmod by using some tool on phone?
Sent from my MB860 using XDA App
You can do all this with Root Explorer if you have it. Same idea.
I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot
Lack of ability to use a lot of smali. Or else can do more...
ein1002 said:
Lack of ability to use a lot of smali. Or else can do more...
Click to expand...
Click to collapse
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation
Shaydar said:
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation
Click to expand...
Click to collapse
I have no way to make the right moves Brightness：（
So I removed the BrightnessSettingButton
Leaving only the image resources
Hope someone can fix. And add this part.
sorry. My English is not good
Thanks, It does not matter anyway.
The Screen is so bright that I always set the brightness to its lowest.
malfuncion said:
I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot
Click to expand...
Click to collapse
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!
CyberPunk7t9 said:
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!
Click to expand...
Click to collapse
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk
Abu-7abash said:
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
It's just the latest Aura ROM (found in the development section) + this awesome quick panel MOD.
Aura is based on 2.3.4. I noticed that arabic fonts were connecting properly in the system+browser with Aura ROM as-is. No framework.jar or lebwebcore.is hacks are needed with that ROM.
Root+Battery % icons MOD+No carrier logo MOD+proper Arabic font connecting+this quick panel MOD is pretty much what I want now in my Atrix. Currently happy to have all that.
Not to mention a lot of other plus features Aura ROM adds.
Hi,
I was using this mod on 2.3.4 and it was great! Just upgraded to Android OS 2.3.6 (att build 4.5.141) and it just boot loops until I replace it back with the original. Is there any way to modify this to work on 2.3.6? Or, is there a version around that I'm not finding that will work on 2.3.6?
Thanks!
--Q
Hi all. If anyone is willing to help please assist me, im currently trying to upload cm 7 Morrison files for our beloved Ruth devices. I still haven't figured out how the 2nd init injector works yet.
For all charm users we can always branch the files and delete the MOTO.ROTATOR line for your devices.
If you have time, patients and sh¡t loads of guts please help or add links for me to checkout.
EVEYTHING IS APPRECIATED! :fistbump:
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Ok if anyone know of any other motorola developers please let me know.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
ruth(MB511) sensors in init.mapphone30_umts.rc
# sensor interface
chown compass compass /dev/lis331dlh --> not found
chmod 660 /dev/lis331dlh
chown compass compass /dev/kxtf9 --> found
chmod 660 /dev/kxtf9
chown compass compass /dev/akm8973 --> not found
chmod 660 /dev/akm8973
chown compass compass /dev/sfh7743 --> found
chmod 660 /dev/sfh7743
chown compass compass /dev/akm8973_dev --> found
chmod 660 /dev/akm8973_dev
chown compass compass /dev/akm8973_aot --> found
chmod 660 /dev/akm8973_aot
chown compass compass /dev/airc --> not found
chmod 660 /dev/airc
so ruth(MB511) sensors should be /dev/kxtf9, /dev/sfh7743,/dev/akm8973_dev, /dev/akm8973_aot
but Morrison sensors in libsensors/nusensors.h
#define AKM_DEVICE_NAME "/dev/akm8973_aot"
#define ACCEL_MODE_NAME "/sys/class/i2c-adapter/i2c-0/0-0018/mode"
#define CM_DEVICE_NAME "/dev/proximity"
#define LS_DEVICE_NAME "/dev"
#define LIS_DEVICE_NAME "/dev/lis331dlh"
I think porting Morrison maybe less suitable for ruth
Thanks phc, and yes I know its a long shot, I still haven't gotten to the lib files, let alone hardware. But morrison IS the closest port for us. All the other devices are to advanced for the device. Do a compare between the two, ram is almost identical, chips are close, gpu aswell. Only thing that isnt is screen size. Thanks for the lost, it will come in handy later.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Hi,
I used jordan-common and MagicDevTeam's MB508([h t t p s : / / github.com/MagicDevTeam) files,
and compiled eclair AOSP to check different files than create ruth device files.
My ROM VERSION:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
My ruth configure files: ruthconfigureforcm7.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqQUlWTWI3SURGU1U/edit)
https://github.com/phchshow/android_device_motorola_ruth
My unstable update file:v0.1.5.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqaXNzRVJDSU95Slk/edit)
V0.5.0.zip
can work:
battd[2013/03/14]
bluetooth
half work:
audio->media codec can't use.
[2013/03/19]solved some media codec running problem, but video recorder codec still has problem (even use low quality).
[2013/03/23]only mp3 and jpg codec is ok, orthers codec has problem, unknow how to solved...
sensors.
fmradio->FMRadioService.apk can't use, but can purchase "Spirit FM Radio Unlocked" to use.[2013/03/15]
camera->[2013/03/18]replace to use MB508's libcamera.so and libcameraservice.so. can take a picture, but media codec has some problem, so can't photograph.
wifi->[2013/03/23]dhcp has problem, but use command to execute is ok.
use mb508's bootmenu/2nd-init/init, solve setprop question, now wifi is OK.
but no softap beacuse can't compile tiap_drv.ko with 2.6.29 kernel.
ril->[2013/03/25]can call, but no sound, seems like audio codec problem.
not work:
battd->log say INIT BATTD SOCKET SERVER: failed. unknow how to solve. update[2013/03/14]:chmod cpcap permission
camera->used mb508's camera library, log say "mapped at 0x4103c000, not at 0xa7900000" can not load library
used ruth camera library, log say CAMERA HAL not support. unknow how to solve.
radio. unknow how to solve.
wifi->when process step 2, /system/bin/wlan_loader -f /system/etc/wifi/fw_wlan1271.bin -i /system/etc/wifi/tiwlan.ini -e /pds/wifi/nvs_map.bin
failed. [2013/03/16]get new question Failed to start supplicant daemon.unknow to solve.
[2013/03/23]gps->Failed to enable location provider
forget test:
fmradio, gps
phchshow said:
Hi,
I used jordan-common and MagicDevTeam's MB508([h t t p s : / / github.com/MagicDevTeam) files,
and compiled eclair AOSP to check different files than create ruth device files.
My ROM VERSION:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
My ruth configure files: ruthconfigureforcm7.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqQUlWTWI3SURGU1U/edit)
My unstable update file:v0.1.5.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqaXNzRVJDSU95Slk/edit)
can work:bluetooth
halt work:
audio->media codes can't use.
sensors.
not work:
battd->log say INIT BATTD SOCKET SERVER: failed. unknow how to solve.
camera->used mb508's camera library, log say "mapped at 0x4103c000, not at 0xa7900000" can not load library
used ruth camera library, log say CAMERA HAL not support. unknow how to solve.
radio. unknow how to solve.
wifi->when process step 2, /system/bin/wlan_loader -f /system/etc/wifi/fw_wlan1271.bin -i /system/etc/wifi/tiwlan.ini -e /pds/wifi/nvs_map.bin
failed. unknow to solve.
forget test:
fmradio, gps
Click to expand...
Click to collapse
How are you flashing the update.zip files, my phone doesnt seem to respond to any of the changes.
hsr0 said:
How are you flashing the update.zip files, my phone doesnt seem to respond to any of the changes.
Click to expand...
Click to collapse
you can use charm Big Bootstrapped Recovery Update to update.
or use bootmenu to update.
update:
if you want use bootmenu,
you can unzip my update zip (v0.1.5.zip).
WARNING: if step fails, may be need reinstall the system. BE CAREFUL.
1. remount system (root)
mount -o remount,rw / /system
2. push bootmenu files
adb push v0.1.5/system/bin/bootmenu /system/bin/
adb push v0.1.5/system/bootmenu /system/bootmenu
3. chmod files permisson (root)
chmod 0755 /system/bin/bootmenu
chmod 0755 /system/bootmenu/binary/*
chmod 0755 /system/bootmenu/script/*
chmod 0755 /system/bootmenu/recovery/sbin/*
4. change mot_boot_mode(original motorola file) (root)
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
5. edit mot_boot_mode (root) update(2013/02/08)
/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode
#!/system/bin/sh
export PATH=/system/bin:$PATH
/system/bin/bootmenu
mot_boot_mode.bin
6. chmod mot_boot_mode permission (root)
chmod 0755 /system/bin/mot_boot_mode
7. reboot and click click click(loop) "vol down" key until show bootmenu screen
Can you post just the bootmenu files?
I have already tried your steps twice but soft bricked the phone.
hsr0 said:
Can you post just the bootmenu files?
I have already tried your steps twice but soft bricked the phone.
Click to expand...
Click to collapse
OK. I re-installed system. And write script name mkbootmenu.sh
unzip bootmenuDIR.zip
adb push bootmenuDIR/bootmenu /sdcard/bootmenu
adb push bootmenuDIR/mkbootmenu.sh /sdcard
in phone side:
$su
#sh /sdcard/mkbootmenu.sh
#reboot
when MOTO LOGO click click click (loop) "VOL - " (VOL DOWN) until show bootmenu screen
NOTICE: only new system or never changed mot_boot_mode can run this script .
thank you very much, it worked!
However I still do not know why it did not run when I executed it although I did a fresh install with RSD lite.
Maybe because I used windows to create mot_boot_mode file, maybe some character issues occured.
but once again thank you!
Will check it in the morning, so far i've modded most of the make files for CM9 and my only worry is the framework.apk but so far so good :thumbup:
Almost forgot! The 2nd init and a modified boot kernel will be the biggest problems.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
https://github.com/plageran/ruth
Good job, man
My Flipout is waiting for a stable CM
ruth device cpu and gpu
As far as I know, flipout and charm have OMAP 3410 CPU inside, this CPU DOESN'T include GPU. Others like OMAP 3430 in Milestone 1 does include Imagination PowerVR SGX535 GPU.
Please check this location on your device with a root explorer app:
/system/lib/egl/
and in there you will find your gpu drivers, also most phones do have gpu's although it only helps the device a little bit.
I know my device has atleast 3 .so files in there and I think thats android drivers. I must just figure out if it should be recompiled for newer versions of android.
xinbada007 said:
As far as I know, flipout and charm have OMAP 3410 CPU inside, this CPU DOESN'T include GPU. Others like OMAP 3430 in Milestone 1 does include Imagination PowerVR SGX535 GPU.
Click to expand...
Click to collapse
Hijack
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
phchshow said:
you can use charm Big Bootstrapped Recovery Update to update.
or use bootmenu to update.
update:
if you want use bootmenu,
you can unzip my update zip (v0.1.5.zip).
WARNING: if step fails, may be need reinstall the system. BE CAREFUL.
1. remount system (root)
mount -o remount,rw / /system
2. push bootmenu files
adb push v0.1.5/system/bin/bootmenu /system/bin/
adb push v0.1.5/system/bootmenu /system/bootmenu
3. chmod files permisson (root)
chmod 0755 /system/bin/bootmenu
chmod 0755 /system/bootmenu/binary/*
chmod 0755 /system/bootmenu/script/*
chmod 0755 /system/bootmenu/recovery/sbin/*
4. change mot_boot_mode(original motorola file) (root)
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
"5. edit mot_boot_mode (root)
vi /system/bin/mot_boot_mode "
#!/system/bin/sh
export PATH=/system/bin:$PATH
/system/bin/bootmenu
mot_boot_mode.bin
6. chmod mot_boot_mode permission (root)
chmod 0755 /system/bin/mot_boot_mode
7. reboot and click click click(loop) "vol down" key until show bootmenu screen
Click to expand...
Click to collapse
plageran said:
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
Click to expand...
Click to collapse
He basically rewrote the boot script, so while booting up, it opens the bootmenu script and only then does it do a regular boot..
The normal 2nd init installer don't invoke the boot script in the same way I guess and hence it doesn't work.
Well now since bootmenu works, its like a torchlight in an otherwise dark tunnel.
Another point I want to make is that the flipout cm7 update given is in a bootloop. probably I need to change the files for basil (charm).
I think bootloop is audio device (libaudio.so) error. Maybe like when I use MB508's libcamera.so the message log show "mapped at .... " can't load library.
So should be use charm's libaudio.so to recompile CM7 sources. But maybe make some error, like media codec can't use.
hsr0 said:
He basically rewrote the boot script, so while booting up, it opens the bootmenu script and only then does it do a regular boot..
The normal 2nd init installer don't invoke the boot script in the same way I guess and hence it doesn't work.
Well now since bootmenu works, its like a torchlight in an otherwise dark tunnel.
Another point I want to make is that the flipout cm7 update given is in a bootloop. probably I need to change the files for basil (charm).
Click to expand...
Click to collapse
---------- Post added at 10:55 PM ---------- Previous post was at 10:34 PM ----------
The 5 step should be
"/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode", I forgot no install busybox no vi.
Defy use logwrapper to hijack, but flipout can't.
I think flipout processed init have not execute logwrapper, let we can't hijack logwrapper.
But mot_boot_mode executed.
So I rename mot_boot_mode to mot_boot_mode.bin and write new script name mot_boot_mode. Make bootmenu can execute.
And modify init.mapphone30_umts.rc
"exec /system/bin/mot_boot_mode" to "exec /system/bin/mot_boot_mode.bin", make 2nd-init can success execute init files.
In My uploaded bootmenuDIR.zip, the 2nd-init directory is modify for eclair to use.
You can modify eclair init files to test 2ndinit.
plageran said:
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
Click to expand...
Click to collapse
What I've learned so far is that most motorola's have the hijacked kernel from the original device, I'm not sure up to what level of Android os this works but if you dig deep enough. Its all almost the same to stock.
I hope you don't mind me using your scripts for my rom, this changed things big time.
Now to get my build machine up and running and to finish my LIB list for CM
edit: has anyone figured out the fingerprint system yet? I haven't found anything about it yet, whether it's generated or copied over.
phchshow said:
I think bootloop is audio device (libaudio.so) error. Maybe like when I use MB508's libcamera.so the message log show "mapped at .... " can't load library.
So should be use charm's libaudio.so to recompile CM7 sources. But maybe make some error, like media codec can't use.
---------- Post added at 10:55 PM ---------- Previous post was at 10:34 PM ----------
The 5 step should be
"/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode", I forgot no install busybox no vi.
Defy use logwrapper to hijack, but flipout can't.
I think flipout processed init have not execute logwrapper, let we can't hijack logwrapper.
But mot_boot_mode executed.
So I rename mot_boot_mode to mot_boot_mode.bin and write new script name mot_boot_mode. Make bootmenu can execute.
And modify init.mapphone30_umts.rc
"exec /system/bin/mot_boot_mode" to "exec /system/bin/mot_boot_mode.bin", make 2nd-init can success execute init files.
In My uploaded bootmenuDIR.zip, the 2nd-init directory is modify for eclair to use.
You can modify eclair init files to test 2ndinit.
Click to expand...
Click to collapse
hey dude, r you guys still working on flip/charm? any progress to share?
xinbada007 said:
hey dude, r you guys still working on flip/charm? any progress to share?
Click to expand...
Click to collapse
keep an eye on our github pages, i can only update monthly due to cost's. Still need to get and build my build machine lol!
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.