Related
Let me start by saying that i do not take credit, by any means for this fix, i did use the SEARCH tool and found the solution. What i'm doing is posting a faster/easier fix for the thread here http://forum.xda-developers.com/showthread.php?t=2196200
All of the help i read, is from this thread here http://forum.xda-developers.com/showthread.php?t=2102981&highlight=miui+camera.
Our common issue was that each time we flashed an AOSP ROM(for me the new MIUI PORT FROM SPRING TO SHG3 TMO) the camera wouldn't connect, and that's a deal breaker. Im sure it was for many of you. (I'm a noob, just giving a heads up, and this is why i have to post here rather than the first thread, being understandbly limited and all) As the 2nd of the two threads says, the issue is that on stock rom there is a bin file named SlimISP_ZH.bin, once flashed, it's no longer there, causing the camera to simply not connect. I odin'ed back to stock(because i didn't have access to the bin file), used ES File Explorer to "copy" the SlimISP_ZH.bin file into my external sd card, then i proceeded to flash to the MIUI ROM of my choice, after setting up the phone, using ES File Explorer again, i placed the bin file on the /data directory. If a mod can confirm it's ok, i'll be more than happy to upload the bin file to make it easier. Oh one last thing i changed permissions, so it should show as rw-r--r--
fmanila said:
Let me start by saying that i do not take credit, by any means for this fix, i did use the SEARCH tool and found the solution. What i'm doing is posting a faster/easier fix for the thread here http://forum.xda-developers.com/showthread.php?t=2196200
All of the help i read, is from this thread here http://forum.xda-developers.com/showthread.php?t=2102981&highlight=miui+camera.
Our common issue was that each time we flashed an AOSP ROM(for me the new MIUI PORT FROM SPRING TO SHG3 TMO) the camera wouldn't connect, and that's a deal breaker. Im sure it was for many of you. (I'm a noob, just giving a heads up, and this is why i have to post here rather than the first thread, being understandbly limited and all) As the 2nd of the two threads says, the issue is that on stock rom there is a bin file named SlimISP_ZH.bin, once flashed, it's no longer there, causing the camera to simply not connect. I odin'ed back to stock(because i didn't have access to the bin file), used ES File Explorer to "copy" the SlimISP_ZH.bin file into my external sd card, then i proceeded to flash to the MIUI ROM of my choice, after setting up the phone, using ES File Explorer again, i placed the bin file on the /data directory. If a mod can confirm it's ok, i'll be more than happy to upload the bin file to make it easier. Oh one last thing i changed permissions, so it should show as rw-r--r--
Click to expand...
Click to collapse
How do you change permissions? Do I need to be rooted? Do I need busybox?
dbwlaw said:
How do you change permissions? Do I need to be rooted? Do I need busybox?
Click to expand...
Click to collapse
Yes you need to be rooted. No you do not need busybox. Use ES File Explorer. Better yet, try Fix Permissions in Custom Recovery.
file
can you please provide me the file
email: [email protected]
I just switched from my M7 to the M8 yesterday. I was excited to have the external SD for saving pictures, moving apps, but mostly to host my backups. I have since unlocked my bootloader and rooted the device. Unfortunately I'm unable to write any back ups through TWRP to the card. I was wondering if anyone found any fixes? I've already tried SDFix but it seems not to work with our device. Any help would be appreciated!
Sidenote: I know this probably belongs under development but I'm unable to post yet as my post count is too low. Thanks again!
iNiREALiZED said:
I just switched from my M7 to the M8 yesterday. I was excited to have the external SD for saving pictures, moving apps, but mostly to host my backups. I have since unlocked my bootloader and rooted the device. Unfortunately I'm unable to write any back ups through TWRP to the card. I was wondering if anyone found any fixes? I've already tried SDFix but it seems not to work with our device. Any help would be appreciated!
Sidenote: I know this probably belongs under development but I'm unable to post yet as my post count is too low. Thanks again!
Click to expand...
Click to collapse
You will need to edit platform.xml file in/system/etc. Are you comfortable ?
I'm not sure. If there was a tutorial that was available I could possibly follow it. Otherwise is this something that could be included in future rom builds? I wouldn't mind waiting.
Sent from my HTC One_M8 using xda app-developers app
iNiREALiZED said:
I'm not sure. If there was a tutorial that was available I could possibly follow it. Otherwise is this something that could be included in future rom builds? I wouldn't mind waiting.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Look for nextapp's SDFix in the play store.. Root and system write protection off is required. It basically edits the file for you (also backs up the original)
silentvisitor said:
You will need to edit platform.xml file in/system/etc. Are you comfortable ?
Click to expand...
Click to collapse
Could you detail the edits for reference anyway please? I'll need to know shortly too.
graffixnyc said:
Look for nextapp's SDFix in the play store.. Root and system write protection off is required. It basically edits the file for you (also backs up the original)
Click to expand...
Click to collapse
The app worked for me!
graffixnyc said:
Look for nextapp's SDFix in the play store.. Root and system write protection off is required. It basically edits the file for you (also backs up the original)
Click to expand...
Click to collapse
Thanks for the help. I tried sdfix this morning. It kept failing and rebooting. I'm rooted but if you could explain how I turn write protection off that would be awesome!
iNiREALiZED said:
Thanks for the help. I tried sdfix this morning. It kept failing and rebooting. I'm rooted but if you could explain how I turn write protection off that would be awesome!
Click to expand...
Click to collapse
the quick way? go to the module thread in Original development and follow the instructions. You'll have to do it at every boot though unless you're on a rom that supports init.d support. If you're on stock I made a guide to disable it on boot automatically without init.d support
My guide: http://forum.xda-developers.com/showthread.php?t=2702575
graffixnyc said:
the quick way? go to the module thread in Original development and follow the instructions. You'll have to do it at every boot though unless you're on a rom that supports init.d support. If you're on stock I made a guide to disable it on boot automatically without init.d support
My guide: http://forum.xda-developers.com/showthread.php?t=2702575
Click to expand...
Click to collapse
Sorry if I'm missing something totally obvious. I went and read the thread. I download the file with extension .ko. Copied it to root of internal memory. Opened up terminal app and typed "sh" then used command "insmod /storage/sdcard0/wp_mod.ko"
Am I missing something?
iNiREALiZED said:
Sorry if I'm missing something totally obvious. I went and read the thread. I download the file with extension .ko. Copied it to root of internal memory. Opened up terminal app and typed "sh" then used command "insmod /storage/sdcard0/wp_mod.ko"
Am I missing something?
Click to expand...
Click to collapse
su
not sh..
type su
hit enter
then type
insmod /storage/sdcard0/wp_mod.ko it wont show you any output or anything.. if it brings your back to the terminal prompt it ran right
graffixnyc said:
su
not sh..
type su
hit enter
then type
insmod /storage/sdcard0/wp_mod.ko it wont show you any output or anything.. if it brings your back to the terminal prompt it ran right
Click to expand...
Click to collapse
I tried it again using "su". I'm pretty sure that is what I used the first time as well because when I entered the command the super user prompt came up to allow access for terminal. Same results. Didn't see any confirmation. Exited app and tried running SDFix and failed again. I then followed your link to your thread and followed step by step. Got all the way to the point where I was trying to save the text document at the end and got the prompt that I could not save the file.
I'm usually pretty good at following tutorials and I'm sure I'm not skipping steps but who knows. I think this one has me defeated lol.
If you put it on your SD card try just /sdcard/wp_mod.ko
Sent from my HTC One using Tapatalk
If you run the command.. And then run it again. It will tell you it already exists that's how I figured out it ran ok..
Sent from my HTC One using Tapatalk
backfromthestorm said:
Could you detail the edits for reference anyway please? I'll need to know shortly too.
Click to expand...
Click to collapse
Sure. Here it is:
You need to make following change to platform.xml in /system/etc.
Add <group gid="Media_rw"/> under WRITE_EXTERNAL_STORAGE and WRITE_MEDIA_STORAGE(or similar).
Save. Set Permission to rw-r-r or 644.
Reboot and Enjoy
Good luck :good:
silentvisitor said:
Sure. Here it is:
You need to make following change to platform.xml in /system/etc.
Add <group gid="Media_rw"/> under WRITE_EXTERNAL_STORAGE and WRITE_MEDIA_STORAGE(or similar).
Save. Set Permission to rw-r-r or 644.
Reboot and Enjoy
Good luck :good:
Click to expand...
Click to collapse
Well I ran through both tutorials (yours and the others) once again. Entered the command twice to confirm and got the message "failed file already exists". So I'm assuming that part went through fine but still unable to run SDFix successfully or edit the install_recovery.sh file. Wouldn't allow me to save through es text edit or the standard one.
So now I'm trying to manually change the platform.xml file. When I navigate to system/etc I don't see any file named "platform.xml". Also tried a search through es file explorer and couldn't find any file. Any thoughts?
iNiREALiZED said:
Well I ran through both tutorials (yours and the others) once again. Entered the command twice to confirm and got the message "failed file already exists". So I'm assuming that part went through fine but still unable to run SDFix successfully or edit the install_recovery.sh file. Wouldn't allow me to save through es text edit or the standard one.
So now I'm trying to manually change the platform.xml file. When I navigate to system/etc I don't see any file named "platform.xml". Also tried a search through es file explorer and couldn't find any file. Any thoughts?
Click to expand...
Click to collapse
My apologies.
Its /system/etc/Permission/platform.xml
iNiREALiZED said:
Well I ran through both tutorials (yours and the others) once again. Entered the command twice to confirm and got the message "failed file already exists". So I'm assuming that part went through fine but still unable to run SDFix successfully or edit the install_recovery.sh file. Wouldn't allow me to save through es text edit or the standard one.
So now I'm trying to manually change the platform.xml file. When I navigate to system/etc I don't see any file named "platform.xml". Also tried a search through es file explorer and couldn't find any file. Any thoughts?
Click to expand...
Click to collapse
Are you mounting it as r/w in the file explorer? It doesn't seem like you're doing that. I know the module works.. You can't just install the module and it's magically writable.. you still have to make it r/w in a file explorer before you make any changes. I don't use es. I use root explorer and there is a r/w button on top.
graffixnyc said:
Are you mounting it as r/w in the file explorer? It doesn't seem like you're doing that. I know the module works.. You can't just install the module and it's magically writable.. you still have to make it r/w in a file explorer before you make any changes. I don't use es. I use root explorer and there is a r/w button on top.
Click to expand...
Click to collapse
Wow. Excuse my ignorance. I wasn't doing that. I downloaded root explorer and used the button to mount as you mentioned and viola I was able to save the edits! I'm now able to create folders on the ext SD. Still get an error when trying to backup from twrp but I guess that's an issue for another day.
I really appreciate all the help!
iNiREALiZED said:
Wow. Excuse my ignorance. I wasn't doing that. I downloaded root explorer and used the button to mount as you mentioned and viola I was able to save the edits! I'm now able to create folders on the ext SD. Still get an error when trying to backup from twrp but I guess that's an issue for another day.
I really appreciate all the help!
Click to expand...
Click to collapse
As of now recovery doesn't support exfat formatted cards, If your sd card is formatted as exfat it will fail in recovery. You need to either format your external sd card to fat32 or just wait until the recovery is updated to support exfat. It will once they get kernel source code
graffixnyc said:
As of now recovery doesn't support exfat formatted cards, If your sd card is formatted as exfat it will fail in recovery. You need to either format your external sd card to fat32 or just wait until the recovery is updated to support exfat. It will once they get kernel source code
Click to expand...
Click to collapse
How far out do you think that is? I was figuring I could just get a cheaper card for my backups. Only thing is if I remember correctly Fat32 only supports up to 4GB files correct? I remember my backups being a tad over that so getting another card might not even make a difference.
Hi - I'm desperately hoping someone can help....
In the process of endeavouring to enable RW access to my UK HTC One M8 (O2) I've sucessfully rooted and installed the SDFix from Next App in the hope that it would perform the necessary mod to the platform.xml file in /system/etc/permissions but it failed because it didn't recognise the file as xml.
I've checked into it and I can see that the file itself has become corrupt and is full of spurious korean (probably) text.
I'm desperately hoping someone would please email me a copy of their platform.xml file so I can overwrite this corrupt one as I don't dare switch my phone off until it has a chance of booting.
I've looked for a copy of the stock ROM but cannot see the wood for the trees.
I imagine the file from any HTC One M8 variant will do - certainly any viable platform.xml file would be better than a file full of garbage, although ideally for the UK model would probably be wise.
my email is etherkeiffer at the google email domain thanks in anticipation guys!
p.s. I appreciate this is kind of dev related but I don't have enough posts to post in that forum and this is so urgent as I don't dare switch my phone off for fear of bricking it
kw1mx5 said:
Hi - I'm desperately hoping someone can help....
In the process of endeavouring to enable RW access to my UK HTC One M8 (O2) I've sucessfully rooted and installed the SDFix from Next App in the hope that it would perform the necessary mod to the platform.xml file in /system/etc/permissions but it failed because it didn't recognise the file as xml.
I've checked into it and I can see that the file itself has become corrupt and is full of spurious korean (probably) text.
I'm desperately hoping someone would please email me a copy of their platform.xml file so I can overwrite this corrupt one as I don't dare switch my phone off until it has a chance of booting.
I've looked for a copy of the stock ROM but cannot see the wood for the trees.
I imagine the file from any HTC One M8 variant will do - certainly any viable platform.xml file would be better than a file full of garbage, although ideally for the UK model would probably be wise.
my email is etherkeiffer at the google email domain thanks in anticipation guys!
p.s. I appreciate this is kind of dev related but I don't have enough posts to post in that forum and this is so urgent as I don't dare switch my phone off for fear of bricking it
Click to expand...
Click to collapse
Now resolved, with thanks! Please close thread / delete
kw1mx5 said:
Now resolved, with thanks! Please close thread / delete
Click to expand...
Click to collapse
What was your fix?
brent372 said:
What was your fix?
Click to expand...
Click to collapse
A member (name withheld to respect his privacy) kindly emailed the relevant file.
kw1mx5 said:
A member (name withheld to respect his privacy) kindly emailed the relevant file.
Click to expand...
Click to collapse
I think you would have been fine restarting. If you're rooted and not S-Off it would revert all changes on reboot, like you never touched platform.xml at all.
Xdpker06 said:
I think you would have been fine restarting. If you're rooted and not S-Off it would revert all changes on reboot, like you never touched platform.xml at all.
Click to expand...
Click to collapse
yes - I'm sure you're right but I just didn't want to take any chances as I'm mostly a stock user and only root and make changes where I consider it absolutely essential so I don't have much experience (in case it doesn't show ).
With my previous Galaxy S2 that was both essential and the changes (removals) quite substantial - it's amazing how much crap Samsung were cramming on handsets, even a couple of years ago.
kw1mx5 said:
yes - I'm sure you're right but I just didn't want to take any chances as I'm mostly a stock user and only root and make changes where I consider it absolutely essential so I don't have much experience (in case it doesn't show ).
With my previous Galaxy S2 that was both essential and the changes (removals) quite substantial - it's amazing how much crap Samsung were cramming on handsets, even a couple of years ago.
Click to expand...
Click to collapse
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the new (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. how can i reset the xml files on my phone..
Since I experience the same issue as the thread starter (just with a German HTC One M8) I would really appreciate to get a clean version of the platform.xml file also.
Thanks!
EDIT: I don't need the file anymore. For some reason it looked fine again after another couple of reboots. I have no idea what went wrong here...
Did you make your SD card writable to apps?
If yes, how?
Right now I'm on rooted One M8 from t-mobile. All those SDfix apps from Play Store do not work.
Sn8kbordin said:
Did you make your SD card writable to apps?
If yes, how?
...
Click to expand...
Click to collapse
Well, it's not really necessary to use any tools. They didn't work for me also, so I used this description (Method 1):
http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/
You just need to add one line in the mentioned xml-file. That's it...
bama35453 said:
Well, it's not really necessary to use any tools. They didn't work for me also, so I used this description (Method 1):
http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/
You just need to add one line in the mentioned xml-file. That's it...
Click to expand...
Click to collapse
Thank you.
When I edit the platform.xml with ES File Explorer and save it, it goes back to stock on reboot.
I tried to copy that file, edit in new location, save, and then:
1. When I overwrite platform.xml with ES File Explorer phone reboots and stock file is back
2. When I delete stock platform.xml to copy modified file in its place phone reboots and stock file is back.
Sn8kbordin said:
Thank you.
When I edit the platform.xml with ES File Explorer and save it, it goes back to stock on reboot.
I tried to copy that file, edit in new location, save, and then:
1. When I overwrite platform.xml with ES File Explorer phone reboots and stock file is back
2. When I delete stock platform.xml to copy modified file in its place phone reboots and stock file is back.
Click to expand...
Click to collapse
Well, you're right. I ran into that issue also. Finally I think I found a solution more or less by accident:
I moved the platform.xml to /data/data
• Boot in recovery mode
• Mount system*and*data
• Start ADB shell (on a Windows PC cmd: “adb.exe shell”)
• Type the following commands:
1 cd /system/etc/permissions
2 mv platform.xml /data/data
3 ln -s /data/data/platform.xml platform.xml
4 exit
Reboot phone and do the necessary changes to the platform.xml file:
1 Using a root-enabled file manager navigate to /data/data
2 Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3 Add an additional line containing the group definition for this permission: <group gid=”media_rw” />
4 Save the changes to the file.
5 Restart the phone.
Once done I moved the file back:
• Boot in recovery mode
• Mount system*and*data
• Start ADB shell (on a Windows PC cmd: “adb.exe shell”)
• Type the following commands:
1 cd /data/data
2 mv platform.xml /system/etc/permissions
3 exit
After that the changed file survived several reboots so far.
As always: If you also try it that way - it's on your own risk...
The following fixed apps write access to the SD card on my rooted (I followed this to root my phone http://forum.xda-developers.com/showthread.php?t=2066390 ) HTC One M8 from T-Mobile (Android 4.4.2, Sense 6.0) with TWRP recovery:
1. Copy platform.xml from /system/etc/permissions to SD card or internal memory with ES File Explorer or any other way.
2. Open copied platform.xml in new location and edit it according to http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/ (Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission. Add an additional group definition for this permission: <group gid=”media_rw” />)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Save the changes to the file.
4. Turn phone off.
5. Press and hold volume down and power buttons to boot into TWRP recovery.
6. Press volume down until "recovery" is highlighted, then press power button to boot into recovery.
7. Back up your phone before proceeding just in case something goes wrong.
8. In TWRP recovery mount system partition. This took me a while to figure it out as otherwise you can't find and overwrite stock platform.xml in /system/etc/permissions and it is not mounted by default.
9. In TWRP recovery go to advanced and copy the platform.xml from location you saved the edited copy to /system/etc/permissions and overwrite the stock platform.xml with edited copy.
10. Reboot
11. Apps have write access to SD card and SD is fixed.
Me too
Can someone email me the platform.xml file from an HTC one m8 please
my email is nickbruton at gmaildotcom
kw1mx5 said:
Hi - I'm desperately hoping someone can help....
In the process of endeavouring to enable RW access to my UK HTC One M8 (O2) I've sucessfully rooted and installed the SDFix from Next App in the hope that it would perform the necessary mod to the platform.xml file in /system/etc/permissions but it failed because it didn't recognise the file as xml.
I've checked into it and I can see that the file itself has become corrupt and is full of spurious korean (probably) text.
I'm desperately hoping someone would please email me a copy of their platform.xml file so I can overwrite this corrupt one as I don't dare switch my phone off until it has a chance of booting.
I've looked for a copy of the stock ROM but cannot see the wood for the trees.
I imagine the file from any HTC One M8 variant will do - certainly any viable platform.xml file would be better than a file full of garbage, although ideally for the UK model would probably be wise.
my email is etherkeiffer at the google email domain thanks in anticipation guys!
p.s. I appreciate this is kind of dev related but I don't have enough posts to post in that forum and this is so urgent as I don't dare switch my phone off for fear of bricking it
Click to expand...
Click to collapse
Help please
Dont need the platform.xml file, but after changing mine, I rebooted and lots of services failed, titanium backup crashes with Unfortunatley Titanium Backup has stopped.
adb doesnt seem to want to work anymore, can anyone help?
---------- Post added at 01:07 PM ---------- Previous post was at 12:38 PM ----------
What is the correct access mode on /system/etc/permissions/platform.xml ??
Sn8kbordin said:
The following fixed apps write access to the SD card on my rooted (I followed this to root my phone http://forum.xda-developers.com/showthread.php?t=2066390 ) HTC One M8 from T-Mobile (Android 4.4.2, Sense 6.0) with TWRP recovery:
1. Copy platform.xml from /system/etc/permissions to SD card or internal memory with ES File Explorer or any other way.
2. Open copied platform.xml in new location and edit it according to http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/ (Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission. Add an additional group definition for this permission: <group gid=”media_rw” />)
3. Save the changes to the file.
4. Turn phone off.
5. Press and hold volume down and power buttons to boot into TWRP recovery.
6. Press volume down until "recovery" is highlighted, then press power button to boot into recovery.
7. Back up your phone before proceeding just in case something goes wrong.
8. In TWRP recovery mount system partition. This took me a while to figure it out as otherwise you can't find and overwrite stock platform.xml in /system/etc/permissions and it is not mounted by default.
9. In TWRP recovery go to advanced and copy the platform.xml from location you saved the edited copy to /system/etc/permissions and overwrite the stock platform.xml with edited copy.
10. Reboot
11. Apps have write access to SD card and SD is fixed.
Click to expand...
Click to collapse
For those of us who use CWM / Philz, you can also mount system and do it over adb shell.
blondini said:
Can someone email me the platform.xml file from an HTC one m8 please
my email is nickbruton at gmaildotcom
Click to expand...
Click to collapse
Here is my modified platform.xml file from T-Mobile HTC One M8, Android 4.4.2
Looking to do an OTA update so I need the original unedited platform.xml file. I have tried manually editing it back to remove the sd fix (which worked), but the update still does not go through saying there is something wrong with the platform.xml again. If you have it please email it to me! jrsnively1 at gmail.
Thank you!
Hi
So I am looking at blocking a number of websites - no, I don't really want to do this through app's as a mere uninstall can undo the blocks.
I've rooted my phone, I've given +rw mount to /system/ and I'm able to etc hosts under /system/etc/hosts just fine.
However, as soon as I reboot, the system restores the hosts file to it's original state and all my edits to that file are undone.
Is there anything I can do about this? Please be a bit more specific than just "flash the kernel", thanks.
MohamedH93 said:
Hi
So I am looking at blocking a number of websites - no, I don't really want to do this through app's as a mere uninstall can undo the blocks.
I've rooted my phone, I've given +rw mount to /system/ and I'm able to etc hosts under /system/etc/hosts just fine.
However, as soon as I reboot, the system restores the hosts file to it's original state and all my edits to that file are undone.
Is there anything I can do about this? Please be a bit more specific than just "flash the kernel", thanks.
Click to expand...
Click to collapse
any time i edit anything in system folders i copy it to sdcard do my edits then copy it back and make sure the permissions are set correct i think it rw-r--r-- reboot and it should be good to go... for some reason i cant edit them in that folder but moving it to edit then move it back works for me maybe it will work for you too...
buby78 said:
any time i edit anything in system folders i copy it to sdcard do my edits then copy it back and make sure the permissions are set correct i think it rw-r--r-- reboot and it should be good to go... for some reason i cant edit them in that folder but moving it to edit then move it back works for me maybe it will work for you too...
Click to expand...
Click to collapse
I can edit it no probs. I do my changes, test them out and they all work OK.
As soon as I reboot, everything becomes undone. AFAIK this might be some kernel protection.
The system partition is write-protected.
http://forum.xda-developers.com/showthread.php?t=2701816
I am assuming the apps in priv-app below are Carrier IQ....can I just delete these apps and have no problems?
Code:
IQ-tmobile-release-unsigned.signed.apk
Code:
IQ_OOB_v1.6_forLG.signed.apk
Code:
IQToggle_v1.1.3.signed.apk
you could use root explorer and rename them to *.apk.bak to test out. I plan to do this sometime tonight once I get done setting up my phone again.
also delete these files:
libiq.* (forgot the name and forgot to write it down)
com.carrierirq.tmobile
com.carrierir.tmobile.iqoob
com.carrieriq.tmobile.iqtoggle
there multiple copy of these files in different directories so do a search for "com.carrieriq.tmobile" to find them all
but there is more
This is for LG G3 only
I am not responsible if you brick your phone and you MUST have root access and here’s what I did to remove Carrier IQ from my LG G3
I used root explorer to go to the /system/priv-app folder and renamed the files below to .bak
IQ-tmobile-release-unsigned.signed.apk renamed to IQ-tmobile-release-unsigned.signed.apk.bak
IQ-tmobile-release-unsigned.signed.odex.apk renamed IQ-tmobile-release-unsigned.signed.odex.apk.bak
IQToggle_v1.1.3.signed.apk renamed IQToggle_v1.1.3.signed.apk.bak
IQToggle_v1.1.3.signed.odex.apk renamed IQToggle_v1.1.3.signed.odex.apk.bak
IQ_OOB_v1.6_forLG.signed.apk renamed IQ_OOB_v1.6_forLG.signed.apk.bak
IQ_OOB_v1.6_forLG.signed.odex.apk renamed IQ_OOB_v1.6_forLG.signed.odex.apk.bak
Then went into the /data/data folder and also renamed the folders below with a .bak
com.carrieriq.tmobile renamed com.carrieriq.tmobile.bak
com.carrieriq.tmobile.IQOOB renamed com.carrieriq.tmobile.IQOOB.bak
Just a quick edit as I ran multiple CIQ detecting apps and found services still running and traced them back to:
/system/app
LTDDM.apk renamed LTDDM.apk.bak
LTDDM.odex renamed LTDDM.odex.bak
/system/lib/
libiq_service_tmobile_2.2.so renamed libiq_service_tmobile_2.2.so.bak and created a backup folder and moved it there
After these steps, no more services detected.
Rebooted and tested with different CIQ detectors and none were found.
Hope this helps someone and good luck
Goodbye Caller IQ!
vicvega said:
This is for LG G3 only
I am not responsible if you brick your phone and you MUST have root access and here’s what I did to remove Carrier IQ from my LG G3
I used root explorer to go to the /system/priv-app folder and renamed the files below to .bak
IQ-tmobile-release-unsigned.signed.apk renamed to IQ-tmobile-release-unsigned.signed.apk.bak
IQ-tmobile-release-unsigned.signed.odex.apk renamed IQ-tmobile-release-unsigned.signed.odex.apk.bak
IQToggle_v1.1.3.signed.apk renamed IQToggle_v1.1.3.signed.apk.bak
IQToggle_v1.1.3.signed.odex.apk renamed IQToggle_v1.1.3.signed.odex.apk.bak
IQ_OOB_v1.6_forLG.signed.apk renamed IQ_OOB_v1.6_forLG.signed.apk.bak
IQ_OOB_v1.6_forLG.signed.odex.apk renamed IQ_OOB_v1.6_forLG.signed.odex.apk.bak
Then went into the /data/data folder and also renamed the folders below with a .bak
com.carrieriq.tmobile renamed com.carrieriq.tmobile.bak
com.carrieriq.tmobile.IQOOB renamed com.carrieriq.tmobile.IQOOB.bak
Just a quick edit as I ran multiple CIQ detecting apps and found services still running and traced them back to:
/system/app
LTDDM.apk renamed LTDDM.apk.bak
LTDDM.odex renamed LTDDM.odex.bak
/system/lib/
libiq_service_tmobile_2.2.so renamed libiq_service_tmobile_2.2.so.bak and created a backup folder and moved it there
After these steps, no more services detected.
Rebooted and tested with different CIQ detectors and none were found.
Hope this helps someone and good luck
Click to expand...
Click to collapse
This worked for me, thanks!!!!!
-J
The third poster's procedure worked for me too.
On my system there were three IQ related folders in the data/data folder rather than two. So keep an eye open there.
As added precaution (aka "paranoia") I created a new folder in each location called "Folder-bak" and placed the backed up files in there.
Rebooted, tested, and clean!
Probably it's ok to just delete all these files but it's better to be safe.
@Cablespider has a script to delete CarrierIQ here. Give him a "thanks" if you use it.
VV00DY said:
The third poster's procedure worked for me too.
On my system there were three IQ related folders in the data/data folder rather than two. So keep an eye open there.
As added precaution (aka "paranoia") I created a new folder in each location called "Folder-bak" and placed the backed up files in there.
Rebooted, tested, and clean!
Probably it's ok to just delete all these files but it's better to be safe.
Click to expand...
Click to collapse
I also had the third folder. Thanks for the heads-up.
Herb.Grinda said:
I also had the third folder. Thanks for the heads-up.
Click to expand...
Click to collapse
I didn't have as many files but still worked thank you
vicvega said:
This is for LG G3 only
I am not responsible if you brick your phone and you MUST have root access and here’s what I did to remove Carrier IQ from my LG G3
I used root explorer to go to the /system/priv-app folder and renamed the files below to .bak
IQ-tmobile-release-unsigned.signed.apk renamed to IQ-tmobile-release-unsigned.signed.apk.bak
IQ-tmobile-release-unsigned.signed.odex.apk renamed IQ-tmobile-release-unsigned.signed.odex.apk.bak
IQToggle_v1.1.3.signed.apk renamed IQToggle_v1.1.3.signed.apk.bak
IQToggle_v1.1.3.signed.odex.apk renamed IQToggle_v1.1.3.signed.odex.apk.bak
IQ_OOB_v1.6_forLG.signed.apk renamed IQ_OOB_v1.6_forLG.signed.apk.bak
IQ_OOB_v1.6_forLG.signed.odex.apk renamed IQ_OOB_v1.6_forLG.signed.odex.apk.bak
Then went into the /data/data folder and also renamed the folders below with a .bak
com.carrieriq.tmobile renamed com.carrieriq.tmobile.bak
com.carrieriq.tmobile.IQOOB renamed com.carrieriq.tmobile.IQOOB.bak
Just a quick edit as I ran multiple CIQ detecting apps and found services still running and traced them back to:
/system/app
LTDDM.apk renamed LTDDM.apk.bak
LTDDM.odex renamed LTDDM.odex.bak
/system/lib/
libiq_service_tmobile_2.2.so renamed libiq_service_tmobile_2.2.so.bak and created a backup folder and moved it there
After these steps, no more services detected.
Rebooted and tested with different CIQ detectors and none were found.
Hope this helps someone and good luck
Click to expand...
Click to collapse
Thanks for this. I used this as a guide to rename the files instead of deleting them ala Cablespider style!
VV00DY said:
The third poster's procedure worked for me too.
On my system there were three IQ related folders in the data/data folder rather than two. So keep an eye open there.
As added precaution (aka "paranoia") I created a new folder in each location called "Folder-bak" and placed the backed up files in there.
Rebooted, tested, and clean!
Probably it's ok to just delete all these files but it's better to be safe.
Click to expand...
Click to collapse
As suggested by VV00DY (and yeah, maybe I'm a little paranoid too!), I went ahead and made Bak folders in each location to put the renamed files in.
I also found the third file in /data/data folder and renamed it;
com.carrieriq.tmobile.IQToggle renamed com.carrieriq.tmobile.IQToggle.bak
I did notice that the original odex files mentioned above didn't end in .apk, so I simply added the .bak at the end.
vicvega said:
This is for LG G3 only
I am not responsible if you brick your phone and you MUST have root access and here’s what I did to remove Carrier IQ from my LG G3
I used root explorer to go to the /system/priv-app folder and renamed the files below to .bak
IQ-tmobile-release-unsigned.signed.apk renamed to IQ-tmobile-release-unsigned.signed.apk.bak
IQ-tmobile-release-unsigned.signed.odex.apk renamed IQ-tmobile-release-unsigned.signed.odex.apk.bak
IQToggle_v1.1.3.signed.apk renamed IQToggle_v1.1.3.signed.apk.bak
IQToggle_v1.1.3.signed.odex.apk renamed IQToggle_v1.1.3.signed.odex.apk.bak
IQ_OOB_v1.6_forLG.signed.apk renamed IQ_OOB_v1.6_forLG.signed.apk.bak
IQ_OOB_v1.6_forLG.signed.odex.apk renamed IQ_OOB_v1.6_forLG.signed.odex.apk.bak
Then went into the /data/data folder and also renamed the folders below with a .bak
com.carrieriq.tmobile renamed com.carrieriq.tmobile.bak
com.carrieriq.tmobile.IQOOB renamed com.carrieriq.tmobile.IQOOB.bak
Just a quick edit as I ran multiple CIQ detecting apps and found services still running and traced them back to:
/system/app
LTDDM.apk renamed LTDDM.apk.bak
LTDDM.odex renamed LTDDM.odex.bak
/system/lib/
libiq_service_tmobile_2.2.so renamed libiq_service_tmobile_2.2.so.bak and created a backup folder and moved it there
After these steps, no more services detected.
Rebooted and tested with different CIQ detectors and none were found.
Hope this helps someone and good luck
Click to expand...
Click to collapse
This worked great for me! A few notes/warnings for libiq_service_tmobile_2.2.so.
NOTES: I added ".bak" to it, rebooted and it still showed up in Voodoo. So I created a new folder for it, moved it there and rebooted--it still showed up in Voodoo. So I made a backup in TWRP, booted up and then deleted the file and the newly created folder using Root Explorer. Once I rebooted, it was gone from Voodoo.
WARNING: After my wife added ".bak" to the file, rebooted and saw it still showed up in Voodoo, she decided to add another ".bak" to it--so the file ended ".bak.bak". That was a bad idea. When she rebooted, her phone was stuck at the LG boot screen. Worse yet, holding volume down + power got her into recovery, but once there she was unable to restore or do anything in TWRP--and it showed there was nothing on internal memory and she was unable to access her SD card. Following these steps (http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html) she was able to install stock again and thus have a working phone. [As we discussed the problem, she kept on saying ".bac" so it's possible that in addition to the ".bak.bak" change, she may have changed one of the other carrier IQ file names to ".bac". I'm not sure how these would have caused a soft brick, but they are the only differences between my successful removal of carrier IQ on my G3 and her experience of soft bricking hers.]
thepza said:
This worked great for me! A few notes/warnings for libiq_service_tmobile_2.2.so.
NOTES: I added ".bak" to it, rebooted and it still showed up in Voodoo. So I created a new folder for it, moved it there and rebooted--it still showed up in Voodoo. So I made a backup in TWRP, booted up and then deleted the file and the newly created folder using Root Explorer. Once I rebooted, it was gone from Voodoo.
WARNING: After my wife added ".bak" to the file, rebooted and saw it still showed up in Voodoo, she decided to add another ".bak" to it--so the file ended ".bak.bak". That was a bad idea. When she rebooted, her phone was stuck at the LG boot screen. Worse yet, holding volume down + power got her into recovery, but once there she was unable to restore or do anything in TWRP--and it showed there was nothing on internal memory and she was unable to access her SD card. Following these steps (http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html) she was able to install stock again and thus have a working phone. [As we discussed the problem, she kept on saying ".bac" so it's possible that in addition to the ".bak.bak" change, she may have changed one of the other carrier IQ file names to ".bac". I'm not sure how these would have caused a soft brick, but they are the only differences between my successful removal of carrier IQ on my G3 and her experience of soft bricking hers.]
Click to expand...
Click to collapse
It so much easier to use the zip file. Once you have phone set up flash the zip and correct files get deleted.
BAD ASS G3
BACARDILIMON said:
It so much easier to use the zip file. Once you have phone set up flash the zip and correct files get deleted.
BAD ASS G3
Click to expand...
Click to collapse
You're referring to Cablespider's script?
thepza said:
You're referring to Cablespider's script?
Click to expand...
Click to collapse
Yes sir. Works great
BAD ASS G3
Also works on the F60
This also works on the MetroPCS version of the F60, with no modifications. I have adapted the instructions, (including giving proper credit), to work on the ZTE ZMAX (Z970), here:
http://forum.xda-developers.com/showpost.php?p=61242177&postcount=3300
and here:
http://androidforums.com/threads/carrier-iq.922016/
Thanks!