don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
By "still rooted" do you mean you still have the superuser.apk or can you actually still boot into CWM? Because an OTA will not delete those apps but it WILL break root.
oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
The update doesn't wipe the phone at all, it only patches certain files in the /system partition, so it doesn't actually delete the su binary in /system/bin or the superuser.apk in /data/apps.
The update script does, however, do a recursive chmod of the permission on /system/bin, and that broke root on my phone. Even though the files were still there, and some apps thought that I was still rooted, many root things (like Titanium and Root Explorer's ability to mount /system as R/W) wouldn't work.
I've seen some reports that root stuck, but I'd advise flashing the su update again...it's quick and easy to do with CWM, and it will fix the permissions to make sure none of your apps have any issues.
Are you sure the update actually occurred? Your android version and build number have changed?
so, now i have
Android version - 2.3.2
Kernel - 2.6.35.7-g7f1638a
Build number - GRH78C
if start titanium backup - can see that superuser permission granted
Market access working perfectly - i hav an acces for paid apps
Can grab screen with ShootMe
dont remember how did i root - seems i just run some script on ubuntu notebook
Thanks for everybody for replies
yes, going into CWR can easily update the permissions recursively
not sure but probably i am on superboot loader (not SWR)
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
RogerPodacter said:
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
Click to expand...
Click to collapse
He's saying that he thought the OTA would unroot him, not that being rooted would keep him from OTAing.
Funny how the update seems to impact the root of people differently. It definitely broke mine, even though it didn't erase the files.
Oh oops my bad I mis read!
The update didn't break my root
sagech said:
The update didn't break my root
Click to expand...
Click to collapse
it seems new uppdate does not unroot phones with superboot rooting
No Update
Hello,
I tried to update my phone but I am now looking since 10 minutes at the little Android and nothing happens.
There was a short message where the Clockworkrecovery said something like it could not verfy the update file.
Should I just put out the battery and try to reboot?
Edit:
The Clockwork recovery came up again and I selected to reboot the phone. Now it's still running on 2.3.1.
What have I done wrong?
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Bronk93 said:
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Click to expand...
Click to collapse
Yes, exactly!
So is the solution maybe to wait till the 2.3.2 version is available at the ROM Manager?
Related
I see talk the the Super User Root has been upgraded to 2.3. It's suppose to be much better than the current one. Will we have to uninstall the current one before applying the new root? Has anyone made an attempt to install SU 2.3 in a Captivate yet?
Qmotion said:
I see talk the the Super User Root has been upgraded to 2.3. It's suppose to be much better than the current one. Will we have to uninstall the current one before applying the new root? Has anyone made an attempt to install SU 2.3 in a Captivate yet?
Click to expand...
Click to collapse
my update.zip is getting it added soon.
edit---
uploading now
edit---
up now
http://forum.xda-developers.com/showthread.php?t=751934
I rooted my phone using the pimp my cap. PDF. If I wanted to unroot. Could I just delete the original update.zip file and replace it with out flashing back to stock? The reason I'm asking is I don't have a pc. (im on mac) and I can't use odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
What will we have to do to replace the old version? Can one be installed on top of the other?
?
Qmotion said:
What will we have to do to replace the old version? Can one be installed on top of the other?
?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=682828
there is an update.zip that will do what you need.
So what your saying is you just install the new update.zip as we did during the first install?. As stated that means we don't have to uninstall or go back to the stock rom. It pays for us noobs to be certain.
Qmotion said:
So what your saying is you just install the new update.zip as we did during the first install?. As stated that means we don't have to uninstall or go back to the stock rom. It pays for us noobs to be certain.
Click to expand...
Click to collapse
yup, flash over
DONT UPDATE TO THIS. I did, and now I get force close after force close, I can't load a backup ROM at all. Going to unroot and root again hoping to get back to the previous version.
designgears said:
yup, flash over
Click to expand...
Click to collapse
Ok so just install over my current root? Or flash to stock then root?
Sent from my SAMSUNG-SGH-I897 using XDA App
Smallsmx3 said:
Ok so just install over my current root? Or flash to stock then root?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
install over your current root
flashman2002 said:
DONT UPDATE TO THIS. I did, and now I get force close after force close, I can't load a backup ROM at all. Going to unroot and root again hoping to get back to the previous version.
Click to expand...
Click to collapse
designgears said:
install over your current root
Click to expand...
Click to collapse
OK, now I'm confused. I almost did it. I'm scared now....
Designgears, you have done this to your phone and it works now. Flashman did you figure out what you did wrong?
The only thing I can figure is I updated through ROM manager. I imagine people that are using the update.zip should have no issues from what I read in the Superuser thread. I am not going to try again for a couple days to be sure, but people are able to make it work without issue. I figured with it showing up in ROM manager it would have been safe to load that way, as I upgraded to 2.2.2 when I first got ROM Manager.
Qmotion said:
OK, now I'm confused. I almost did it. I'm scared now....
Designgears, you have done this to your phone and it works now. Flashman did you figure out what you did wrong?
Click to expand...
Click to collapse
Just did mine, works fine.
Is this just the updated Su 2.3.1 ??
I see that you also have the http://www.multiupload.com/BCLH94FNVD file on the other thread that seems to include the new root file. Or does this update.zip file include everything?
Excuse me for being extra carefull. Better safe than sorry.
I actually want to install the file that includes the sideloading. I haven't made that mod to my phone yet.
Does the BCLH94FNVD file include everything all in one shot?
designgears said:
my update.zip is getting it added soon.
edit---
uploading now
edit---
up now
http://forum.xda-developers.com/showthread.php?t=751934
Click to expand...
Click to collapse
If I may.. Was there a changelog? I mean.. 2.2 grants needed privilege. Not trying to be sarcastic at all but I see so many people worried about this or that it left me wondering what was new.
I tried it and it said the update was aborted. Didn't give a reason. I took out the original update file and replaced it with the new one. Should I have left both files in?
Maybe I'm not asking the question right. The link to the update file you added to this thread. Is it for the EliteSuperRooter or is it just for the 2.3.1 root OR would we still have to add the file on the other thread that seems to include the new root file. Or does this update.zip file include everything?
mostyle said:
If I may.. Was there a changelog? I mean.. 2.2 grants needed privilege. Not trying to be sarcastic at all but I see so many people worried about this or that it left me wondering what was new.
Click to expand...
Click to collapse
In the General Android Dev forum there is a changelog and he changed a ton of stuff.
edit - It was in Apps and Games my bad.
http://forum.xda-developers.com/showthread.php?t=682828
for lazy ppl this is what different between 2.2 and 2.3.1
(New for 2.3)
- New layout of main app
- Full logging
- New request layout
- Fixed boot/widget bug
- Date/time format options
- Better notification system
- New icon
- Better allow system
- A whole mess of code cleanup
- Rearranged drawables so that only one apk needs to be built for any firmware
(New for 2.3.1)
- Big bugfixes
- Better support for landscape mode
- better support for ldpi devices
The question is, what does this offer that my current superuser doesn't?
I'm getting my Mom a Skyrocket for Xmas. I'm going to set it up for her. I would like to remove some of the ATT junk. That would require root. But when ICS comes, I would like her to be able to get the update OTA without any problems. She lives 600 miles away and I can't just fix things for her easily.
If I root and then unroot, will she be able to gt OTA updates?
yes if you unroot you can recieve the update. even if your rooted but have stock recovery you should be able to recieve the update.. you must have stock recovery
silver03wrx said:
yes if you unroot you can recieve the update. even if your rooted but have stock recovery you should be able to recieve the update.. you must have stock recovery
Click to expand...
Click to collapse
So if I just root for su access. Then install a few apps that require superuser to install but not run,then uninstall root I should be OK. But I could also leave root maybe?
So we can root, delete bloat ware then unroot?
you may not be able to take and ota update if u deleted bloat... you can root and freeze your bloat then if theres an ota update unfreeze and take teh update. as long as you have stock recovery..
draztikrhymez said:
So we can root, delete bloat ware then unroot?
Click to expand...
Click to collapse
You missed a step
1) Root
2) Uninstall Bloatware
3) Install my own Bloatware
4) Unroot
I'm hoping that will work.
Or maybe leave root in place?
Silver03wrx is one of the best sources of help skyrockets have right now.
You only need stock recovery and bloatware means, you only need stock recovery and bloatware.
So freeze it, don't uninstall it. Anything that needs to be flashed by cwm, don't. Do it manually as cwm replaces stock recovery.
Aside from those, do whatever you want. Just make sure if any over the air updates come out, all the apps are unfrozen first or it can cause issues and/or no allow the update to install.
Play around with droidvnc. It allows remote connection to an Android. Let's you do remote assistance. Can be slow, but sometimes, most the time, faster than our parents.
Sent from my páhhōniē
silver03wrx said:
you may not be able to take and ota update if u deleted bloat... you can root and freeze your bloat then if theres an ota update unfreeze and take teh update. as long as you have stock recovery..
Click to expand...
Click to collapse
I'm new here, what does freezing do? I've seen it in Titanium. Won't the app still show in the appz menus?
les_garten said:
I'm new here, what does freezing do? I've seen it in Titanium. Won't the app still show in the appz menus?
Click to expand...
Click to collapse
no. thats the point of freezing. it wont show up in app drawer or run in background if its a service....from looking at your phone, it wont appear that its installed, however, the files are still there in case you need to defrost them later on for some service that Samsung requires for an OTA (over the air)
if you uninstall, you are REMOVING the files from /system/apps/ and we dont know how that will react to an OTA at this point.
Hi, sorry to re-open an old thread but I too am a new android user and was wondering about the future ICS update for our skyrockets.
The words that keep repeating in this post are "freeze bloatware" and "stock recovery" in order to get the official ICS update.
I rooted my phone and used bloat freezer free found in the app market to freeze a bunch of bloat and installed wifi tether for root users. Does this mean I still have "stock recovery"?
Sorry- I've been an iphone user for the past 4 years (since nearly the first day it came out) and i'm not familiar with all the android terms yet. thanks!
You would know if u had stock recovery. Because you would have had to flash cwm recovery tar with odin or installed it with rom manager. If u did not do eiher of those yes you have stock recovery
Is there a way to get root access without installing CWM? I thought that was the only way to install the superuser file?
So I've rooted (the day it came out, so before the first update) and can't update anymore. It'll fail when attempting and reboot me. It wouldn't be an issue but I don't like getting popup reminders about the update. I've searched around but haven't found this issue and am hoping I don't have to reflash the stock rom to update again, I'd also like to keep all my stuff you know. Hopefully someone knows a solution. Sorry if this is dumb
iamheero said:
So I've rooted (the day it came out, so before the first update) and can't update anymore. It'll fail when attempting and reboot me. It wouldn't be an issue but I don't like getting popup reminders about the update. I've searched around but haven't found this issue and am hoping I don't have to reflash the stock rom to update again, I'd also like to keep all my stuff you know. Hopefully someone knows a solution. Sorry if this is dumb
Click to expand...
Click to collapse
Unroot, install update, reroot.
How to Unroot:
Thanks shabbypenguin for posting this.
You can manually unroot your Droid by using a root file manager program (such as root explorer) and mountsystem as R/W. Then delete the following:
/system/app/Superuser.apk
/system/bin/su
and if it has it
/system/xbin/su
EdwardN said:
Unroot, install update, reroot.
How to Unroot:
Thanks shabbypenguin for posting this.
You can manually unroot your Droid by using a root file manager program (such as root explorer) and mountsystem as R/W. Then delete the following:
/system/app/Superuser.apk
/system/bin/su
and if it has it
/system/xbin/su
Click to expand...
Click to collapse
Thanks! Unfortunately, it still fails about 10% of the way through the update. Since JB just came out I'll have to just flash to stock completely and try updating legitimately, then rooting it again, I guess.
iamheero said:
Thanks! Unfortunately, it still fails about 10% of the way through the update. Since JB just came out I'll have to just flash to stock completely and try updating legitimately, then rooting it again, I guess.
Click to expand...
Click to collapse
You may have solved this problem already but did you try using voodoo root keeper? It's a pretty straight forward way of backing up the root, unrooting to install the update, then rerooting when the update is installed.
Sent from my DROID RAZR HD using Tapatalk 2
Were you successful?
iamheero said:
Thanks! Unfortunately, it still fails about 10% of the way through the update. Since JB just came out I'll have to just flash to stock completely and try updating legitimately, then rooting it again, I guess.
Click to expand...
Click to collapse
I'm running into the same problem. Did the flash back to stock and subsequent update to JB work for you? If so, were can I download the stock OS?
mmettlen said:
I'm running into the same problem. Did the flash back to stock and subsequent update to JB work for you? If so, were can I download the stock OS?
Click to expand...
Click to collapse
Hey there, I had the same problem. Rooted, unrooted, frozen, deleted, restored, couldn't get anything to get JB to work. Eventually just gave up and flashed to stock. Used the amazing Utility presented here
just make sure to gain root access before going to the JB update. there is no present method for getting root on fresh phone with JB update.
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse
TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?
dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.
nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM
back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...
nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?
Hi,
I rooted my phone before upgrading to Lollipop back in the day and as a result I was left with a non-rooted phone with traces of root (annoying for apps that check that to grant usage).
I effectively still have a couple of su binaries and tools in /system/xbin, what I'm wondering is:
how could these binaries have survived to multiple OTA updates (I'm now running 6.0), as I thought everything except /data would get wiped and reflashed after every update?
I don't think an OTA formats partitions (like /system), it just modifies files/folders. It knows what to update/overwrite/patch, that's why if we modify a file that's going to be updated by the OTA, it will no longer be the exact file and thus the OTA will fail.
For files that have been placed there by the user, OTA doesnt know about them.
Sent from my Nexus 5 using Tapatalk
Hi,
thanks for the answer. It makes sense now. I guess I'll have to unlock the bootloader to be able to get rid of those files.
PS: if the su binary is effectively there, why SuperSU exits immediately complaining there's no binary? The phone is not rooted, but the binary is there.
lafayette84 said:
Hi,
thanks for the answer. It makes sense now. I guess I'll have to unlock the bootloader to be able to get rid of those files.
PS: if the su binary is effectively there, why SuperSU exits immediately complaining there's no binary? The phone is not rooted, but the binary is there.
Click to expand...
Click to collapse
Binary needs to be updated to work with M+root on M requires kernel support
Sent from my Nexus 10 using Tapatalk