I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
pavitar said:
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
Click to expand...
Click to collapse
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
ricky310711 said:
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
Click to expand...
Click to collapse
Can you please tell me, how to apply a file permission? I tried checking the box which is not checked in the snapshot shared, but that too gives an error.Says "Operation failed"
pavitar said:
Can you please tell me, how to apply a file permission?
Click to expand...
Click to collapse
download mobile terminal from playstore
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
pavitar said:
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
Click to expand...
Click to collapse
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
iamareebjamal said:
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Click to expand...
Click to collapse
pavitar said:
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
Click to expand...
Click to collapse
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
iamareebjamal said:
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
Click to expand...
Click to collapse
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
pavitar said:
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
Click to expand...
Click to collapse
Try this
https://play.google.com/store/apps/...&utm_medium=organic&utm_term=universal+init.d
Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
N7Gabe said:
Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
Click to expand...
Click to collapse
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
MigoMujahid said:
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
Click to expand...
Click to collapse
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
N7Gabe said:
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
Click to expand...
Click to collapse
No, no need for that, just the ROM, and it won't delete anything.
MigoMujahid said:
No, no need for that, just the ROM, and it won't delete anything.
Click to expand...
Click to collapse
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
N7Gabe said:
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
Click to expand...
Click to collapse
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
MigoMujahid said:
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
Click to expand...
Click to collapse
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
Code:
D:\Android\sdk\platform-tools>adb devices
List of devices attached
0009bd0863c43f unauthorized
Code:
D:\Android\sdk\platform-tools>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
N7Gabe said:
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
Click to expand...
Click to collapse
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
MigoMujahid said:
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
Click to expand...
Click to collapse
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
N7Gabe said:
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
Click to expand...
Click to collapse
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
MigoMujahid said:
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
Click to expand...
Click to collapse
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Code:
D:\Android\sdk\platform-tools>adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
D:\Android\sdk\platform-tools>adb shell
~ # [6n
~ # [6nls
and-sec init.recovery.service.rc selinux_version
boot init.recovery.smdk4210.rc sepolicy
boot.txt init.recovery.usb.rc service_contexts
cache license sideload
charger mnt supersu
data proc sys
default.prop property_contexts system
dev recovery tmp
etc res twres
file_contexts sbin ueventd.rc
fstab.smdk4210 sdcard0 ueventd.smdk4210.rc
init sdcard1 usbotg
init.rc seapp_contexts
~ # [6ncd data
/data # [6nls
/data # [6n
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
N7Gabe said:
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
Click to expand...
Click to collapse
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
MigoMujahid said:
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
Click to expand...
Click to collapse
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
N7Gabe said:
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
Click to expand...
Click to collapse
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
MigoMujahid said:
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
Click to expand...
Click to collapse
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
N7Gabe said:
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
Click to expand...
Click to collapse
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
(not the same path for the contacts.db file)
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
MigoMujahid said:
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
Click to expand...
Click to collapse
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
N7Gabe said:
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
Click to expand...
Click to collapse
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
MigoMujahid said:
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
Click to expand...
Click to collapse
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
N7Gabe said:
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
Click to expand...
Click to collapse
Thanks for the tip, i have a marshmallow ROM right now, it seems that the location was changed in Nogut, I'll keep that in mind.
Have a good life too.
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Rust3dCor3 said:
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Click to expand...
Click to collapse
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
MyNameIsRage said:
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
Click to expand...
Click to collapse
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Rust3dCor3 said:
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Click to expand...
Click to collapse
Why don't you use es file manager? I just tried i was able to do it with es.
MyNameIsRage said:
Why don't you use es file manager? I just tried i was able to do it with es.
Click to expand...
Click to collapse
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Rust3dCor3 said:
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Click to expand...
Click to collapse
Why don't you try deleting it from twrp.
MyNameIsRage said:
Why don't you try deleting it from twrp.
Click to expand...
Click to collapse
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Rust3dCor3 said:
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Click to expand...
Click to collapse
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
MyNameIsRage said:
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
Click to expand...
Click to collapse
I can't believe how stupid I am. Thank You for Your advice.
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
Code:
ln -s /vendor/etc/charger /system/etc/charger
*You can actually use adb within OS:
adb root
adb remount
adb pushor you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Dil3mm4 said:
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
*You can actually use adb within OS:
adb root
adb remount
adb push
or you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Click to expand...
Click to collapse
Error pushing on adb, Doesn't work on mate 9,will appreciate if you provide more instructions for installation.
Thank you!
The partitions are mostly to small partitioned... On honor 9 lite i used product partition instead...
Its not forever... every dirty flash on system or updating vendor security patch level will drop it. A magisk module dont work cause its mounted to late...
Darkest-Dark said:
The partitions are mostly to small partitioned... On honor 9 lite i used product partition instead...
Its not forever... every dirty flash on system or updating vendor security patch level will drop it. A magisk module dont work cause its mounted to late...
Click to expand...
Click to collapse
"Nothing lasts forever and we both know hearts can change"
-Guns 'N' Roses
Anyways, yeah, updates on vendor will wipe this "hack".
But, better than nothing
No need for this if you wipe data with stock recovery and then flash ROM + GApps, and then factory reset in stock recovery. My phone chargea fine in "offline mode."
Dil3mm4 said:
"Nothing lasts forever and we both know hearts can change"
-Guns 'N' Roses
Anyways, yeah, updates on vendor will wipe this "hack".
But, better than nothing
Click to expand...
Click to collapse
Directly modifying /system/etc/charger also seems to be effective.Could you make it into a magisk module?
Ccboxes said:
Directly modifying /system/etc/charger also seems to be effective.Could you make it into a magisk module?
Click to expand...
Click to collapse
Here's your answer. Read the thread first.
Darkest-Dark said:
A magisk module dont work cause its mounted to late...
Click to expand...
Click to collapse
Thanks for this Fix. Works awesome on Mate 10 lite with RR Official.
I installed on other way cause ADB provided to many Error Messages.
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Done and works awesome Thank you Dil3mm4 !
Dil3mm4 said:
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
Code:
ln -s /vendor/etc/charger /system/etc/charger
*You can actually use adb within OS:
adb root
adb remount
adb pushor you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Click to expand...
Click to collapse
Hey,
I did everything like destriben, but it did not work for my Mediapad M5,
it still boots up when I wanted to change while my device is powered off.
anyone to tell me how i can use this on aosp 8,1 treble rom ? i am new on huawei, treble rom ... thanks
leap_ahead said:
anyone to tell me how i can use this on aosp 8,1 treble rom ? i am new on huawei, treble rom ... thanks
Click to expand...
Click to collapse
anyone ?
leap_ahead said:
anyone ?
Click to expand...
Click to collapse
Dude, there is this new term called reading the thread, i know it's a bit hard to take in at first, but you'll get the hang of it. If you can't read, then you shouldn't be here.
This cause reboot constantly.
i've p8 lite 2017 (Pra-LX1) with GSI 8.1
crayonicle said:
Dude, there is this new term called reading the thread, i know it's a bit hard to take in at first, but you'll get the hang of it. If you can't read, then you shouldn't be here.
Click to expand...
Click to collapse
I read the instruction.but many user and me have problem with this,
so its not my false
leap_ahead said:
I read the instruction.but many user and me have problem with this,
so its not my false
Click to expand...
Click to collapse
if many users, including you, that have this problem, then all of you should read the thread, again and again until you understand
the instructions are very clear on what to do.
Everytime we flash a new system image this command has to be executed, right @Dil3mm4?
Will it work if @phhusson includes the "ln" command to the script rw-system.sh, after identifying the device as an Huawei device?
that`s good
I have already post a second variant of tutorial. Works 100% and its easy.
TUT 2:
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Reboot and done
Copkiller2010 said:
I have already post a second variant of tutorial. Works 100% and its easy.
TUT 2:
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Reboot and done
Click to expand...
Click to collapse
same things done but not working, huawei p20 lite android 10
I have this offline charging problem also in my Lenovo s5.