i pretty much understand what rooting is, basically giving yourself admin privileges on the phone. however, i was wondering, if after rooting, does everything else stay stock and will i still get the OTA updates. the reason i'm asking is because i want to install the honeycomb music player on my stock nexus s and i believe i need to root it to do so. if i do the install, i should still get the OTA right?
Yes you will still get the ota.
Sent from my Nexus S using XDA App
Root by itself won't stop you from getting the OTA, but if you mod your system with anything that changes the stock files in /system/app and a few other /system/ subfolders, or the kernel/boot.img file, the OTA will fail since the crc checks in the update script will abort the install once any of those files are checked.
Depending on how you install the honeycomb music player, that alone could be a reason for the update to abort. If it's pushed to your /system/app folder as a replacement (with the same name) as the stock player, the update will abort.
I'm planning on joining the soak test (I have the invite and survey already done) and it was recommended that I reset my phone before the test sense I have it rooted.
This essentially gives me 3 options
As-Is, leave the root, busybox, and my mods on the phone (apn changes and some build.prop changes but not those that mis-identify the phone, nothing major) and hope for the best.
Unroot, uninstall root needed apps like busybox and update
Factory Reset, Recommended by Motorola but it'd take some time to rebuild the settings how I like them
Which option?
Thanks!
SaratogaCx said:
I'm planning on joining the soak test (I have the invite and survey already done) and it was recommended that I reset my phone before the test sense I have it rooted.
This essentially gives me 3 options
As-Is, leave the root, busybox, and my mods on the phone (apn changes and some build.prop changes but not those that mis-identify the phone, nothing major) and hope for the best.
Unroot, uninstall root needed apps like busybox and update
Factory Reset, Recommended by Motorola but it'd take some time to rebuild the settings how I like them
Which option?
Thanks!
Click to expand...
Click to collapse
The update will check build.prop for a sha1sum of "9ff9faedeb74bd02b3fe6a912e758f55d1437538", along with 615 more files (I am saying based on previous leak, the count may change). So if you touched build.prop or default.prop the OTA will refuse to proceed. It doesn't matter if you leave it rooted, at least leak didn't check for existence of su. But it recursively reset permission of /system so you'll lose root. If you hand edited build.prop I doubt if factory reset will help you restore. Maybe you want to return to full stock to guarantee that OTA update will work.
kousik said:
The update will check build.prop for a sha1sum of "9ff9faedeb74bd02b3fe6a912e758f55d1437538", along with 615 more files (I am saying based on previous leak, the count may change). So if you touched build.prop or default.prop the OTA will refuse to proceed. It doesn't matter if you leave it rooted, at least leak didn't check for existence of su. But it recursively reset permission of /system so you'll lose root. If you hand edited build.prop I doubt if factory reset will help you restore. Maybe you want to return to full stock to guarantee that OTA update will work.
Click to expand...
Click to collapse
That's the kind of information I was looking for. Thanks!
Now for the dumb question.. can I do that completely from within the phone?
Returning to full stock just from the phone, I think not possible, you need a computer to flash the firmware.
If you didn't touch any file except build.prop, then maybe you can download or email yourself a stock build.prop (attached, rename to build.prop), and then use root explorer or terminal emulator to overwrite the modified one.
kousik said:
Returning to full stock just from the phone, I think not possible, you need a computer to flash the firmware.
If you didn't touch any file except build.prop, then maybe you can download or email yourself a stock build.prop (attached, rename to build.prop), and then use root explorer or terminal emulator to overwrite the modified one.
Click to expand...
Click to collapse
Thanks, I restored the file. I'll hook back into the thread when the upgrade comes down and report how it goes.
Also, if you installed the Atrix 2 Bootstrap to run Clockworkmod recovery you will need to restore the following files. You need to still be rooted in order to do this. I did it with Root Explorer.
1) Delete file /system/bin/logwrapper
2) Delete file /system/bin/hijack
3) Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
4) Delete directory /preinstall/recovery
Furthermore, if you installed it to be loaded every time you boot you also need to restore the following file.
1) Delete file /system/bin/mot_boot_mode
2) Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
I didn't do anything with Clockworkmod but I was able to find another version of the build.prop file I had that was the original that was on my phone.
The one that kousik gave me was the AsiaRetail.GB version. I attached my build.prop file which should be more suitable for AT&T phones (remove the .phone.txt).
jboxer said:
Also, if you installed the Atrix 2 Bootstrap to run Clockworkmod recovery you will need to restore the following files. You need to still be rooted in order to do this. I did it with Root Explorer.
1) Delete file /system/bin/logwrapper
2) Delete file /system/bin/hijack
3) Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
4) Delete directory /preinstall/recovery
Furthermore, if you installed it to be loaded every time you boot you also need to restore the following file.
1) Delete file /system/bin/mot_boot_mode
2) Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
Click to expand...
Click to collapse
Are you saying the above has to be done if using fxz with RDS Lite to get back to 2.3.5 stock?
Another question...I did go back to stock 2.3.5, but when I check for update to go OTA 2.3.6, it tells me that check for updates is disabled.
How long after going back to 2.3.5 stock before it updates to 2.3.6?
troycarpenter said:
Are you saying the above has to be done if using fxz with RDS Lite to get back to 2.3.5 stock?
Another question...I did go back to stock 2.3.5, but when I check for update to go OTA 2.3.6, it tells me that check for updates is disabled.
How long after going back to 2.3.5 stock before it updates to 2.3.6?
Click to expand...
Click to collapse
1. No if you flashed back to stock everything you did has been removed.
2. You should be able to download the OTA to 2.3.6 from 2.3.5 immediately, but often the production update servers are offline before a soak test or new OTA being released. I just checked my phone and for me the servers were online and told me no updates are available. I am on 2.3.6.
troycarpenter said:
Are you saying the above has to be done if using fxz with RDS Lite to get back to 2.3.5 stock?
Another question...I did go back to stock 2.3.5, but when I check for update to go OTA 2.3.6, it tells me that check for updates is disabled.
How long after going back to 2.3.5 stock before it updates to 2.3.6?
Click to expand...
Click to collapse
Make sure you're on wifi to receive the 2.3.6 update. I don't think it works on data.
The phone finally took 2.3.6 earlier today. Quite a bit of time on 2.3.5 before it recognized the update.
Hi, I have a GT-S7500 (wife's phone) with stock firmware and CWM. For some reason as soon as I root it, tried many different methods, camera and camcorder (and sometimes wireless) stop working. The thing is i don't really want to root this phone - but I really need to remove bloat Samsung and Italian TIM apps from it because the phone is unusable. (This means: freshly pushed stock firmware has 10-15 useless system processes and services running resulting in 70-80% of RAM usage)
So, I need to remove bloatware without rooting the phone. This is my starting point(http://forum.xda-developers.com/showthread.php?t=1534349#post23343879)
I'd like to take the "system.ext4.tar" from my CWM backup, extract, manually remove unwanted apk and odex files from it repack and push it back to the phone. Sounds fun!
Q1: "system.ext4.tar" is a normal .tar file, right? so when I'm finished i just use tar (i'm on *nix)
Q2: The above guide does not say but what is the best way to "push" the system partition back to the phone? My idea was to substitute the "system.ext4.tar" with its modded version right in the CWM backup folder (calculate and change md5 checksum in nandroid.md5) and then execute a restore from CWM. You think that would work? Is there another way to do this(ODIN)?
thanks
a\
Android Kitchen
Ok, I found Android Kitchen(http://forum.xda-developers.com/showthread.php?t=633246) and it resolved all my questions and doubts. You can take apart any rom (stock or custom) modify and repack it for CWM install. Thanx xda!
Anyone know?
I tried renaming OTAcerts.zip to .bak but no luck
couldn't find htcOMADM.apk or similar
An OTA needs to be approved by the user, so unless you agree to run it, it won't happen.
Sent from my Evita
Remove COTA app?
If rooted, just use Titanium to freeze the process "updater".
Hi everyone.
Well, basically I'm here because Pokémon GO is now unable to run if the OS is rooted, so I'm going to get rid of the root. However, I don't want to revert all the things that I've got like the deleting of all that annoying bloatware that came along the first time, and for and for all that I need to know what to exclude from the firmware when I do proceed from flash mode in Flashtool. I suppose that system.sin is the directory where all that crap is stored but I'm not really sure. Would you be kind to explain me?
Thank you so much. :laugh::victory:
Since no one answered I will try. Instead of changing .ftf file and trying to do something where you don't have expirience, why don't you simply unroot your phone? Delete all apps that need root to work (Xposed, root explored...) and if I remember well there is option in SuperSU to unroot phone. I would suggest you to use Magisk, but I think it is for 5.0+ because Pokemon GO use same safety system as AndroidPay use.
P.S. Before you do anything, make a backup.