Related
I have a question about replacing system files (system accelerators) on-the-fly, the idea is to make a bat script which uses adb to do the following thing:
If Adrenaline shot is installed and want to change to thunderbolt:
First using the stop command so the phone freezes
then removing adrenaline shot:
- Replace with stock one:
* system/bin/app_process and system_server
* system/lib/libsqlite.so and libsqlite_jni.so
- Remove:
* system/etc/init.d/(all)
* system/etc/sysctl.conf
Then push thunderbolt:
* sdcard/bolt-scripts/(all)
* system/etc/init.d/(all)
* system/lib/libncurses.so
* system/xbin/sqlite3 and zip
* data/99supercharger.sh, local.prop, superchargeradj, superchargerminfree
Then reboot
Click to expand...
Click to collapse
If Thunderbolt is installed and want to change to Adrenaline Shot:
First using the stop command so the phone freezes
then removing thunderbolt:
- Remove:
* system/etc/init.d/(all)
* system/xbin/tune2fs, fsck.ext4 and zipalign
* data/99supercharger.sh, local.prop, superchargeradj, superchargerminfree
* sdcard/bolt_scripts/(all)
- Replace with stock one:
* system/bin/app_process and system_server
* system/lib/libsqlite.so, libsqlite_jni.so and libncurses.so
* system/xbin/sqlite3
* data/local.prop
Then push adrenaline shot:
* system/bin/app_process and system_server
* system/etc/init.d/(all)
* system/etc/sysctl.conf
* system/lib/libsqlite.so and libsqlite_jni.so
Then reboot
Click to expand...
Click to collapse
(made these lists according to updater-script)
Is it possible to do this without getting a brick? just like you flash themes in broodROM Configurator.
Another thing is, how do I add the remount script (running as root) of thunderbolt to scripts which load on boot (not init.d execution but when system is loaded)?
(the thing you normally do with script manager)
I don't like to double post. But can someone who knows it please reply?
The only command that I know which might help is invoked in adb: stop.
It literally freezes the whole phone but you can still access the whole filesystem over adb and replace files or remount. Obviously, when you do replace those files, you have no other option than to perform a reboot after you're done. Otherwise processes will crash and FC.
wintel_mac said:
The only command that I know which might help is invoked in adb: stop.
It literally freezes the whole phone but you can still access the whole filesystem over adb and replace files or remount. Obviously, when you do replace those files, you have no other option than to perform a reboot after you're done. Otherwise processes will crash and FC.
Click to expand...
Click to collapse
Ok thanks I had that in mind. so I will make a fully automated system accelerator switch script
I switched to a I9001 Galaxy S Plus, thus no more updates.
About
If You are like me - a fan of those monolithic install-and-forget scripts to optimize Your Ace at boot then this is for You.
As a base i took Slaid480's LagFreeV3 script and fixed some errors in it. Seeing that his script constantly overwrites earlier tweaks set up in itself i went on to consolidate it.
After that turned out succesful i combed through all the other scripts, snippets and tweaks floating around XDA (TurboBoostv8.5, BoostBuster, allinone Ram) and came up with my solution of a monolithic All-In-One script.
This here script contains all the useful tweaks for the Ace, was error checked, optimized and thoroughly tested on my personal Ace.
This is a continuation of the thread:
[SCRIPT] Slaid480's LagFree V3 script -fixed- -optimized-
http://forum.xda-developers.com/showthread.php?t=1486930&page=11
Required
* Ace S5830
* Root
* CM7.x
* Busybox (should already be there if rooted)
* Kernel supporting NOOP scheduler and SmartA**V2 governor
Script was tested on:
zImage-Mod v1.1 and v1.2 Kernel
http://forum.xda-developers.com/showthread.php?t=1292200
CM7.2 RC0 KANG by vo-1 deodexed with PDroid
http://forum.xda-developers.com/showthread.php?t=1462178
Instructions
- Make a nandroid of Your phone (just in case).
- Flash zip using CWM recovery.
- Reboot.
- Success.
An optional error logging function can be enabled by creating an empty
file named lagfree_debug in Your /data/ folder. Doing so will allow the
script to create a logfile /data/lagfree_debug.log during execution on
boot. This might help for finding issues on other ROMs and Kernels.
The script now contains some logic so when it does not succesfully run
to its end it will disable itself on the next boot. This will fix the "stuck
on android" issue.
To remove the script alltogether just flash the LagFreeV3_Rerolled_
Uninstaller.zip via CWM.
Credits
* SLAID480
* GadgetCheck
* Juwe11
* Salah Abouabdillah
* Einherjar Development Team
* CRANIUM ROM
* zacharias.maladroit
* voku1987
* [email protected]
* redmaner
* pikachu01
* fuss132
* LeonardLuangga
* Team Blockbuster
* tossan
* iandol
* _Roysten
* dragonnn
* XDA (for the help identifying the bugs)
* Everyone (i forgot but who put an effort into parts of this script)
Enjoy,
g_BonE
Changelog
0.17b - first release in XDA Development subforum, replaces older version --- REMOVED DUE TO setprop ISSUE!!!
0.23b - second release, replaces older version: setprop slot fix and bootloop (stuck on android) fix implemented. Thanks to tossan, iandol, _Roysten and dragonnn for the detective work and help getting this fixed.
Now, thank you! And why is it that we need CM7? Isn't this supposed to run on stock roms (rooted of course, and with cf-root kernel)?
WAIT so is this the combination of the given tweaks in OP or just fixed Lagfree? Kinda confusing O.O
original lagfreev3 runs great on stock with all permissions checked. Is this for stock also?
itasoulas said:
original lagfreev3 runs great on stock with all permissions checked. Is this for stock also?
Click to expand...
Click to collapse
if you consider "runs great" to mean that it fails to run properly because it has more bugs than the Amazon Jungle and thus it can run "great" anywhere because it actually fails to run everywhere!!!
lagfreev3 original is like homeopathy!
How do I install this over original lagfree?
Sent from my GT-S5830 using xda premium
iAreBeRtii said:
How do I install this over original lagfree?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Why do you want to install it over the original one? It was stated that it has too many bugs. Just delete the old one and flash this.
actually no need to uninstall, the installer of my script removes the original lagfreev3, turboboost and other scripts from init.d
and no, no need to install anything else besides this one its ALL INCLUDED
does this work on stock?
g_BonE said:
actually no need to uninstall, the installer of my script removes the original lagfreev3, turboboost and other scripts from init.d
and no, no need to install anything else besides this one its ALL INCLUDED
Click to expand...
Click to collapse
so, just install this script, and we're done?
Cool! Thanks gbone, you's a boss!
flashing your script makes my phone stuck on boot. i have LeWa rom installed. also, lagfreev3 and turboboostv8 is installed..
tomy2590 said:
flashing your script makes my phone stuck on boot.
Click to expand...
Click to collapse
Wait awhile and see if the desktop loads. I guess it takes time to rebuild the caches.
@g_BonE
You sholdn't clean up the caches (especially the *.apk files) on every reboot (->Dalvik Optimization).
The user can do it manually in CWM. This is only necessary before installing a custom rom or after modding some system files.
Otherwise: Great clean up work done! Hope all the script lovers appreciate it. Here are the line counts as a rough comparision:
Code:
[email protected]:~/Downloads/$ wc -l S9*
1130 S95Lagfree
305 S99_LFv3gB
1435 total
^^
@DooAce: I cant positively answer on the "working on stock" question as idont have a stock rom on my ace. i'd say it *should* if the rom has init.d support and the other requirements posted in the first post. anyone willing to give it a shot might do so using the debug feature and posting the logfile here so i can have a look.
@tossan: yes, i'll make the zipaligning a optional step, maybe using the same approach i took with the debug option (-soon-)
@tomy2590: and yes, first boot will take a while as zipaligning and database optimization takes a while. please be patient for a bit.
Doesn't work on Ace-of-Spades V1 - stuck on Android for over 20 minutes.
I have debug this script - don't know why but it's stuck on the setprop lines, removing it will repair this script. You can add on the begin of this script the command:
Code:
adbd &
And on the end:
Code:
killall adbd
Using this you can debug this script (via logcat) in real time and show on what he stops.
g_BonE said:
@tossan: yes, i'll make the zipaligning a optional step, maybe using the same approach i took with the debug option (-soon-)
Click to expand...
Click to collapse
I'm referring to this line at the end of the file, which will be executed on every phone reboot, making the dalvik cache unusable.
Code:
rm -f /data/dalvik-cache/*.apk
The zipaligning should be ok, because the code fragment only zipaligns new installed apks, if they're not already aligned.
~~
Phone rebooted succesfully afyer flash themyhrom advanced
g_BonE said:
actually no need to uninstall, the installer of my script removes the original lagfreev3, turboboost and other scripts from init.d
and no, no need to install anything else besides this one its ALL INCLUDED
Click to expand...
Click to collapse
Awesome! Thanks!
Sent from my GT-S5830 using xda premium
This will not be worked on any longer thanks to Huawei's incompetence. I'm glad my main phone isn't by them. I leave my 0.2 diff attached (which did make my phone faster FWIW - and has fsync() control. Not of use to me, but people who use a modified libsqlite would like it...). Feel free to apply it and see if you can somehow fix dhd.ko loading.
Hi,
Not one for names, so this shall be known as "OC kernel" This is built from the ICS U8800pro source that Huawei put out.
Install at your own risk; I take no responsibilty for any damage that may occur through the usage of this kernel.
Features:
ADB as root
Overclocking enabled (thanks to genokolar)
Undervolting interface added (from genokolar, who took it from a SE kernel modder somewhere) - I think SetXperia can use it
SIO I/O scheduler added
SmartassV2 cpufreq scheduler (AnDyX mod) - although I think ondemand does a bit better IMO
sysfs entry to turn off keypad lights (I wrote an applet for this some time back, I'll dig it out later)
Logcat is always enabled now as the ServiceMenu toggle doesn't work anymore
Minimum display backlight is set to 15, but I think Android needs a framework change to use it. You could try RootDim
Kernel actually builds (and Bluetooth works)
ZRAM (+ swap) support. ZRAM is optimized for Android (taken from Siyah kernel). I'll write up the instructions on enabling this later
CIFS as module
Extras:
Change schedulers and phone speed:
Use a tool like No Frills CPU or SetCPU.
Turn off button lights:
Install the ButtonLight widget and add it to your main screen. I've published the source before in another thread; seek it out if you're after its (bad) code.
It's buggy the first few times you run it, but works fine after that.
Dim screen to 14:
The minimum backlight level is now set to 15. RootDim from the Play Store lets you set it to that.
Mount Windows shares:
Grab CifsMounter and point it to the cifs.ko in /system/lib/modules. You may also need to insmod nls_utf8.ko and md4.ko.
Enable ZRAM (taken from Siyah kernel):
(Note I've not used ZRAM so I have nothing to say on its stability, good or bad)
Grab a BusyBox binary from somewhere
Run the following commands:
Code:
echo 90 > /proc/sys/vm/swappiness #You must set the swappiness high to ensure that the compressed RAM is accessed first!
echo $SIZE > /sys/devices/virtual/block/zram0/disksize #Set size to whatever you wish. 100MB is 104857600 = 100 * 1024 * 1024
busybox mkswap /dev/block/zram0
busybox swapon /dev/block/zram0
Dump the lines in install-recovery.sh if you want to be ZRAMMed every time you boot the phone (although in that case, make sure you have
Code:
busybox swapoff /dev/block/zram0 > /dev/null 2>&1 #Use > /dev/null 2>&1 for every busybox command in install-recovery.sh as it will discard any messages outputted
echo 1 > /sys/devices/virtual/block/zram0/reset
before the lines above)
Install:
Flash the attached ZIP in CWM recovery. You should backup your original boot.img and /system/lib/modules first
Source:
Take http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3NTU= and apply attached diff
at last..xaaxxaa!!but why with modules too???whats their use?
pikachukaki said:
at last..xaaxxaa!!but why with modules too???whats their use?
Click to expand...
Click to collapse
'cause I add a new module - cifs (used by CifsMounter if you want to mount Windows shares) - and because the modules that are originally in /system/lib/modules need to be replaced so that they can load with this kernel (I don't know what those modules do, but I'd rather play it safe)
qwerty12 said:
'cause I add a new module - cifs (used by CifsMounter if you want to mount Windows shares) - and because the modules that are originally in /system/lib/modules need to be replaced so that they can load with this kernel (I don't know what those modules do, but I'd rather play it safe)
Click to expand...
Click to collapse
Boot normally change io to sio and smartassv2...1500mhz lets check..good work..i envy you and i want your guide on compiling...xaaxax im off to bed!!
fps is locked!!xaaxax
pikachukaki said:
Boot normally change io to sio and smartassv2...1500mhz lets check..good work..i envy you and i want your guide on compiling...xaaxax im off to bed!!
fps is locked!!xaaxax
Click to expand...
Click to collapse
I'll write it up sometime - but bear in mind I'm not an expert at this
Regarding FPS: do the install-recovery.sh trick
Only thing I modify in initramfs is the ro.secure setting so that ADB can be ran as root
qwerty12 said:
I'll write it up sometime - but bear in mind I'm not an expert at this
Regarding FPS: do the install-recovery.sh trick
Only thing I modify in initramfs is the ro.secure setting so that ADB can be ran as root
Click to expand...
Click to collapse
You did a great job i couldnt even compile the kernel without changes!!you did great!!
the difference is obvious !!
Sent from my U8800Pro using xda premium
Pika When U add This Kernet To ur ROM?
As expected from qwerty12!
Great job!
I'll also request a guide on how to build the kernel like pika asked.
Hope you continue to improve the kernel! A thanks is simply not enough to thank you for your work, but thanks again
husen4u said:
Pika When U add This Kernet To ur ROM?
Click to expand...
Click to collapse
I wont!just d/w it and flash it!simple!
Sent from my U8800Pro using xda premium
Now what you suggest oc ics or kalo gb?
Sent from my U8800pro using xda app-developers app
husen4u said:
Now what you suggest oc ics or kalo gb?
Sent from my U8800pro using xda app-developers app
Click to expand...
Click to collapse
From now on i wont ever go back to GB ever again! if our luck changes and someone release cm9 i will forget what gb is!! there are some small bugs but the rom is usable for everyday!!
Moihack said:
As expected from qwerty12!
Great job!
Click to expand...
Click to collapse
Thank you
I'll also request a guide on how to build the kernel like pika asked.
Click to expand...
Click to collapse
Certainly, sir.
Hope you continue to improve the kernel! A thanks is simply not enough to thank you for your work, but thanks again
Click to expand...
Click to collapse
Unfortunately I won't be working on this anymore unless Huawei get back to my request for the source to the the dhd.ko module (which they may not have to comply with because the license for the module states "Unless you and Broadcom execute a separate written software license agreement governing use of this software" so the U8800pro version may not be under GPL). I made (well, found on the Internet) more optimizations but the Wi-Fi refuses to turn on because the dhd.ko module refuses to load. Only way I can get something working is to build the source that Huawei give or attempt to force other versions of the bcm source to load, but it's unlikely that would work.
--
Anyway, a small guide.
I used an x86_64 laptop running (X)ubuntu 12.04.1 to follow these steps. This page was a great resource.
Prerequisites:
A computer running GNU/Linux (a Mac should work in theory - the same toolchain we use is built for it, too, but I have no idea how OS X works)
git installed (apt-get install --no-install-recommends git-core is enough under Ubuntu)
sudo apt-get install flex bison gperf build-essential libncurses5-dev zlib1g-dev ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib abootimg
Getting ADB working
One of the best things to do is getting ADB set up, as you then have easy communication with the device. It's not essential but you'll just end up wasting time transferring files through other, longer means.
Grab the Linux platform tools ZIP from here: http://www.hariadi.org/android/manually-download-of-android-sdk-tools-and-sdk-platform-tools/. Extract the adb binary from the zip file, preferably to somewhere in your $PATH. chmod 755 it. chown, if necessary.
Next, open http://aur.archlinux.org/packages/an/android-udev/android-udev.tar.gz and, doing all this as root (sudo in Terminal etc.), place 51-android.rules in /lib/udev/rules.d/ (not the best place - but it works), chmod 644 it and chown root:root it.
Next, execute /usr/sbin/groupadd adbusers, followed by gpasswd -a USERNAME adbusers, USERNAME being the user you normally log on with.
Restart (while you can force Linux to see the new group through the, well, newgrp command udev will not "see" the new rule, despite how much you try with udevadm).
That should be ADB set up (give it a test, remembering to enable USB debugging mode on the phone first!).
On to preparing your workarea.
--
Create a new folder in your home folder and cd to it. This folder will house the prebuilt folder of toolchains and other stuff, and the kernel source in a folder of its own.
In this folder, execute git clone --depth 1 https://android.googlesource.com/platform/prebuilt.git and move onto the next step, since the download takes a while. That command grabs the prebuilt toolchain from Google using Git, but doesn't obtain a deep history for each file to make the download quicker.
Open http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3NTU= and save the source to your Downloads directory. After git has finished running, still in the folder with the "prebuilt" folder, execute tar jxf ~/Downloads/HUAWEI_U8800pro<tab - as in actually press tab> and you should have a kernel folder alongside the prebuilt one.
Building the kernel
cd to this new kernel folder.
First things first: make sure that Bluetooth is properly enabled by editing the Makefile. Find the line #ifeq ($(ENABLE_BTLA_VER30),true) and comment out every line in that section except for KBUILD_CFLAGS += -DHUAWEI_BT_BTLA_VER30 so you end up with this:
Code:
#/* < DTS2012020604357 zhangyun 20120206 begin */
# Add Huawei Marco for different BT chip
#ifeq ($(ENABLE_BTLA_VER30),true)
KBUILD_CFLAGS += -DHUAWEI_BT_BTLA_VER30
#endif
#ifeq ($(ENABLE_BLUEZ_VER30),true)
#KBUILD_CFLAGS += -DHUAWEI_BT_BLUEZ_VER30
#endif
#/* DTS2012020604357 zhangyun 20120206 end > */
Commenting out the offending code leaves you with a kernel that builds but a Bluetooth module that won't start up - the same also applies if you try to build with the other define.
You can also make things easier for yourself by replacing the following
Code:
ARCH ?= $(SUBARCH)
CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
with
Code:
ARCH ?= arm
CROSS_COMPILE ?= ../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
else you will have to put "ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" after "make" each time. Remember this as I'll be assuming that you went for the option to edit the Makefile. I also assume that the prebuilt folder is above the kernel one. Adjust CROSS_COMPILE if necessary.
The ARCH variable is self-explanatory, but the CROSS_COMPILE variable (and the toolchain that it's pointing to) need to be set because the standard GNU development tools that apt installs don't produce output that an ARM processor can understand. So you cross-compile: the tools are for the X86 architecture but produce ARM output. 4.4.3 is chosen because the stock kernel is compiled with GCC 4.4.3 (if you run "adb shell cat /proc/version" you'll see). The arm-eabi-4.4.3 folder is chosen over arm-linux-androideabi-4.4.x because it specifies that magic "3" (I know, bad way to decide but it works), and over i686-android-linux-4.4.3 because we don't want to produce code for the PC.
Get the current configuration in use by the stock kernel (as that's a good point to start from - a known working configuration): http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source#Configure_the_Build
I'd also recommend placing a copy of .config as arch/arm/configs/<your funky name here> so that if .config gets deleted (make clean etc.) you can run make <the name you gave to the file in arch/arm/configs> and have .config come back again.
(cp arch/arm/configs/<the name you gave to the file> .config if you didn't modify the Makefile to specify the ARM arch.)
Run make oldconfig (not always necessary - generally it's invoked if you've applied a patch that introduces a new config option and the option then needs to go into your .config. Run make menuconfig afterwards and customize away.
When you're done, run make -jX - X as in the number of cores you have + 1. So, in my case, with a quad-core processor and HyperThreading enabled on all of them, "make -j9" works for me. If the compile went OK, you'll be left with a message saying that arch/arm/boot/zImage is ready. If not, run "make" without the -jX argument and make should stop where the error occurs. Have fun fixing the error!
Assuming that you have a new, shiny zImage, it's now time to put it into your boot.img.
Updating your boot.img:
Google have tools for this purpose but I've never used them so I don't know how they work. abootimg works fine for this, however.
Pull the current boot.img off your phone: adb pull /.cust_backup/image/boot.img.. I'd recommend creating a backup somewhere.
Create a new directory to store the boot.img in on your computer and run abootimg -x boot.img (if you had fun enabling every option in the kernel, you'll see why I'm telling you to use the -x option first rather than directly use the -u option). Now run abootimg -u boot.img -k <path to your newly built zImage>.
If this succeeds, yay! If not and you're told it's too big for the boot image, then don't worry. Take the size it's saying that the zImage is and convert that number into hex. Edit bootimg.cfg and change the value of the bootsize setting into the number you just converted into hex. We'll now repack again, but this time running abootimg -u boot.img -f bootimg.cfg -k <path to your newly built zImage>. This should work.
Sending the boot.img to the phone
If your ADB is already running as root, you can do the following to upload the new bootimg:
Code:
adb shell mount -o remount,rw /.cust_backup
adb push boot.img /.cust_backup/image/
adb reboot
If not, just reboot into pink screen mode and copy and paste.
Check System Settings and the version number should've changed. Congratulations!
Extras
Installing the modules:
OK, so you decided to build parts of the kernel as a module and you want to actually, y'know, have the modules present on the device. After building the kernel, execute:
make INSTALL_MOD_STRIP=1 modules_install INSTALL_MOD_PATH=<any folder name here>
If you look in that folder, you'll find the modules neatly wrapped up in folders, along with other text files. These text files are useless on a stock ROM because there's no modprobe - you need BusyBox for that. And since we don't want to have them seperated in folders (this is how the stock kernel does it), the files would be wrong, anyway. If you want to use modprobe and have BusyBox installed, you can run depmod on the phone after transferring the modules.
To get the modules into one folder make the directory "modules" in a folder higher-up to where the modules are stored, and then run for i in `find . | grep ko`; do mv "$i" ../modules/; done to move them into that folder.
At this point, I'd just recommend using my OC_Kernel.zip and replacing the modules in that. Or you can adb push them over to the /system/lib/modules folder (after issuing an "adb remount" - assuming that ADB is running as root in the first place).
Making ADB run as root:
As root on your computer, (we want to preserve permissions) use abootimg to split the boot image and extract the contents of the initrd:
abootimg -x boot.img && mkdir newramdisk && cd newramdisk && zcat ../initrd.img | cpio -i --no-absolute-filenames (--no-absolute-filenames is important! I trashed a Ubuntu install by leaving it out - the initrd contains ARM binaries of core Linux programs and if the initrd.img contains an absolute path of "/" then these files will get placed in /)
Make any changes you desire to the initrd. To have adb run as root, just edit /default.prop and set ro.secure to 0. Make sure that the editor you used didn't leave any backup files.
When you're done, run find . -print | cpio -o -H newc | gzip -n -9 > ../initrd.img and this will put the modified initrd folder back into initrd.img.
After that run cd .. ; abootimg -u boot.img -r initrd.img to actually put the initrd.img back into the boot.img.
If you run into a space error, you can do one of three things:
if you only made a single change (like enabling ADB), check to see that there is no backup file (default.prop~) littered about
you can remove the lengthy comments and copyright notices from the files to make space
you can use the trick we used earlier with abootimg to increase the size number in bootimg.cfg for the initrd
Overclocking:
Just look at the acpuclock C file (and possibly relevant cpufreq changes - but I can't remember) in my "OC kernel" diff. Make sure that the option in the kernel config is selected to limit the speeds to the U8800pro's native 1GHz, otherwise the phone will boot at 2GHz!
Rebuilding the Wi-Fi module:
I hope to be able to write this one since it's apparently needed in some cases, but it depends on if Huawei come through
any idea about this error?
drivers/mfd/pmic8058.c:327: error: rtc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:327: error: rtc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:241: error: othc0_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:241: error: othc0_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:250: error: othc1_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:250: error: othc1_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:261: error: othc2_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:261: error: othc2_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:183: error: misc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:183: error: misc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:210: error: thermal_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:210: error: thermal_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:270: error: batt_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:270: error: batt_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:152: error: pm8058_charger_resources causes a section type conflict
drivers/mfd/pmic8058.c:152: error: pm8058_charger_resources causes a section type conflict
matteof93 said:
any idea about this error?
drivers/mfd/pmic8058.c:327: error: rtc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:327: error: rtc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:241: error: othc0_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:241: error: othc0_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:250: error: othc1_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:250: error: othc1_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:261: error: othc2_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:261: error: othc2_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:183: error: misc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:183: error: misc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:210: error: thermal_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:210: error: thermal_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:270: error: batt_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:270: error: batt_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:152: error: pm8058_charger_resources causes a section type conflict
drivers/mfd/pmic8058.c:152: error: pm8058_charger_resources causes a section type conflict
Click to expand...
Click to collapse
Honestly, I have no idea. What toolchain are you using and where was your .config obtained from? Even when the Bluetooth thing was giving me errors, I never once saw that
same toolchain you have used. i have tried with ubuntu 12.04 x64 and ubuntu 10.04 x86 but same problem.....i have obtained my config from my phone using adb command
matteof93 said:
same toolchain you have used. i have tried with ubuntu 12.04 x64 and ubuntu 10.04 x86 but same problem.....i have obtained my config from my phone using adb command
Click to expand...
Click to collapse
I don't know why the same toolchain works on my laptop but not yours :\
Someone with a similar problem (same?) solved it by using an older toolchain: http://forum.xda-developers.com/showpost.php?p=27294383&postcount=7157
thanks thanks thanks.....i saw that post this morning but i did not noticed the post with the solution
UPDATE: NOW KERNEL COMPILED CORRECTLY....this means that tomorrow i know what to do
ZRAM (+ swap) support. ZRAM is optimized for Android (taken from Siyah kernel). I'll write up the instructions on enabling this later
qwerty your owning us some instructions!!xaaxxa
pikachukaki said:
qwerty your owning us some instructions!!xaaxxa
Click to expand...
Click to collapse
Done, check the first post
I also won't be working on this. My email (which does clearly state what I want, even if it's long-winded):
Dear Sir/Madam,
I recently built a kernel for my U8800pro from your sources and it
works fine, except that the Wi-Fi will not start because the dhd.ko
module that comes with the B928 firmware refuses to load into my
modified kernel. After looking around, the bcm4329 source is what I
need to build (usually distributed outside of the kernel); however, it
seems that the U8800pro uses a customized version. After looking at
the strings of the dhd.ko on the B928 firmware, I have seen many
strings that are present in that dhd.ko binary do not appear in:
* bcm_4.218.248.6_7x25_wifi_driver.tar from the Huawei Device website,
despite it having the same version number
* the bcm4329 source in the Qualcomm CodeAurora Git repository
* the bcm4329 source on the NyVIDIA Tegra Git repository
Furthermore, the strings also do not appear in the ICS kernel nor the
Gingerbread one. I can only conclude that Huawei have their own
specialized version of the bcm4329 4.218.248.6 source for the U8800pro
that is distributed outside the kernel. I understand that Qualcomm
allow the option to let the vendor arrange to have the code
distributed under a different license provided that the vendor makes
an agreement beforehand with Qualcomm. Otherwise it becomes GPLed by
default. If Huawei chose to make an agreement, then I have no right to
ask. However, I believe it is still licensed under the GPL for two
reasons:
* Running modinfo on the dhd.ko from the B928 firmware says this:
"license: GPL v2
* Both bcm_4.218.248.6_7x25_wifi_driver.tar.gz and
[S7][SoftWare]S7_Broadcom_BCM4329_4.218.205.0_Open_Source are under
the GPL
I would like to request the source code, please, of the bcm4329
4.218.248.6 source that is modified for the U8800pro if the code is
under the GPL
Best regards
Click to expand...
Click to collapse
was met with the following generic response:
Dear Customer,
Thank you for contacting Huawei device.
This is our website link http://www.huaweidevice.com/worldwide/searchResult.
do?method=execute&searchString=U8800pro where you can download the secure
code for U8800pro to you.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.
Click to expand...
Click to collapse
Since my U8800pro is not my main phone anymore, I do not have the energy to fight. Nor do I want to work on Huawei's kernel, where you have to be careful about what you change or the Wi-Fi module won't load (and Huawei won't give you the source - which they should do since I'm sure it's under GPL). matteof93 will most likely produce something better or when everyone starts producing their own kernels and make enough improvements to be hit with the same issue as I, they'll start to get more emails and listen
@qwerty at the last command it said that device is busy...also is there any way that you can make it for init.d so it will be easier??thx!!
OS X Build Set Up 1.2 - By Kyle Frost (frostincredible)
So you want to build AOKP or CM10.1 on OS X? Well worry no longer my friends,
it is about to get a whole lot easier. Why is that? Because this script I've written will do pretty
much everything for you, from creating the case sensitive DMG to installing the required files,
to setting up all the folders. The best part? It also will initialize the AOKP or CM repo (depending
on your choice) and you can also build them straight from the script! How fantastic is that?!
Simply read on to see how! Make sure to follow all the instructions (there aren't many)!
Follow these steps:
Go here and download OS X Build Set Up 1.2 (OSX_Setup-1.2.zip) - DOWNLOAD
Place the ZIP file on your Desktop.
Extract the ZIP to your Desktop.
Here comes the only tricky part. Open the file located at OSX_Setup/scripts/advanced_scripts/build_cm or build_aokp, whichever you're going to build.
Find this line -
Code:
# BELOW IS THE ONLY LINE YOU SHOULD BE EDITING. REPLACE *YOUR DEVICE* WHITH YOUR DEVICE'S CODE NAME. EX - NEXUS 7 = "grouper"
Just below that, edit this line with the instructions in the one I just posted -
Code:
cp /Volumes/Android/OUT/target/product/*YOUR DEVICE*/aokp_*YOUR DEVICE*-ota-eng.$ME.zip /Volumes/Android/Builds/AOKP_$ME.$NOW.zip
IT IS IMPORTANT THAT YOU DON'T EDIT ANYTHING ELSE.
Open your favorite Terminal application (the default on is Terminal located at /Applications/Utilities/Terminal).
cd to the OSX_Setup folder on your Desktop.
Code:
cd /Users/YOUR NAME/OSX_Setup
Run the following -
Code:
./runme
After running this, you will be presented with the following menu -
Code:
============================================================
OS X Build Set Up 1.2 - by Kyle Frost
============================================================
---Main Menu---
1 - Create DMG
2 - Install required files (MUST install MacPorts first)
MacPorts available free at www.macports.org
3 - Set up folders
WARNING: DO NOT RUN ADVANCED MENU UNTIL
YOU HAVE RUN ALL 3 ABOVE, OR HAVE DONE
THEM ALL MANUALLY. THANK YOU.
0 - Advanced Menu
x - Exit
Enter option:
As you can see, you need to go here and install MacPorts before proceeding - MacPorts
After installing MacPorts you can go ahead and run everything.
Create DMG will give you the options of creating a 25GB, 30GB, 40GB, 50GB, or 60GB DMG. 25GB is the lowest recommended by the Android Team.
Install required files will simply do just that, it will install the files needed as specified in the AOSP documents. This can take a while, so go take a nap while it runs.
Set up folders will give you the option of setting up the folders for AOKP or CM10.1. Simply choose which you want and the folders will be created.
Choosing Advanced Menu will give you this -
Code:
============================================================
OS X Build Set Up 1.2 - by Kyle Frost
============================================================
---Advanced Menu---
MUST INSTALL XCODE BEFORE BUILDING!
XCODE IS FREE IN THE MAC APP STORE!
1 - Initialize AOKP Repo
2 - Initialize CM10.1 Repo
When building, it will give you a list
of devices. Enter the number for your device
configuration and the build will continue.
It will take a while the first time, as the
source must first completely download.
3 - Build AOKP
4 - Build CM10.1
Note: When the build is complete, you can
find the finished ZIP in the Builds
folder on your Android disk image.
0 - Go to Main Menu
Enter option:
There you can see you need to install Xcode, if you haven't already. It is free in the Mac App Store (this script is for OS X, you know).
All the options are pretty self explanatory. Make sure you have run the folder set up for the ROM which you wish to build first. Run the initialize option for your desired ROM before running the build option.
That is it! After the build has done (takes a while the first time you set all this up, much faster the next few times) you will be able to build your own nightly's, or whatever you so desire! Have fun!
NOTE: If you have an error regarding "Xcode" and the "10.6 SDK" when trying to build, download the MacOSX10.6.sdk.zip, decompress it, and place it in "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/".
Disclaimer: This will only work with devices that are officially supported by AOKP or CM10.1. If your device is not supported by their official repos, either wait to see if it is, try to edit my script to get the repo your device's tree is on, or wait until I get around to writing a tutorial on how to add custom repos.
Please do not redistribute this without my permission,
and feel free to hit that thanks button if you liked this.
Version 1.0 - Initial Release
Version 1.1 - Bug Fixes
Version 1.2 - Bug Fixes
Reserved for future tips and tricks.
Thanks mate..
Sent from my A99 using Tapatalk 2
What Mac OS version is this for?
This is sweet and appreciated. I can't wait to try this tonight.Thanks for the script and tutorial.
What Mac OS X is this for? I assume Mountain Lion. I'm run 10.8.2 at work and thinking about updating my home computer to the same. I have a build environment setup for OS X 10.6.8 at home, but Mac Ports was giving me issues and this will help me in getting my build environment back up and going. Thanks again.
I have mountain Lion, will it work on it? I am surely gonna give it a try when i get home! I was thinking on installing ubuntu. but nahh!
Make sure you mount the sparse image before trying to install the folders
I unfortunately do not own a fast enough computer can someone build aokp for xoom?
Which Version of xCode is requirement? (4.4, 4.0 or a older Version)
emd2009 said:
I unfortunately do not own a fast enough computer can someone build aokp for xoom?
Click to expand...
Click to collapse
Wingray stingray, everest ?
---------- Post added at 08:33 PM ---------- Previous post was at 08:33 PM ----------
heubergen said:
Which Version of xCode is requirement? (4.4, 4.0 or a older Version)
Click to expand...
Click to collapse
just follow the instructions at macports to get the latest updated.
grad061980 said:
This is sweet and appreciated. I can't wait to try this tonight.Thanks for the script and tutorial.
What Mac OS X is this for? I assume Mountain Lion. I'm run 10.8.2 at work and thinking about updating my home computer to the same. I have a build environment setup for OS X 10.6.8 at home, but Mac Ports was giving me issues and this will help me in getting my build environment back up and going. Thanks again.
Click to expand...
Click to collapse
I'm running OS X 10.8.2 and that's what I build on.
sonymsam said:
I have mountain Lion, will it work on it? I am surely gonna give it a try when i get home! I was thinking on installing ubuntu. but nahh!
Click to expand...
Click to collapse
Mountain Lion should be fine. I run 10.8.2
wildestpixel said:
Make sure you mount the sparse image before trying to install the folders
Click to expand...
Click to collapse
Did you have to? Mounting should be a part of the script. I will look into that.
heubergen said:
Which Version of xCode is requirement? (4.4, 4.0 or a older Version)
Click to expand...
Click to collapse
I have the developer beta, but the newest in the App Store should work fine.
any way we can build on windows? without emulation?
Thanks for making this easy! Is there a way to leverage this to also cherrypick patches or revert official merges that don't work well for me?
ross231 said:
any way we can build on windows? without emulation?
Click to expand...
Click to collapse
Not at the moment, and not that I know of at all, actually.
ahpatel said:
Thanks for making this easy! Is there a way to leverage this to also cherrypick patches or revert official merges that don't work well for me?
Click to expand...
Click to collapse
Not currently, not a bad idea though.
Fantastic tutorial. Cant wait to figure out how to compile AOKP for my unsupported i777.
i screwed up and mistakenly ejected the Android DMG and it won't let me create a new one,,,,what should i do?
Plays2 said:
i screwed up and mistakenly ejected the Android DMG and it won't let me create a new one,,,,what should i do?
Click to expand...
Click to collapse
Remount it. It is located in your home directory.
---------- Post added at 07:54 PM ---------- Previous post was at 07:38 PM ----------
Trying to compile for the SGS2 i777 and I get the following error:
Code:
---This is where you choose your device config---
You're building on Darwin
(ohai, koush!)
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_mips-eng
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. mini_mips-userdebug
8. mini_x86-userdebug
9. full_panda-userdebug
Which would you like? [full-eng] 6
build/core/combo/HOST_darwin-x86.mk:62: *****************************************************
build/core/combo/HOST_darwin-x86.mk:63: * Cannot find SDK 10.6 at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
build/core/combo/HOST_darwin-x86.mk:65: * If you wish to build using higher version of SDK,
build/core/combo/HOST_darwin-x86.mk:66: * try setting BUILD_MAC_SDK_EXPERIMENTAL=1 before
build/core/combo/HOST_darwin-x86.mk:67: * rerunning this command
build/core/combo/HOST_darwin-x86.mk:69: *****************************************************
build/core/combo/HOST_darwin-x86.mk:70: *** Stop.. Stop.
Device armv7a not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for armv7a not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/combo/HOST_darwin-x86.mk:62: *****************************************************
build/core/combo/HOST_darwin-x86.mk:63: * Cannot find SDK 10.6 at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
build/core/combo/HOST_darwin-x86.mk:65: * If you wish to build using higher version of SDK,
build/core/combo/HOST_darwin-x86.mk:66: * try setting BUILD_MAC_SDK_EXPERIMENTAL=1 before
build/core/combo/HOST_darwin-x86.mk:67: * rerunning this command
build/core/combo/HOST_darwin-x86.mk:69: *****************************************************
build/core/combo/HOST_darwin-x86.mk:70: *** Stop.. Stop.
** Don't have a product spec for: 'mini_armv7a'
** Do you have the right repo manifest?
build/core/combo/HOST_darwin-x86.mk:62: *****************************************************
build/core/combo/HOST_darwin-x86.mk:63: * Cannot find SDK 10.6 at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
build/core/combo/HOST_darwin-x86.mk:65: * If you wish to build using higher version of SDK,
build/core/combo/HOST_darwin-x86.mk:66: * try setting BUILD_MAC_SDK_EXPERIMENTAL=1 before
build/core/combo/HOST_darwin-x86.mk:67: * rerunning this command
build/core/combo/HOST_darwin-x86.mk:69: *****************************************************
build/core/combo/HOST_darwin-x86.mk:70: *** Stop.. Stop.
cp: /Volumes/Android/OUT/target/product/i777/cm_i777-ota-eng.xxxxxxx.zip: No such file or directory
Followed the instructions to the letter, but Im not sure whats wrong.
biontc said:
Remount it. It is located in your home directory.
---------- Post added at 07:54 PM ---------- Previous post was at 07:38 PM ----------
Trying to compile for the SGS2 i777 and I get the following error:
Code:
---This is where you choose your device config---
You're building on Darwin
(ohai, koush!)
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_mips-eng
5. mini_armv7a_neon-userdebug
6. mini_armv7a-userdebug
7. mini_mips-userdebug
8. mini_x86-userdebug
9. full_panda-userdebug
Which would you like? [full-eng] 6
build/core/combo/HOST_darwin-x86.mk:62: *****************************************************
build/core/combo/HOST_darwin-x86.mk:63: * Cannot find SDK 10.6 at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
build/core/combo/HOST_darwin-x86.mk:65: * If you wish to build using higher version of SDK,
build/core/combo/HOST_darwin-x86.mk:66: * try setting BUILD_MAC_SDK_EXPERIMENTAL=1 before
build/core/combo/HOST_darwin-x86.mk:67: * rerunning this command
build/core/combo/HOST_darwin-x86.mk:69: *****************************************************
build/core/combo/HOST_darwin-x86.mk:70: *** Stop.. Stop.
Device armv7a not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for armv7a not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/combo/HOST_darwin-x86.mk:62: *****************************************************
build/core/combo/HOST_darwin-x86.mk:63: * Cannot find SDK 10.6 at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
build/core/combo/HOST_darwin-x86.mk:65: * If you wish to build using higher version of SDK,
build/core/combo/HOST_darwin-x86.mk:66: * try setting BUILD_MAC_SDK_EXPERIMENTAL=1 before
build/core/combo/HOST_darwin-x86.mk:67: * rerunning this command
build/core/combo/HOST_darwin-x86.mk:69: *****************************************************
build/core/combo/HOST_darwin-x86.mk:70: *** Stop.. Stop.
** Don't have a product spec for: 'mini_armv7a'
** Do you have the right repo manifest?
build/core/combo/HOST_darwin-x86.mk:62: *****************************************************
build/core/combo/HOST_darwin-x86.mk:63: * Cannot find SDK 10.6 at /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
build/core/combo/HOST_darwin-x86.mk:65: * If you wish to build using higher version of SDK,
build/core/combo/HOST_darwin-x86.mk:66: * try setting BUILD_MAC_SDK_EXPERIMENTAL=1 before
build/core/combo/HOST_darwin-x86.mk:67: * rerunning this command
build/core/combo/HOST_darwin-x86.mk:69: *****************************************************
build/core/combo/HOST_darwin-x86.mk:70: *** Stop.. Stop.
cp: /Volumes/Android/OUT/target/product/i777/cm_i777-ota-eng.xxxxxxx.zip: No such file or directory
Followed the instructions to the letter, but Im not sure whats wrong.
Click to expand...
Click to collapse
Same here compiling for grouper and tried 5 and 6.
It would appear that I've completely screwed it up. After creating a twenty-five gig partition, I began to try to build, and was met with an error about Xcode. I fix it, and continued. However, I ended up deleting the created partition through Disk Image. Whenever I try using the program to create another, it says one already exists (which it doesn't). I don't know what to do now.
DinoSoup said:
It would appear that I've completely screwed it up. After creating a twenty-five gig partition, I began to try to build, and was met with an error about Xcode. I fix it, and continued. However, I ended up deleting the created partition through Disk Image. Whenever I try using the program to create another, it says one already exists (which it doesn't). I don't know what to do now.
Click to expand...
Click to collapse
You could try:
Code:
rm -f ~/Android.dmg.sparseimage
then try recreating it through the app.
Disclaimer: This is undoable and use it at your own risk.
!!! Fast Kernel Flasher!!!
This tool is made for flash kernel faster than before !
It work for all Xperia Kernel.
Click to expand...
Click to collapse
Windows Version:
I let the new version to @Ghostfreak NB because he made this version before me and there is really better and also support .SIN and .ELF files.
Click to expand...
Click to collapse
GO HERE
http://forum.xda-developers.com/member.php?u=4788442
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Linux Version
Adb + Fastboot drivers installer is already include in the .zip
Click to expand...
Click to collapse
Instructions:
Please Read the ReadMe inside the .zip
Click to expand...
Click to collapse
Changelog:
V1:
Initial release
Click to expand...
Click to collapse
V2:
Fix Kernel Flash
Add some options (Windows)
Ubuntu based OS Support (General Linux Support Later)
Click to expand...
Click to collapse
V3
Combine with @Ghostfreak NB Kernel Flasher (Only For Windows) / I continue the Linux Version
Add Mac Version
Now Support all Linux Version
Remake the thread
Fast Adb+Fastboot drivers installer in Linux (+Uninstaller inside the zip)
Click to expand...
Click to collapse
!!!!!!You are the only responsible one for the fact that you made on your Phone !!!!!
Download
Download:
V1 HERE
Click to expand...
Click to collapse
- - - - - - - - - - - - - - - - - - - - -
V3 HERE {Only Linux}
Click to expand...
Click to collapse
V2 HERE {Windows}
Click to expand...
Click to collapse
looks great!
are you planning on making a linux version?
matgras said:
looks great!
are you planning on making a linux version?
Click to expand...
Click to collapse
Yes sure bro !! I will start to work on it !! It was in my ideas
HeadFox said:
Yes sure bro !! I will start to work on it !! It was in my ideas
Click to expand...
Click to collapse
unfortunately i'm running Elementary os at the moment so i'd really like to check it out once it's released!
Nice work... As for similar tool maybe you can check this: http://forum.xda-developers.com/showthread.php?t=2214724
Sent from my Xperia Neo V using xda app-developers app
Attitude.SSJ said:
Nice work... As for similar tool maybe you can check this: http://forum.xda-developers.com/showthread.php?t=2214724
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
Ok thk for the info ! Me i will add Linux and Mac support
Sent from my SGP311 using xda app-developers app
HeadFox said:
Ok thk for the info ! Me i will add Linux and Mac support
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
Thanks, i already loved your ROM and I'm sure you won't disappoint us
sent from my @mark manning
Error by me in script edit.... i have forget the flash before boot so you boot with the kernel but after one reboot you have the older kernel.
Pls wait the new version who comes in few minutes with linux Support @matgras
V2 is HERE !
I have not found tool like this so if there is an other similar tool please tell me
Click to expand...
Click to collapse
Well I'd already made the Windows version Months back..Just that it was only for Xperias so I posted in my forum only to avoid redundancy..
For further issues,you can Pm me.
i've tried the linux version but this happend:
Code:
[email protected]:/home/henry/fastboot# fastboot devices
CB511UYB6C&ZLP fastboot
[email protected]:/home/henry/fastboot# ./FKF_L.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On cm10.1/2 please accept the message ! You have 5sec ! If you are already in fastboot pls wait 5s
error: device not found
cp: cannot stat `*.img': No such file or directory
mv: cannot stat `*.img': No such file or directory
Unknown id: fastboot
rm: cannot remove `boot.img': No such file or directory
[email protected]:/home/henry/fastboot#
manually fastboot works just fine...
EDIT: tried it once again but kept my device on and let it "adb reboot"
Code:
[email protected]:/home/henry/fastboot# ./FKF_L.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On cm10.1/2 please accept the message ! You have 5sec ! If you are already in fastboot pls wait 5s
cp: with --parents, the destination must be a directory
Try `cp --help' for more information.
mv: cannot stat `*.img': No such file or directory
Unknown id: fastboot
rm: cannot remove `boot.img': No such file or directory
[email protected]:/home/henry/fastboot#
Code:
[email protected]:/home/henry/fastboot# ./FKF_L.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On cm10.1/2 please accept the message ! You have 5sec ! If you are already in fastboot pls wait 5s
error: device not found
cp: with --parents, the destination must be a directory
Try `cp --help' for more information.
mv: cannot stat `*.img': No such file or directory
Unknown id: fastboot
rm: cannot remove `boot.img': No such file or directory
matgras said:
i've tried the linux version but this happend:
Code:
[email protected]:/home/henry/fastboot# fastboot devices
CB511UYB6C&ZLPfastboot
[email protected]:/home/henry/fastboot# ./FKF_L.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On cm10.1/2 please accept the message ! You have 5sec ! If you are already in fastboot pls wait 5s
error: device not found
cp: cannot stat `*.img': No such file or directory
mv: cannot stat `*.img': No such file or directory
Unknown id: fastboot
rm: cannot remove `boot.img': No such file or directory
[email protected]:/home/henry/fastboot#
manually fastboot works just fine...
EDIT: tried it once again but kept my device on and let it "adb reboot"
Code:
[email protected]:/home/henry/fastboot# ./FKF_L.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On cm10.1/2 please accept the message ! You have 5sec ! If you are already in fastboot pls wait 5s
cp: with --parents, the destination must be a directory
Try `cp --help' for more information.
mv: cannot stat `*.img': No such file or directory
Unknown id: fastboot
rm: cannot remove `boot.img': No such file or directory
[email protected]:/home/henry/fastboot#
Code:
[email protected]:/home/henry/fastboot# ./FKF_L.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On cm10.1/2 please accept the message ! You have 5sec ! If you are already in fastboot pls wait 5s
error: device not found
cp: with --parents, the destination must be a directory
Try `cp --help' for more information.
mv: cannot stat `*.img': No such file or directory
Unknown id: fastboot
rm: cannot remove `boot.img': No such file or directory
Click to expand...
Click to collapse
You have test my version i send you with PM ?
Sent from my Xperia Arc S using xda app-developers app
HeadFox said:
You have test my version i send you with PM ?
Sent from my Xperia Arc S using xda app-developers app
Click to expand...
Click to collapse
Will try later this day
sent from my kitkat™
matgras said:
Will try later this day
sent from my kitkat™
Click to expand...
Click to collapse
Ok because new version have many fix
Sent from my Xperia Tablet Z
HeadFox said:
Ok because new version have many fix
Sent from my Xperia Tablet Z
Click to expand...
Click to collapse
I can't test now because I only have acces to macbooks running xp at the moment, in 6 hours I may have some spare time
sent from my kitkat™
V3 for Linux is here !!