I'm sorry if this was posted somewhere else, but I searched and nothing came up. When you root your phone does that mean you no longer can receive over the air updates? Or is that only if you have custom ROM's installed? That being said, is the ROM that you install to gain root access considered a custom ROM? Sorry... I feel like a n00b but I had to ask. :] Thanks
Trevlo said:
I'm sorry if this was posted somewhere else, but I searched and nothing came up. When you root your phone does that mean you no longer can receive over the air updates? Or is that only if you have custom ROM's installed? That being said, is the ROM that you install to gain root access considered a custom ROM? Sorry... I feel like a n00b but I had to ask. :] Thanks
Click to expand...
Click to collapse
Originally Posted by WormDoes
http://androidforums.com/thunderbolt-all-things-root/306774-simple-newbie-questions.html
"If you're rooted and you've deleted any bloatware and you try and install the ota update it will not update successfully. You can unroot and update, but be warned a lot of the time an ota update will also correct the current exploits that were used to achieve root access. If you are rooted it's usually a good idea and easier to flash a ROM that includes the update already. The developers get a hold of the source codes a few weeks before VZW actually pushes it to your phone and you don't have to wait for jcase, unrevoked, or whomever to find a new way to root if the ota breaks root access.
Hope this helps"
I was searching the same thing earlier bro and this is the answer I found.
Does this mean if I don't delete bloatware and just freeze it, then I can still get the updates? I read that article and I didn't see them answer whether or not getting an OTA update would take root off. Thanks for the response!
Sent from my ADR6400L using XDA Premium App
Trevlo said:
Does this mean if I don't delete bloatware and just freeze it, then I can still get the updates? I read that article and I didn't see them answer whether or not getting an OTA update would take root off. Thanks for the response!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
No the point is if you root, have SU, and/or a custom recovery, the update will fail.
Sent from my ADR6400L using XDA Premium App
Good deal. Thank you for the info.
Sent from my ADR6400L using XDA Premium App
So if I'm reading this correctly, a corollary is that if you intend to root but haven't, its likely a good idea to do it before the OTA is pushed, or else you'll have to wait for the developers to figure out how to root the new one?
Sent from my ADR6400L using XDA App
More then likely any important updates/fixes/etc will turn up in ROMs anyways.
so how do you disable updates?
Nikolai2.1 said:
No the point is if you root, have SU, and/or a custom recovery, the update will fail.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
so how do you disable updates I have a galaxy s2 4g service sprint I ve been searching around how to disable updates I keep getting prompt for one and it wont install root blocking it from installing I guess I just want to turn it of I read use bloat ware or titanum backup tried both same issue. I thought this would be an easy fix.
arcolino1 said:
so how do you disable updates I have a galaxy s2 4g service sprint I ve been searching around how to disable updates I keep getting prompt for one and it wont install root blocking it from installing I guess I just want to turn it of I read use bloat ware or titanum backup tried both same issue. I thought this would be an easy fix.
Click to expand...
Click to collapse
try this it works
only difference for you will be lines 4 and 5
look for your current ro.build.fingerprint and change it to the current update...
oh and also don't forget to delete the update from your cache
If you are comfortable editing the build.prop then follow these directions.
Directions:
1. Use root explorer and navigate to /system
2. Mount as r/w
3. Long press on build.prop then click on Open With then Text Editor
4. Find the line ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP1:user/release-keys
5. Change FP1 or FP5 in that line to FP8
6. Press the menu button on the phone and click on Save and Exit
7. Mount back to r/o
8. Reboot phone
cujo6801 said:
try this it works
only difference for you will be lines 4 and 5
look for your current ro.build.fingerprint and change it to the current update...
oh and also don't forget to delete the update from your cache
If you are comfortable editing the build.prop then follow these directions.
Directions:
1. Use root explorer and navigate to /system
2. Mount as r/w
3. Long press on build.prop then click on Open With then Text Editor
4. Find the line ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP1:user/release-keys
5. Change FP1 or FP5 in that line to FP8
6. Press the menu button on the phone and click on Save and Exit
7. Mount back to r/o
8. Reboot phone
Click to expand...
Click to collapse
I attached the file for more info.
mine reads:
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FI27:user/release-keys
do I change the FI to something else? if so this change will not brick my phone? this is my only cell connection to outside world.
the download system update that wants to install is a FL24 is it because the phone knows FI the FL will not install?
You could just rename otacerts to otacerts.bak and then rename updater.apk to updater.bak.
Sent from my personally built from source CM10.1 N7.
arcolino1 said:
I attached the file for more info.
mine reads:
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FI27:user/release-keys
do I change the FI to something else? if so this change will not brick my phone? this is my only cell connection to outside world.
the download system update that wants to install is a FL24 is it because the phone knows FI the FL will not install?
Click to expand...
Click to collapse
Yes change the FI27 to FL24
Should do it for you..
Disclaimer.. I don't know your phone but this has worked for me and many others on the Samsung charge...
I don't think it will brick your phone..
Make sure you have a backup .
SENT FROM THE DOG POUND
cujo6801 said:
Yes change the FI27 to FL24
Should do it for you..
Disclaimer.. I don't know your phone but this has worked for me and many others on the Samsung charge...
I don't think it will brick your phone..
Make sure you have a backup .
SENT FROM THE DOG POUND
Click to expand...
Click to collapse
what additional info do you need from my phone, that will make this a more sure ok to do for sure no worries ? what about
what disconnecktie recommended "You could just rename otacerts to otacerts.bak and then rename updater.apk to updater.bak"
is that safer, not sure where to find those files? I am doing titanium back. but i do not want to go through the hassel of reloading everything back on the phone.
Either way will work but the otacerts and updater both just catch ota information when it is sent out. You aren't deleting anything so it is impossible to brick from it. The otacerts is in /system/etc and the updater apk is in /system/app or course. Use a root file explorer like es file explorer and mount system as read/write.
Sent from my personally built from source CM10.1 N7.
disconnecktie said:
Either way will work but the otacerts and updater both just catch ota information when it is sent out. You aren't deleting anything so it is impossible to brick from it. The otacerts is in /system/etc and the updater apk is in /system/app or course. Use a root file explorer like es file explorer and mount system as read/write.
Sent from my personally built from source CM10.1 N7.
Click to expand...
Click to collapse
so do I wait to see the update icon? then do the process
and to be clear the process is?
go to /system/etc then rename otacerts to otacerts.bak save it
then go to /system/app then rename update.apk to update.bak save it
how long does that change last if they are pushing the update wont it just come right back?
arcolino1 said:
so do I wait to see the update icon? then do the process
and to be clear the process is?
go to /system/etc then rename otacerts to otacerts.bak save it
then go to /system/app then rename update.apk to update.bak save it
how long does that change last if they are pushing the update wont it just come right back?
Click to expand...
Click to collapse
They won't be able to push it anymore after that. Change it then reboot and they can't send then to you anymore.
Sent from my personally built from source CM10.1 N7.
What he said...
SENT FROM THE DOG POUND
disconnecktie said:
They won't be able to push it anymore after that. Change it then reboot and they can't send then to you anymore.
Sent from my personally built from source CM10.1 N7.
Click to expand...
Click to collapse
ok, so to be clear I do not see the files now in those locations
otacerts and updater.apk
will I see them after the update icon comes back?
arcolino1 said:
ok, so to be clear I do not see the files now in those locations
otacerts and updater.apk
will I see them after the update icon comes back?
Click to expand...
Click to collapse
Are you using a thunderbolt? If you're not then you're in the wrong forum and should probably post your questions there.
Sent from my personally built from source CM10.1 N7.
he has a GS2....
but mine should work....
take the info to your phone section here on XDA and ask what they think...
good luck
Related
For the Atrix, what's the recommended way to disable the OEM AT&T boot animation?
And will this cause any problems - either with normal useage, or with future updates?
Rename the file extension from .zip to .backup. That will stop it from playing. I dont see why this would have a negative affect on your phone other than you will be missing a boot animation. If you ever want it back just rename the file extension back to .zip. But why not change it to something you like?
What it comes down to was that I didn't know anything about boot animations, and whether they were one of those things that would cause an OTA update to fail.
I have since learned more about how to adjust them. But there is still the question about whether it affects OTA updates.
Haphim said:
What it comes down to was that I didn't know anything about boot animations, and whether they were one of those things that would cause an OTA update to fail.
I have since learned more about how to adjust them. But there is still the question about whether it affects OTA updates.
Click to expand...
Click to collapse
Doubtful it would affect an ota, just keep a backup of the file incase you need it. However if you have the root access required to change the bootanimation and if you want to keep root access you should not accept an ota. When its time to update just come back to the forums.
Understood. Thanks.
WiredPirate said:
Doubtful it would affect an ota, just keep a backup of the file incase you need it. However if you have the root access required to change the bootanimation and if you want to keep root access you should not accept an ota. When its time to update just come back to the forums.
Click to expand...
Click to collapse
Great question, that animation was starting to bug me, especially cause start up is so long... ia this the same case for you guys?
Just to confirm, I would change bootanimation.zip to bootanimation.backup? Where ia this located exactly?
Thanks
Sent from my MB860 using XDA App
hluk said:
Great question, that animation was starting to bug me, especially cause start up is so long... ia this the same case for you guys?
Just to confirm, I would change bootanimation.zip to bootanimation.backup? Where ia this located exactly?
Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Correct. system/media
Here is a cool bootanimation modified for the atrix:
http://forum.xda-developers.com/showthread.php?t=1037561
Use Root Explorer or a similar file explorer to paste the bootanimation.zip in system/media after you rename the original.
I found a fix on XDA forums right here. Instead of 'asia' I input north-american into the gps.conf file. For those of you that don't want tolook for the file, I have supplied the gps.conf file for you to download right here. Post responses with how well this works. Works 100% of the time for me nearly instant locks on all gingerbread ROM's I put on my device.
If you are downloading my file, simply use adb to push it to /system/etc/ and you are golden.
**Warning|Disclaimer|Blah Blah**
If you brick your phone I am not responsible ... yadda yadda, ya'll know the drill.
thank you! that did solve the problems i've been having with the latest cm builds.
Wow! Thank you so much! I went from a 2+ minute lock to a <20 second lock.
I did find a method to make this adjustment simpler. I used root explorer, available in the market, then simply copied your 'gps.text' file to system/etc. I then deleted the gps.conf file and renamed gps.text to gps.conf. Finally, I rebooted and opened maps, enabled gps, and waited for a lock. Then, after I was locked I did one final reboot and behold, locked in less than 20 seconds.
So, maybe not simpler but it can all be done without adb, straight from the phone.
Nevertheless, thank you, thank you, annnnnd thank you!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Did you guys use his file or make your own? Mine already said North America but was missing the extra servers.
skulnik, is your phone s-off? I can never make that kind of change with root explorer. It acts like it did something, but it doesn't. Same with ADB if the phone is on.
I read on another thread that apparently if you are s-off, you need to go into recovery, mount system and then use adb to push the files.
I am not sure this worked for me though, once I got the file in there, nothing much changed. I used the old fix which involved putting the cm6 gpslib.so file into the system/etc folder. Using both, I seemed to get a quick lock.
I made flashable fix for myself that includes both fixes and the wifi fix (just in case) and things seem better on both CM7 and the xm rom based on CM7.
The extra servers is what made the difference for me. Glad that this is helping. I stopped using cm7 for the longest time because GPS wouldn't lock for me. I loaded the xm7 and is was so awesome I just HAD to find something to make GPS work because I rely on it all the time. Downtown San Antonio is very easy for me to get lost in and MapQuest was never reliable.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I used a different file after reading his method. However same concept of replacing the config file. I'm just rooted without s off. Another method to replace the file is to mount via clockwork and use android commander to push the file. FYI after this i now I get an accurate gps lock in under 10 seconds.
WhoWhere said:
I used a different file after reading his method... after this i now I get an accurate gps lock in under 10 seconds.
Click to expand...
Click to collapse
What file did you use or what did your file contain? Locks are still taking around a 1 min for me.
ovar said:
What file did you use or what did your file contain? Locks are still taking around a 1 min for me.
Click to expand...
Click to collapse
I used the gps.conf file for the us midwest file on this thread: http://forum.xda-developers.com/showthread.php?t=953630
WhoWhere said:
I used the gps.conf file for the us midwest file on this thread: http://forum.xda-developers.com/showthread.php?t=953630
Click to expand...
Click to collapse
Thanks a ton. Instant locks!
WhoWhere said:
I used the gps.conf file for the us midwest file on this thread: http://forum.xda-developers.com/showthread.php?t=953630
Click to expand...
Click to collapse
You just used the gps.conf file right? Nothing else?
jacewt said:
You just used the gps.conf file right? Nothing else?
Click to expand...
Click to collapse
Yep thats all I did. But you may want to use a different file based off your location if you aren't in that area of the us
WhoWhere said:
Yep thats all I did. But you may want to use a different file based off your location if you aren't in that area of the us
Click to expand...
Click to collapse
Thanks! I used the southwest file and I am getting real fast locks, even indoors. I wonder if I need to keep a northeast file for when I travel east.
Just want to make sure i get the steps right, all i have to do is unzip the .zip file, put gps.conf in platform-tools folder for android sdk, run adb and type "adb push gps.conf /system/etc/" right? It's been a while since i did any sort of work with adb, so i don't want any major goof-up.
txdeathray said:
Just want to make sure i get the steps right, all i have to do is unzip the .zip file, put gps.conf in platform-tools folder for android sdk, run adb and type "adb push gps.conf /system/etc/" right? It's been a while since i did any sort of work with adb, so i don't want any major goof-up.
Click to expand...
Click to collapse
You could do that or a more foul proof method would be to use android commander. Just mount the system in clockwork plug your phone in "assuming you already have adb, jdk etc. Installed" and push it that way. Android commander is pretty much a gui for adb... also could push it in terminal emulator if you were feeling adventurus. hope this helps. Android commander is most likely going to be the safest method for you. That way you can easily do a backup of the file. Though I would do a nandroid backup just to be safe.
WhoWhere said:
You could do that or a more foul proof method would be to use android commander. Just mount the system in clockwork plug your phone in "assuming you already have adb, jdk etc. Installed" and push it that way. Android commander is pretty much a gui for adb... also could push it in terminal emulator if you were feeling adventurus. hope this helps. Android commander is most likely going to be the safest method for you. That way you can easily do a backup of the file. Though I would do a nandroid backup just to be safe.
Click to expand...
Click to collapse
Haha thanks, definitely gonna give Android commander a try. And definitely gonna remember that nandroid backup (lol, learned it the hard way today).
txdeathray said:
Haha thanks, definitely gonna give Android commander a try. And definitely gonna remember that nandroid backup (lol, learned it the hard way today).
Click to expand...
Click to collapse
Sorry guys, no dice for me, same performance as before.... dunno why...
Sent from my T-Mobile myTouch 3G Slide using xda premium
Ekorshus said:
Sorry guys, no dice for me, same performance as before.... dunno why...
Sent from my T-Mobile myTouch 3G Slide using xda premium
Click to expand...
Click to collapse
hmm can't imagine why it would be different for you. Did you push the correct GPS file for your location & confirm that it took the change /view the file after you pushed the file/rebooted your phone?
Yeah, took the midwest file & moved it to the system/etc folder & removed the old file., did it all w/ root explorer rebooted the phone & everything... got the same performance as I did before, 2 min or so for a lock. Then consecutive, immediate locks as long as I didn't leave the maps app alone for too long.. @ one point I wound up using gpsfix to actually get a damn lock, it was so bad....
I'll just have to settle for slow locks.
Sent from my T-Mobile myTouch 3G Slide using xda premium
Ekorshus said:
Yeah, took the midwest file & moved it to the system/etc folder & removed the old file., did it all w/ root explorer rebooted the phone & everything... got the same performance as I did before, 2 min or so for a lock. Then consecutive, immediate locks as long as I didn't leave the maps app alone for too long.. @ one point I wound up using gpsfix to actually get a damn lock, it was so bad....
I'll just have to settle for slow locks.
Sent from my T-Mobile myTouch 3G Slide using xda premium
Click to expand...
Click to collapse
Hmm. I wonder if it's a hardware or driver problem. One thing I did want to note; I had tried using the latest version of root explorer to replace the file, mounting the system as write, etc prior to using adb. The result showed the file as being replaced however after rebooting to confirm changes the file was back to default. It might be worth double checking the file to confirm that the replacement actually took. If not possibly mount the system in clockwork and push the file using adb.
Hmmmmm, good call, I DID make sure to mount the system as r/w as opposed to r/o but I didn't chk to see if the file got overwritten by the system on restart (if I'm understanding you correctly?).
I'll try it again, this time using adb...
Sent from my T-Mobile myTouch 3G Slide using xda premium
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
johnwaynegacy said:
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
Click to expand...
Click to collapse
probably delete the OTA apk files in /system/app
con247 said:
probably delete the OTA apk files in /system/app
Click to expand...
Click to collapse
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
johnwaynegacy said:
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
Click to expand...
Click to collapse
I deleted those from my /system/app directory. The previous OTA did not ever come through my phone, so I think you'll be OK.
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
Good call!
instructions, pls?
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
i just did this on rezrom, thanks!
why is this file included with a custom rom?
michaelbsheldon said:
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
Click to expand...
Click to collapse
If for what ever reason you cant use root explorer and do have busybox (i think you need it) installed
It has been a really long time since I have used adb for anything, but this should work unless it denies you because system is mounted as read only.
adb shell
su
rm /filepath/file.apk
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
FabianaS said:
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
Click to expand...
Click to collapse
If you are stock unrooted, the best you can do is to say no if it asks. If for some reason it is a forced OTA, I don't think you can without staying in airplane mode.
Via Rezound using XDA Premium
Thanks, that is what I was wondering, if it asks or if it's forced? I don't remember how my past updates have been and for some reason I feel like they were forced!?!
Hi everyone just picked up this phone coming from a rezound.I'm brand new to att and I've never see this icon before,it's the one to the left of the alarm clock.I've already unlocked and rooted so if I need to edit the build prop that's not a problem.any one know what this ugly icon is?
Sent from my HTC One X+ using xda app-developers app
It's the NFC notification.
You can turn NFC off in settings and the notification goes away. Just turn it on when you want to use it.
nobnut said:
It's the NFC notification.
You can turn NFC off in settings and the notification goes away. Just turn it on when you want to use it.
Click to expand...
Click to collapse
WOW! I feel dumb now,but this is my first phone with NFC so that explains why I've never seen that before.Thanks again for your help.
Sent from my HTC One X+ using xda app-developers app
JT75 said:
WOW! I feel dumb now,but this is my first phone with NFC so that explains why I've never seen that before.Thanks again for your help.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
I had several phones with NFC and none of them showed this ugly symbol. Must be a HTC thing. The worst is that Google Wallet is anyway deactivated by AT&T. So it is pretty useless except for exchanging data with Google beam.
Does anyone know how to remove the icon from the status bar without disabling NFC?
I found a thread about disabling it on the Galaxy Note II, but it doesn't work for the One X+.
This is what you do on the Note:
"This can be edited in the feature.xml file (located in "/system/csc/feature.xml") under the NFC the Statusbaricontype should be changed from ATT to none."
Perhaps there's a similar method for us.
esiedlecki said:
Does anyone know how to remove the icon from the status bar without disabling NFC?
I found a thread about disabling it on the Galaxy Note II, but it doesn't work for the One X+.
This is what you do on the Note:
"This can be edited in the feature.xml file (located in "/system/csc/feature.xml") under the NFC the Statusbaricontype should be changed from ATT to none."
Perhaps there's a similar method for us.
Click to expand...
Click to collapse
The process isn't exactly similar, but the icon can indeed be replaced. The icon is found in the Nfc.apk package in /system/apps. Open Nfc.apk with the archive manager of your choice and replace the stat_sys_nfc_vzw.png file located in res/drawable-hdpi with an icon that is a bit more pleasing to the eye (I've opted for a transparent image myself). I've attached my modified Nfc.apk; it is from an AT&T HOX+ so I can only recommend using it with that variant (but who knows!).
mgymnop said:
I had several phones with NFC and none of them showed this ugly symbol. Must be a HTC thing. The worst is that Google Wallet is anyway deactivated by AT&T. So it is pretty useless except for exchanging data with Google beam.
Click to expand...
Click to collapse
No it's a jellybean thing I believe my friends Note 2 does this also so must new phone will show this icon
Sent from my HTC One X+ using Tapatalk 2
NasaGeek said:
The process isn't exactly similar, but the icon can indeed be replaced. The icon is found in the Nfc.apk package in /system/apps. Open Nfc.apk with the archive manager of your choice and replace the stat_sys_nfc_vzw.png file located in res/drawable-hdpi with an icon that is a bit more pleasing to the eye (I've opted for a transparent image myself). I've attached my modified Nfc.apk; it is from an AT&T HOX+ so I can only recommend using it with that variant (but who knows!).
Click to expand...
Click to collapse
Awesome! I appreciate your work on this!
I still have one question, however. I've opened and explored your apk and see your 1x1 transparent .png, and I also see how you edited the .apk.
My question is, how do you go about flashing it and replacing the stock app?
I'm runing a rooted HTC One X+, with the stock OS.
esiedlecki said:
Awesome! I appreciate your work on this!
I still have one question, however. I've opened and explored your apk and see your 1x1 transparent .png, and I also see how you edited the .apk.
My question is, how do you go about flashing it and replacing the stock app?
I'm runing a rooted HTC One X+, with the stock OS.
Click to expand...
Click to collapse
You can either use adb and the push command. Or you can use a file explorer, delete the original first, then copy the new one over. Finally set it's permissions to rwx-rxx-rxx.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
You can either use adb and the push command. Or you can use a file explorer, delete the original first, then copy the new one over. Finally set it's permissions to rwx-rxx-rxx.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Hmm...I'm using Root Browser Lite (I currently don't have access to a computer with the Android SDK installed). I deleted the original Nfc.apk, and it seems to have removed the app from the phone (or uninstalled it, I suppose), however the original .apk still appears in the /system/app/ directory according to both Root Browser Lite and OI File Manager. Furthermore, when I try to copy the modified Nfc.apk, I get a message saying that a file by that name already exists, so I just ask the phone to overwrite the existing file. It starts thinking about it for a minute or two, then says that the operation failed.
As it stands, I have the original file in the original location,albeit unistalled and no way to install it, as I get the "App was not installed" Message when I try to install it.
This may be a dumb question, but am I able to use the Terminal Emulator app to issue the adb command you suggested? If not, Do you have any other suggestions to get me out of this hole I've dug myself into?
Edit: I've succesfully moved the edited file to the correct location!!! I used ES File Explorer. However....I still can't install. I've done everything including changing the permsissions....it just won't install.
Thanks ahead of time!
esiedlecki said:
Hmm...I'm using Root Browser Lite (I currently don't have access to a computer with the Android SDK installed). I deleted the original Nfc.apk, and it seems to have removed the app from the phone (or uninstalled it, I suppose), however the original .apk still appears in the /system/app/ directory according to both Root Browser Lite and OI File Manager. Furthermore, when I try to copy the modified Nfc.apk, I get a message saying that a file by that name already exists, so I just ask the phone to overwrite the existing file. It starts thinking about it for a minute or two, then says that the operation failed.
As it stands, I have the original file in the original location,albeit unistalled and no way to install it, as I get the "App was not installed" Message when I try to install it.
This may be a dumb question, but am I able to use the Terminal Emulator app to issue the adb command you suggested? If not, Do you have any other suggestions to get me out of this hole I've dug myself into?
Edit: I've succesfully moved the edited file to the correct location!!! I used ES File Explorer. However....I still can't install. I've done everything including changing the permsissions....it just won't install.
Thanks ahead of time!
Click to expand...
Click to collapse
Did you try wiping the dalvik cache
Sent from my HTC One X+ using Tapatalk 2
esiedlecki said:
Hmm...I'm using Root Browser Lite (I currently don't have access to a computer with the Android SDK installed). I deleted the original Nfc.apk, and it seems to have removed the app from the phone (or uninstalled it, I suppose), however the original .apk still appears in the /system/app/ directory according to both Root Browser Lite and OI File Manager. Furthermore, when I try to copy the modified Nfc.apk, I get a message saying that a file by that name already exists, so I just ask the phone to overwrite the existing file. It starts thinking about it for a minute or two, then says that the operation failed.
As it stands, I have the original file in the original location,albeit unistalled and no way to install it, as I get the "App was not installed" Message when I try to install it.
This may be a dumb question, but am I able to use the Terminal Emulator app to issue the adb command you suggested? If not, Do you have any other suggestions to get me out of this hole I've dug myself into?
Edit: I've succesfully moved the edited file to the correct location!!! I used ES File Explorer. However....I still can't install. I've done everything including changing the permsissions....it just won't install.
Thanks ahead of time!
Click to expand...
Click to collapse
System apps are not meant to be installed like regular apks, just reboot the phone and the changes in the new apk should take effect (when you turn NFC on no icon should appear).
AndroHero said:
Did you try wiping the dalvik cache
Click to expand...
Click to collapse
NasaGeek said:
System apps are not meant to be installed like regular apks, just reboot the phone and the changes in the new apk should take effect (when you turn NFC on no icon should appear).
Click to expand...
Click to collapse
I've done both of those things now, and still the NFC options don't show up in the menu. It makes the menu look rather lonely.
Just wondering if any further developments have been made regarding this issue. It makes me sad every time I think about how my phone is probably one of the only HOX+s out there that's incapable of using its NFC hardware.
I know its a pain in the ass, but you could always flash a new rom
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
I know its a pain in the ass, but you could always flash a new rom
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Bleh...I think you're right. As it sits, I'll probably just live without NFC until a stable CM10 build is released for AT&T phones.
esiedlecki said:
Awesome! I appreciate your work on this!
I still have one question, however. I've opened and explored your apk and see your 1x1 transparent .png, and I also see how you edited the .apk.
My question is, how do you go about flashing it and replacing the stock app?
I'm runing a rooted HTC One X+, with the stock OS.
Click to expand...
Click to collapse
Is your One X+ an AT&T version? If it is, how did you root it? I have the phone, and I already unlocked the boot loader, but I can't find a way to root.
FilyPhanatic said:
Is your One X+ an AT&T version? If it is, how did you root it? I have the phone, and I already unlocked the boot loader, but I can't find a way to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994961
That's the easiest way to go about it.
I hope it helps.
P.S. I personally don't mind, but you should probably start with the search bar, otherwise you may end up getting berated by other forum users.
esiedlecki said:
Just wondering if any further developments have been made regarding this issue. It makes me sad every time I think about how my phone is probably one of the only HOX+s out there that's incapable of using its NFC hardware.
Click to expand...
Click to collapse
Here are the original apk and odex files if you want to give them a try (just to get functional NFC back for when you need it).
Edit: xda tells me the odex is an invalid file, here's a dropbox link instead https://www.dropbox.com/s/cpb87mar7eipjdd/Nfc.odex
NasaGeek said:
Here are the original apk and odex files if you want to give them a try (just to get functional NFC back for when you need it).
Edit: xda tells me the odex is an invalid file, here's a dropbox link instead https://www.dropbox.com/s/cpb87mar7eipjdd/Nfc.odex
Click to expand...
Click to collapse
I very much appreciate the sentiment! I, however was sure to leave a copy, untouched, of the original .apk and .odex on my sd card.
I did indeed try the copies you provided to no avail.
A reflash is looking more and more imminent...
ES file explorer isn't mounting system as writeable. Can't copy any file to system or change any files within system using the apps root explorer. Anyone else have this issue? Anyone know a solution?
Please dont suggest using another app. I have tried that and they do work. I just prefer ES.
Sent from my SCH-I545
I had the same issue, and ended up buying Root Explorer. No idea why. I couldn't even find the option to make it writeable like I used to be able to.
..
thanx for chart
I noticed this too. Has anyone tried previous the version to see if that makes a difference?
Update: I tried the older version and it tries to run a test which fails, resulting in not being able to use that feature. I would assume the same test is failing in the new version.
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im_Gumby said:
Update: I tried the older version and it tries to run a test which fails, resulting in not being able to use that feature. I would assume the same test is failing in the new version.
Click to expand...
Click to collapse
Not sure, but maybe related to OP's issue: after rooting, using ES File Explorer version 3.0.4 (dl'd from play store), I can't use the built in root explorer. After selecting "Root Explorer" from the menu, after a delay (appoximately 20 seconds) I get the "Sorry, test failed. This feature cannot run on your phone." message in the attached screenshot.
Interestingly, I was able to access ES's root explorer while still on the pre-release kernel, before flashing back to the stock kernel.
The new ES is a little different. Pull up the fast access menu and open the tools tab on the left. from there, tap on root explorer, mount R/W, then change the bubbles to RW. I had to do this to edit my build.prop so I assume this is what you're asking. Hope this helps!
whichonespink73 said:
The new ES is a little different. Pull up the fast access menu and open the tools tab on the left. from there, tap on root explorer, mount R/W, then change the bubbles to RW. I had to do this to edit my build.prop so I assume this is what you're asking. Hope this helps!
Click to expand...
Click to collapse
I don't get any options for mount as R/W. I think I've seen that menu before so I know what you're talking about. But it doesn't show up on the S4. At least not for me.
Sent from my SCH-I545
atrohde said:
I don't get any options for mount as R/W. I think I've seen that menu before so I know what you're talking about. But it doesn't show up on the S4. At least not for me.
Sent from my SCH-I545
Click to expand...
Click to collapse
So when you pull up the fast access menu and click root explorer under tools, you dont see mount R/W like in this picture?
Not at all. Just wiped app data and tried again and nothing. Just the test failed message.
Sent from my SCH-I545
atrohde said:
Not at all. Just wiped app data and tried again and nothing. Just the test failed message.
Sent from my SCH-I545
Click to expand...
Click to collapse
I don't get that menu either. My test fails also.
same here. ES's new update sucks anyway. i've used ES since day one, and with the new update, every single time you wanna do root things you have to mount system....EVERY time. the old one would stay mounted. it's very annoying.
i started using root browser or something..the free one.
I was reading through some other posts on a different thread and I came to the understanding it may have to do with the file system format or kernel. I would test a kernel but not sure if I can easily get back to stock as I don't want to lose functionality. Can anyone else test a different kernel to see if that works?
Sent from my SCH-I545
i'm running ktoonz kernel and it doesn't work.
jayochs said:
i'm running ktoonz kernel and it doesn't work.
Click to expand...
Click to collapse
Touchwiz or AOSP?
Sent from my SCH-I545
ah sorry. stock touchwiz. didn't flash a new rom yet
Sent from my SCH-I545 using Tapatalk 4 Beta
I ran into this exact same problem with ES File Explorer. I thought it might have to do with using SuperSU, but I haven't been brave enough to downgrade to Superuser.
As with others, I've gotten very comfortable with Root Explorer. I now only use ES to copy between the local file system and Windows shares.
- Dave
____________________________________________
Sent from my Galaxy S4 using Tapatalk 2
Worked with developer and got the version that can mount read write on system.
tsangwc said:
Worked with developer and got the version that can mount read write on system.
Click to expand...
Click to collapse
I have also and can confirm the new release works.
tsangwc said:
Worked with developer and got the version that can mount read write on system.
Click to expand...
Click to collapse
Also confirmed, once.
Now that I go back into the app a second time, it doesn't seem to ask SuperSU for permissions and /data (for example) is empty.
I'm still not 100% convinced I fully understand the new ES Explorer's root paradigm. In the old one I fell in love with, you enabled root with one simple checkbox and you had Root Explorer (kinda; I have both installed). In this latest major update, you have to pick Root from the side menu, after which you're prssented with a list of tools that I don't want/need. To browse as root, do I just hit Back to this helpful, unwanted list and start browsing? This is what I did during the first successful test of this test code, but it won't work a second time.
- Dave
____________________________________________
Sent from my Galaxy S4 using Tapatalk 2