Hi!
What is libra.ko and librasdioif.ko?
If I flash different version of kernel, which doesn't have those files, will those kernel modules still working with the new kernel?
The above files you said are generated while compiling the zImage. These modules may be related to wireless connections.(As found in wireless folder)
They are specific for each device.
Sent from my GT-I9500 using XDA Free mobile app
Mandark52 said:
The above files you said are generated while compiling the zImage. These modules may be related to wireless connections.(As found in wireless folder)
They are specific for each device.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
And why librasdioif.ko is located in the extras folder?
The librasdioif.ko is tied to the SDIO's chipset
support for both the SDCard mechanism and wireless. So you can say that it responsible for SD card I/O and also plays part in the wireless.
Sent from my GT-I9500 using XDA Free mobile app
Mandark52 said:
The above files you said are generated while compiling the zImage. These modules may be related to wireless connections.(As found in wireless folder)
They are specific for each device.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. Those modules present on all ROMs I installed. I'm wondering if those modules will still be working on different kernel version.
Related
I recently obtained and used the slow-work.ko and cifs.ko that was posted in the recent xda thread, that was suppose to be new cifs.ko compatible with kernel 2.6.35.7., however I am following problem:
[Problem]
Mount Manager shows the mount was successful, though mounted drive shown as "0.0 KB" and no folder are listed as it should be in any Astro or other explorer.
[Condition]
1. Both modules (slow-work, cifs) loaded fine, even tried several times to make sure that slow-work loads first.
2. -mount parameters are unchanged since it was working during Froyo such as: user="guest", iocharset=utf8, file_mode=0777, dir_mode=0777
3. Network drive name and settings are unchanged since last connected, and accesibility is fine from Windows explorer.
I have found forum discussing about CIFS not working, though there has been no forum discussing about "it mounts, but no folder" issue that I have.
This forum is my only hope some here can give me advise to resolve this problem.
Issue resolved. Cifs did work, it was a bug in Mount Manager that shows mointed drive as 0.0kb
Can you post your module files please. I was trying to use some found here but none of them worked so far.
Sent from my GT-P1000 using XDA App
Please?
Sent from my GT-P1000 using XDA App
nabuhonodozor said:
Can you post your module files please. I was trying to use some found here but none of them worked so far.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Ditto. Please could you post the modules here, thanks!
Sent from my GT-P1000 using XDA Premium App
What is the main difference?
Sent from my HTCONE using xda premium
In short the odexed firmware is faster and supposedly more secure (usually a stock build). A deodexed one gives more modification, themeable, and found in most custom roms.
In terms of user experience deodexed ROMs are only slower on first boot, after which they are or seem the same speed as the former odexed version/source.
Sent from my HTCONE using Tapatalk 2
Thank you for the explanation
Sent from my HTCONE using xda premium
justin24 said:
What is the main difference?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
It means that any apps in /system have an accompanying .odex file which includes integrity information about its corresponding package. This prevents these packages from being modified, which theoretically means that a factory reset/uninstallation of updates should always yield a known working app. Since themes and many customizations work by modifying the apks in /system, they'll fail the check against the corresponding .odex file and cause problems.
I was trying to modify the stock 244 rom using kitchen.I built the zip successfully but when flashing i always get a status 0 error.I know that the error is because of the updater script but i dont know how to modify it for my xperia z.I am new to this so someone please help me to successfully build the rom.
anyone willing to help?
Download a Rom and have a look at their updater script. Then modify yours as required.
Sent from my C6603 using xda app-developers app
I tried that.It seems I have to add c6602 support in kitchen edify folder.Can you help me?I tried some links without success
Status 0 errors are usually caused by an incompatible update-binary.
Try replacing the update-binary in your zip with one from a zip you know works on your phone.
Sent from my SK17i using XDA Premium 4 mobile app
Ticklefish said:
Status 0 errors are usually caused by an incompatible update-binary.
Try replacing the update-binary in your zip with one from a zip you know works on your phone.
Sent from my SK17i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I have zips of a few cm based roms.But I dont think the updater scripts of those will work with my modified stock right?
I didnt do that because i fear i might brick my phone or something..
r1punjay said:
Well I have zips of a few cm based roms.But I dont think the updater scripts of those will work with my modified stock right?
I didnt do that because i fear i might brick my phone or something..
Click to expand...
Click to collapse
I don't mean the update-script, I mean the update-binary. All the script does is tell the recovery what files to replace.
Bricking your phone depends on what you're trying to change. Generally you can only do it by flashing a wrong kernel.
Sent from my SK17i using XDA Premium 4 mobile app
Ticklefish said:
I don't mean the update-script, I mean the update-binary. All the script does is tell the recovery what files to replace.
Bricking your phone depends on what you're trying to change. Generally you can only do it by flashing a wrong kernel.
Sent from my SK17i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh u mean i can use the update binary from the cm rom in my rom?
Yep. After you build with kitchen or whatever, simply substitute update binary from Meta Inf blah blah, from the Cm10 of your device to your own zip. :thumbup:
Sent from my C6603 using xda app-developers app
Hi guys,
I bought a 4800mAh battery for my lg 4x.. With stock and stock-based roms my phone shutdown after 10 seconds with "use genuine battey message". There is a way to bypass this check?( build.prop commands, patches, etc.) thanks in advance
Sent from my LG-P880 using XDA Free mobile app
You'd probably need a modified kernel. There's a command line parameter passed by the bootloader (batteryVerified). It's read on initialization and is loaded by LGE battery driver later. Userspace can read it, the corresponding code is here. I guess you're on stock, because I'm pretty sure this doesn't get checked on custom roms. Modifying userspace part could also be possible and even easier if the needed code is found.
Now i'm on Omnirom and the battery check doesn't appear. i tried also with a non-stock kernel (ioadak) but nothing changed. So, how must i use the code in your link?
simonekamikaze said:
Now i'm on Omnirom and the battery check doesn't appear. i tried also with a non-stock kernel (ioadak) but nothing changed. So, how must i use the code in your link?
Click to expand...
Click to collapse
Stock rom or the kernel used on it must be modified.
Adam77Root said:
Stock rom or the kernel used on it must be modified.
Click to expand...
Click to collapse
How? Sorry i never done something like that
Sent from my GT-P7320 using XDA Free mobile app
simonekamikaze said:
How? Sorry i never done something like that
Sent from my GT-P7320 using XDA Free mobile app
Click to expand...
Click to collapse
Try using your stock rom but with Iodak kernel.
I'll try
Sent from my LG-P880 using XDA Free mobile app
I have checked stock rom frameworks and found the easiest way of disabling it. Edit build.prop and set 'ro.lge.capp_valid_batteryid' to false.
Adam77Root said:
I have checked stock rom frameworks and found the easiest way of disabling it. Edit build.prop and set 'ro.lge.capp_valid_batteryid' to false.
Click to expand...
Click to collapse
Thanks, i'll try and report here the result
Sent from my GT-P7320 using XDA Free mobile app
So i tried both methods and results are: stock rom, iodak kernel and modded build prop are okay, battery works. Stock + stock kernel and modded build prop works too. Thank you very much for intresting and help
Sent from my GT-P7320 using XDA Free mobile app
simonekamikaze said:
So i tried both methods and results are: stock rom, iodak kernel and modded build prop are okay, battery works. Stock + stock kernel and modded build prop works too. Thank you very much for intresting and help
Sent from my GT-P7320 using XDA Free mobile app
Click to expand...
Click to collapse
it worked also for me..thank you!
How to use this code?????.
can it work on L.G F160s??
Use this utility at your own risk. By using this application, you agree not to hold ShinobiSoft Software ( me )
and XDA-Developers liable for any issues or damages that may arise as a by-product of it's use.Important
This application is intended specifically for the LG L90. It will NOT run on any other device.
This application is NOT intended to run on stock ROMs either, although theoretically it should work.
This application currently only works on KitKat ROMs. Sorry for the inconvenience.This application is a remake of my LG Optimus L90 Utilities script. This application has the same abilities as it's script counterpart, but now with a nice GUI.
This application is a navigation drawer styled application. When first installed and run the navigation drawer is initially open. This only happens on the first run of the app. To access the navigation menu, swipe from the left edge of your screen to the right.
NOTE:
There is an option to flash bootloader patches for D405 and D410 variants. It is currently disabled until I work a couple minor things out with the process. It should be enabled in my next release.
Requirements
KitKat ROM
Your device MUST be rooted
Future versions will also require BusyBox
Permissions
android.permission.ACCESS_SUPERUSER - For root access
android.permission.WRITE_EXTERNAL_STORAGE - For writing to the external sdcard. IE; making backups
android.permission.INTERNET - For the built-in help viewer. The help viewer never goes online but the permission is required by the WebView component
Features
View extensive device information ( WIP )
Basic partition backup ( boot, cache, laf, recovery, system, userdata ).
Flash images ( boot and recovery )
Fastboot Manager - Easily toggle between fastboot mode and software upgrade modes.
QuickButton Manager ( D415 ) - Assign an app to open when the QuickButton is pressed. ( 4.4.2 - 4.4.4 only )
Reboot dialog
Most activities have an "Information" icon that provides additional information about itself.
TODO
Cleanup and add more device information ( WIP )
Add an advanced option to backup ANY partition
Add a reboot widget
Add an About activity. Currently I'm just using a popup dialog to show generic about information.
Ability to flash boot and recovery images that are packaged in flashable zips.
User suggestions
DownloadLG L90 UtilitiesAnyone willing to lend a hand to help develop this application further, please let me know via PM, and I'll consider making this a DevDB project as well as sharing my sources on GitHub. I'm slightly hesitant of this mainly because I've spent alot of time developing special classes for this.
Changelog
2015-01-19
0.1.6
Fixed QuickButton Manager nullPointerException
Application base backup folder changed to EXTERNAL_SD/LGL90UTILITIES/<DEVICE_SERIAL>
Add new "Sensors" tab to Device Information
Redesigned how Storage tab information is displayed
Complete code reorganization and cleanup
Removed unused resources
Display tab information rearranged and a little more information is available
Added a menu option for Device Information for quick jumping to a specific tab
2015-01-13
0.1.5 -
Fix for not checking for/creating backup folder if default backup path changed by user
Fix for internal file browser not properly switching between internal and external storage
0.1.4 - Fix where incorrect partitions were getting backed up.
0.1.3 - Fix incorrectly identified internal and external storage
0.1.2 -
Fixed incorrectly identified device ( not actually a problem on my end, but arises from incorrect build.prop values ).
Force portrait mode for main application activity. "Information" activity works in both portrait and landscape modes.
0.1.1 - Attempt to fix where device not correctly identified.
0.1.0 - Initial release
Reserved 2
Reserved
Will test it out, trying to install but how to exactly if i tap install in root browser i get an error on parsing, do i just copy it to a folder.
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Will test it out, trying to install but how to exactly if i tap install in root browser i get an error on parsing, do i just copy it to a folder.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
That's weird... Are you on stock? I installed it via Es File Explorer with no problems. I should note that this IS NOT intended to run on stock KitKat but on custom ROMs. Although I'm not sure why this wouldn't work on stock...
shinobisoft said:
That's weird... Are you on stock? I installed it via Es File Explorer with no problems. I should note that this IS NOT intended to run on stock KitKat but on custom ROMs. Although I'm not sure why this wouldn't work on stock...
Click to expand...
Click to collapse
Im on the stock modified rom, i believe thats on the d41510c build. Ill try to download again, maybe there was an error with the download.
Update: the error is in the download, on the host it states the apk is about 499kb, when i download i only get about 29kb. Not sure if its the apk its self that is the error or my device yet but tried both aosp and dolphin browser, same result. Also te odd thing is b i th downloads are different one was 29.24kb the other 29.36kb
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Im on the stock modified rom, i believe thats on the d41510c build. Ill try to download again, maybe there was an error with the download.
Update: the error is in the download, on the host it states the apk is about 499kb, when i download i only get about 29kb. Not sure if its the apk its self that is the error or my device yet but tried both aosp and dolphin browser, same result. Also te odd thing is b i th downloads are different one was 29.24kb the other 29.36kb
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
I uninstalled and just went thru the download via TapaTalk and FireFox. Choose the "Download Now" button and not the "Download" button. After the download finished, tap the notification to install.
And I'm also going to move this app from Dev-Host to my web site.
shinobisoft said:
That's weird... Are you on stock? I installed it via Es File Explorer with no problems. I should note that this IS NOT intended to run on stock KitKat but on custom ROMs. Although I'm not sure why this wouldn't work on stock...
Click to expand...
Click to collapse
Got it to download, used puffin browser, not sure why it wouldnt in aosp or dolphin, also upon opening the app i get an error saying this is or lg optimus l90 and l90 family then states i have the optimus l90 d415 the closes. Tried couple times same thing.
Sent from my LG-D415 using XDA Free mobile app
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
shinobisoft said:
I uninstalled and just went thru the download via TapaTalk and FireFox. Choose the "Download Now" button and not the "Download" button. After the download finished, tap the notification to install.
And I'm also going to move this app from Dev-Host to my web site.
Click to expand...
Click to collapse
Yes was using the download now button, the other one leads to some website but for some reason and maybe its just my device wouldnt work in aosp or dolphin. Still have the error when opening the app though stating its for l90 and l90 family then closes.
Sent from my LG-D415 using XDA Free mobile app
That's just strange. You have the same device I have and it installs and runs just fine for me, I'm running CM11 tho... I think your stock ROM may be the issue.
shinobisoft said:
That's just strange. You have the same device I have and it installs and runs just fine for me, I'm running CM11 tho... I think your stock ROM may be the issue.
Click to expand...
Click to collapse
Also yes just notice it states i have the lge-d415 and not lg-d415 maybe its the rom making recognizing it incorrectly im on jb3p76's stock modified. Although i looked under hardware in settings and says the model is lg-d415.
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Also yes just notice it states i have the lge-d415 and not lg-d415 maybe its the rom making recognizing it incorrectly im on jb3p76's stock modified. Although i looked under hardware in settings and says the model is lg-d415.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Try this:
Open Terminal Emulator and type:
Code:
getprop ro.product.board
and report back what your result is.
This value is how the app determines if it's installed on the correct device or not. I may need to look in to another method.
shinobisoft said:
Try this:
Open Terminal Emulator and type:
Code:
getprop ro.product.board
and report back what your result is.
This value is how the app determines if it's installed on the correct device or not. I may need to look in to another method.
Click to expand...
Click to collapse
Result came as MSM8226
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Result came as MSM8226
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
That's the issue. It should have returned W7.
Try the same "getprop" command but with "ro.board.platform" instead. This should return MSM8226.
shinobisoft said:
That's the issue. It should have returned W7.
Try the same "getprop" command but with "ro.board.platform" instead. This should return MSM8226.
Click to expand...
Click to collapse
Correct that came back as msm8226
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Correct that came back as msm8226
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
I've added a work-around for this issue. I'll rebuild and re-upload shortly
OP download link updated. Sorry, it's still on Dev-Host.
shinobisoft said:
I've added a work-around for this issue. I'll rebuild and re-upload shortly
OP download link updated. Sorry, it's still on Dev-Host.
Click to expand...
Click to collapse
Also i edited my build.prop with the value you gave me for ro.product.board to w7, the app works correctly now. Ehen you upload the new apk, i can change it back to msm8226 to see if it work on that as well.
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Also i edited my build.prop with the value you gave me for ro.product.board to w7, the app works correctly now. Ehen you upload the new apk, i can change it back to msm8226 to see if it work on that as well.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
I didn't suggest editing build.prop because that can be erroneous at times and as an app user you shouldn't need to edit your device to make an app work.
And the new build is uploaded already
Sent from my LG-D415 using Tapatalk
shinobisoft said:
I didn't suggest editing build.prop because that can be erroneous at times and as an app user you shouldn't need to edit your device to make an app work.
And the new build is uploaded already
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Sorry was just trying to help but downloaded the new apk build, get same error with the MSM8226 value in the build.prop the apk build i downloaded is 0.1.1, same result.
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Sorry was just trying to help but downloaded the new apk build, get same error with the MSM8226 value in the build.prop the apk build i downloaded is 0.1.1, same result.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, I didn't test it myself before uploading... I now have the same issue... Back shortly with a fix...
Fixed and uploaded again. I did test before uploading this time, LOL. See the OP