I'm getting mount file system errors when trying to install some ROMs not all
How do I fix this
Just a thought: if you are reporting bugs maybe include your specific device of lux. I have noticed certain bugs only apply to double sim xt1563 and such.
Related
Hey there, I'm Australian.
My G900I is from Telstra. Right now, I have cm12 installed.
The problem I have is that when I flash roms, NFC is jammed on and doesn't work which causes massive battery drain.
The only way I've found to solve this is to flash KToonsez Kernel which has some kind of "NFC fix" as I've seen it called.
Is there any way to get the NFC fix standalone? Is there some way to make NFC work in the first place?
More details upon request, thank you XDA <3
if already searched, should have mentioned this in your thread:
http://forum.xda-developers.com/galaxy-s5/help/nfc-fix-900i-varients-running-900f-base-t3008439
This is the one I'm now using... which is from Neatrom for 900f...
this seems to work at first... but then I can get the actual NFC tag to read. It reads... but then makes a https://mega.co.nz/#!3EVjDJaA!Qr__QPWD-Ay9aXGr0sSbjgW_sp3gBi8abcEf5Sh1x90 fail sound
I noticed that after replacing files manually it was actually the libs that made the difference to stop the "NFC service has stopped" message.
These are the related files:
Code:
\system\app\NfcNci
\system\app\NfcNci\NfcNci.apk
\etc\libnfc-brcm-20791b04.conf
\system\etc\libnfc-brcm-20791b05.conf
\system\etc\libnfc-brcm.conf
\system\lib\hw
\system\lib\libnfc-nci.so
\system\lib\libnfc_nci_jni.so
\system\lib\hw\nfc_nci.bcm2079x.MSM8974.so
as I say... I went through manually changing these one by one and the apk and odex made no difference, etc files also, just the libs. I didn't get to try changing the file in hw. I'd like to know what that file directory is - is this the kernel driver right?
Hi,
I'm having a weird problem I couldn't find any solution to through google-foo. The concate-power_supply_info.csv if filling up crazy fast (couple MB per minute) on my xt1563 running LineageOs 14.1
I've found a dirty fix for now by removing write and exec permission in parent folder power_supply_logger located in the data partition (removing write permission for the csv itself didn't work, it was reverting back). Anyone experienced similar issue? I've updated Lineage, but the problem persists. Could any problem arise because whatever does this behavior can no longer log in the csv file?
Thanks,
Max
I have exactly the same issue on my MOto G4 Plus running LineageOS 14.1 (20171009-NIGHTLY-athene) with Magisk v14.
The cause of this problem is an internal Motorola debugging tool (batt_health) which collects stats about the battery in that file but it is not supposed to run on production devices. I fixed the problem by removing the binary on moto 8916/8939 family around a month ago. I'll notify athene's maintainers too. In the mean time you can remove system/bin/batt_health.
XT 1644 (4GB/64GB). Flashed to AOSP 8.1 (5.8), all is basically running well except the torch/flashlight.
From what I've surmised, after the ROM flash, there's a mismatch between the /vendor/build.prop and /system/build prop causing the silly "Android System there's an internal problem with your device. contact your manufacturer for details"
The fingerprint mismatch is odd, as the vendor file has almost the same one as the system, but if I do a "getprop ro.build.fingerprint", I get something else entirely. Trying to figure out where all the fingerprint data is stored
Nothing wrong with the phone, but I've fixed all the other pesky items, and would love to fix this one.
Has anyone tackled this issue?
Hi there
I share your frustration, see here:https://forum.xda-developers.com/android/help/build-prop-android-8-1-issues-editing-t3949531
I have what I think is the same issue. i can basically do anything I want with a device I have, but as soon as I touch the /system/build.prop I get bootloop!!
I'm pretty experienced so its not permissions, bad build.prop, have tested DM-Verity etc
My guess so far is that something is looking up the system and vendor build.props and not liking something for some reason.
Your last post was a year ago, did you manage to resolve this?
I usually change /system/build.prop and have never had an issue up through Android 10. I know this is elementary and no intention to offend anyone - but are you sure the file is being saved with unix-style line endings.
Saw this come up a LOT on the beta threads.
Thought it best to consolidate it here.
Unsure how to fix it - certainly there are web pages about this suggesting it is because of a modified rooted system however most people aren't rooted so that's now it.
Anyone have a solution that works for all?
FIXED:
Make sure you are on the latest October firmware before installing update.zip.
"How to fix" .... stop messing with your phone ...fixed...
Well that's helpful - thanks Kevin!
Ok for me i fixed it by updating to the latest firmware - the October one - by Odin.
After that it worked.
Link????! Plz!!
Although this should be in Q&A because the title is misleading. I know a workaround for this error if you're direly wanting to try the beta like I was. Presumably something small could've triggered this error. From my personal experience, I believe XDA Navbar may have triggered something when I granted it permissions through adb (no I do not have root).
Either way, it's a simple fix just requires a micro sd. Instead of flashing the beta update via adb, move it to a micro sd card and when in recovery, navigate the micro sd and install it through there. I do not know if this will fix it for future updates with adb sideload and all (assuming the update will overwrite any 'modified' files) but, worst case you'll have to either keep pushing updates through sd card or flash stock firmware.
You may want to post this in the OG post so it doesn't get moved because, I have a feeling that this issue might be a little more popular.
Thanks guys and hope this fixes the issue!
I am having the same issue but i dont have any adb permissions enabled on my note 10+. know of any other thread or fix that addresses this?
Hello,
whenever I'm inserting the sd card, android crashes and reboots. If I start it with inserted sd card, I can reach the pin screen where it freezes and reboots.
I'm currently running Havoc OS, but have tried it with Bliss, Lineage and another Kernel with the same outcome.
I have tried using different sd cards with different file systems or none at all.
This is the last logcat I see:
0 0 I [LGE][MMC][CCAudit]mmc0: slot status change detected(INSERTED), GPIO_ACTIVE_HIGH
I however can use the sd card without a problem in the recovery.
I have the European version 870.
What can I try or is there a way to track it better than adb with logcat?
Help would be very much appreciated.
For anyone experiencing this problem:
(dirty) flashing this stock kernel helped:
[Kernel][Stock][Pie][H870] Marshall Kernel [v0.2]
[Kernel][Stock][Pie][H870] Marshall Kernel [v0.2]
Marshall Kernel Basic information Marshall kernel is targeted to be balanced between battery life, stability and performance. It's based on a mix of mk2000, Melina kernel and couple of my mods. H870 is so far the only model supported since its...
forum.xda-developers.com
thanks to TheWolveSVK, Melina and mk2000 for the kernel
While this is a fix, which works, it's not an explanation. Since there doesn't seem to be many or any at all persons having the same issue, I'd like to know what the cause was/is.
If I get around to it, looking at what usually happens by inserting the sd card and looking for a diff in the two kernels has been added to the (rather long) to do list.
edit: couldn't gather any last_kmsg. Does it have to be enabled in the build or is it possible to enable it retrospectively?
Update:
Also this kernel with the latest HAVOC build works flawless for me:
[ROM][H870][Stock] OPEN EU LG-H870 10L ROM
LG-H870 OPEN EU 10L ROM Hello everyone This is my first work in things like Android. I am just about to learn how to develop and port for Android. This zip is created from the original KDZ. I changed the Boot.img, so you do not have to...
forum.xda-developers.com