Develop Bugs

[Q]Does having S-OFF stop OTA updates?

The question is simple, I hope someone can answer!

ColdFire InOx said:
The question is simple, I hope someone can answer!
Click to expand...
Click to collapse
No, as long as you don't modify the system partition, or firmware.

Rouz. said:
No, as long as you don't modify the system partition, or firmware.
Click to expand...
Click to collapse
So can I install Better Battery Stats and GSam Root Companion and such apps or will that affect OTA availability?

ColdFire InOx said:
So can I install Better Battery Stats and GSam Root Companion and such apps or will that affect OTA availability?
Click to expand...
Click to collapse
Actually you don't need s-off to use these apps. You can just unlock the bootloader and root.
Unlocking the bootloader does not have any affect on the OTA system. But installing a custom recovery to root your device breaks the update process, unless you flash back the stock recovery before taking the OTA.
Also make sure to not to make any changes in the system apps after rooting, as it may cause the update to fail on system check.
I think you should try reading a bit more about the whole unlocking and rooting process before you proceed. There are a lot of useful threads in this forum that can help you.
If you have any other questions you can ask here.

Rouz. said:
Actually you don't need s-off to use these apps. You can just unlock the bootloader and root.
Unlocking the bootloader does not have any affect on the OTA system. But installing a custom recovery to root your device breaks the update process, unless you flash back the stock recovery before taking the OTA.
Also make sure to not to make any changes in the system apps after rooting, as it may cause the update to fail on system check.
I think you should try reading a bit more about the whole unlocking and rooting process before you proceed. There are a lot of useful threads in this forum that can help you.
If you have any other questions you can ask here.
Click to expand...
Click to collapse
Well my device has indeed unlocked bootloader already and also root access. However, installing the apps I mentioned makes them malfunction - I install as system app as it asks to but it seems to fail as it keeps asking me to repeat the process every time I try.
I am not a beginner to rooting phones although I am a beginner in what concerns the HTC S OFF procedure.
I accidentally deleted two stock apps upon a factory reset after rooting (flashlight and calculator), but I already found the apk and reinstalled them.
P.S. - AdAway also failed to function but from what I have read around it requires S-OFF to work properly.

ColdFire InOx said:
Well my device has indeed unlocked bootloader already and also root access. However, installing the apps I mentioned makes them malfunction - I install as system app as it asks to but it seems to fail as it keeps asking me to repeat the process every time I try.
I am not a beginner to rooting phones although I am a beginner in what concerns the HTC S OFF procedure.
I accidentally deleted two stock apps upon a factory reset after rooting (flashlight and calculator), but I already found the apk and reinstalled them.
P.S. - AdAway also failed to function but from what I have read around it requires S-OFF to work properly.
Click to expand...
Click to collapse
all you need is a insecure kernel as you can see changes to the system partition are lost if you don't have one
look for a matching kernel to your rom or choose a rom that already includes this feature
The only reason you need s-off is to flash firmware older than the one currently on the phone and some GPe/Lollipop roms

[Q] From rooted Kitkat to Lollipop

Hi!
My Z1C is rooted, has dualrecovery and is running a stock 4.4.2 (14.3.a.0.757)
I also have a lot of customizations via XPosed.
What would be the easiest way to upgrade to a Lollipop version? Someone suggested I can just upgrade and use towelroot afterwards to regain root, but I could not find any verification of that.
Is it safer to flash a pre-rooted zip and if so can anyone point to a decent source?
Also, will XPosed Framework still be functional on Lollipop? I hear there are so many headachy changes to the security layout that I am not sure of that, but right now I'Äd feel safer with a version that has Stagefright fixed...
Let me know what you think!
Thanks

Walter_White said:
Hi!
My Z1C is rooted, has dualrecovery and is running a stock 4.4.2 (14.3.a.0.757)
I also have a lot of customizations via XPosed.
What would be the easiest way to upgrade to a Lollipop version? Someone suggested I can just upgrade and use towelroot afterwards to regain root, but I could not find any verification of that.
Is it safer to flash a pre-rooted zip and if so can anyone point to a decent source?
Also, will XPosed Framework still be functional on Lollipop? I hear there are so many headachy changes to the security layout that I am not sure of that, but right now I'Äd feel safer with a version that has Stagefright fixed...
Let me know what you think!
Thanks
Click to expand...
Click to collapse
AFAIK, there is currently no 'one click' root for 5.1. There is a thread about a Kingroot-to-Supersu method that I can verify works for 5.0.2. You can root 5.1, but either by fastboot, (requiring unlocked bl), or downgrade method, (which you're already on step 1 with KK). There seems to be varied reports about PRFs, but I'm sure you can find a good one by now. I think the main question is if you're hoping to save app data, Xposed settings, etc., to restore afterwards. If so, I would say it's very iffy. You could try Titanium or something, but I wouldn't be surprised if you get some glitches.
As far as Xposed, it works great on 5.0 or 5.1, and there's new developments coming steadily.
Search Z1c 'general', and 'android development' forums for downloads, etc.

Forgot to mention, BL is unlocked with dualrecovery.
Thanks for your advice so far. Root procedure for 5.1 with unlocked BL is already outlined in a thread here?
And yeah, I agree, trying to save app data / settings is bordering on impossible now, I fear TiBackup has outlived its usefulness when it comes to ROM migration. Spent half of today getting my Z1C apps to Z5C and still not nearly half done.
Damn gremlins.

Walter_White said:
Forgot to mention, BL is unlocked with dualrecovery.
Thanks for your advice so far. Root procedure for 5.1 with unlocked BL is already outlined in a thread here?
And yeah, I agree, trying to save app data / settings is bordering on impossible now, I fear TiBackup has outlived its usefulness when it comes to ROM migration. Spent half of today getting my Z1C apps to Z5C and still not nearly half done.
Damn gremlins.
Click to expand...
Click to collapse
To root with unlocked bl, flash stock ROM w/ Flashtool, then flash this with fastboot -http://forum.xda-developers.com/sony-xperia-z1-compact/general/ub-root-init-d-support-recovery-busybox-t3202799 - done. Then you can install Xposed, custom kernel, etc..

Thanks!
Will try this as soon as I managed to migrate my stuff fully to my new Z5C. Migration without TiBackup is a real PITA

Just making sure, when using your route "flash any stock and then follow up with the mentioned file" it means I can jump straigfht from 4.4.2 into the 5 era? Or Do I have to go to 5 for some compatibility reasons. I recall there was something like this sometime back when there was a major new version.
As far my planned procedure for tmw is:
TWRP backup
CWM backup
TiBackup
copying required stuff to the computer
then flash http://forum.xda-developers.com/son...al/stock-14-6-0-368-ce1-dualrecovery-t3216740 as this seems to be the most recent version including updates of the recoveries, pre-rooting already combined. This saves me the step from bone stock to pre-rooted stock as I would have to make in your suggestion.
Also, I want to as well try to use the DRM Feature Fix Mod (http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672), so I will flash the LP version of that one afterwards.
This should work, or am I missing anything significant? I can very well toss the data, the Z5C is now my main phone,, the Z1C has been given a 2nd life with a new backplate and battery I just put in so I'd hate to brick it.
Please confirm that I have a general idea of what I am doing lol... Using flashtool etc. is known to me but selecting the right ROMs remains a mystery unless you follow XDA daily...
Much appreciated

Walter_White said:
Just making sure, when using your route "flash any stock and then follow up with the mentioned file" it means I can jump straigfht from 4.4.2 into the 5 era? Or Do I have to go to 5 for some compatibility reasons. I recall there was something like this sometime back when there was a major new version.
As far my planned procedure for tmw is:
TWRP backup
CWM backup
TiBackup
copying required stuff to the computer
then flash http://forum.xda-developers.com/son...al/stock-14-6-0-368-ce1-dualrecovery-t3216740 as this seems to be the most recent version including updates of the recoveries, pre-rooting already combined. This saves me the step from bone stock to pre-rooted stock as I would have to make in your suggestion.
Also, I want to as well try to use the DRM Feature Fix Mod (http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672), so I will flash the LP version of that one afterwards.
This should work, or am I missing anything significant? I can very well toss the data, the Z5C is now my main phone,, the Z1C has been given a 2nd life with a new backplate and battery I just put in so I'd hate to brick it.
Please confirm that I have a general idea of what I am doing lol... Using flashtool etc. is known to me but selecting the right ROMs remains a mystery unless you follow XDA daily...
Much appreciated
Click to expand...
Click to collapse
Sorry, not sure if you were responding to me... As far as backing up and restoring data, I can't say for sure what's best, going from kk to lp. If you're going from stock to stock, probably built-in Google backup would do the trick. 3rd party stuff is chancy when switching versions in my experience, but Titanium might do OK. I don't think you can backup any kk data in recovery, then restore it on lp. Maybe someone else can tell you otherwise. As far as root in on lp, with unlocked bl, all you need is to flash stock ROM in flash mode with Flashtool, then flash the IMG I linked. - done.

Turning Off Enable superuser in SuperSU

Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.

sliding_billy said:
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
Click to expand...
Click to collapse
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.

pcriz said:
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
Click to expand...
Click to collapse
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question

sliding_billy said:
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
Click to expand...
Click to collapse
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.

pcriz said:
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
Click to expand...
Click to collapse
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.

sliding_billy said:
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
Click to expand...
Click to collapse
I can't see the initial process of loading it changing. Right now there are issues with restoring but if you don't make a back up it won't affect a thing but it will make flashing mods and updates to the TWRP easier.
Aside from using a tool kit, installing it seems to be spot on so long as all the steps are followed.
So once a stable build comes out I will simply flash in the TWRP I currently have.

Root & Rom Advice from the Ground Up

I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!

If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?

1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.

mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?

jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.

alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?

The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?

Unlock, Root, Xposed and then relock

Hi, my Mix2 arrived few days ago and I find MiUI quite nice, yet lacking few things. Those are easily available via xposed, hence I need to root. I'm also not so lucky in these matters so before I start to tinker with it I'd like to learn few things.
What are least dangerous ways to unlock and root phone? (heard sth about magisk, its quite new for me, haven't been rooting phones for couple years now) Is it good?
Suppose I succeed unlocking, rooting and flashing xposed, can I relock bootloader? I want that because ie AndroidPay needs that to work, and I haven't found any working rootcloack or similar (at least on Note2)
How reliable is 'the most official tool' for xiaomi flashing (from eu.xiaomi.com ?)? I mean can it bring back the dead or revert phone back to where I started, without any trace of tinkering?
As a new xiaomi owner are there any critical things I need to know?
Thanks!

If you flash magisk, which is the best thing ever btw, you won't have to relock bootloader to get Android pay working.

yeyeoke said:
If you flash magisk, which is the best thing ever btw, you won't have to relock bootloader to get Android pay working.
Click to expand...
Click to collapse
Thanks, I read about that and intend to use it. Though, there might be some issues with magisk and different versions. What features does it have?
So far, need to wait 3 days to unlock bootloader.

Mighty_Ahti said:
Thanks, I read about that and intend to use it. Though, there might be some issues with magisk and different versions.
So far, need to wait 3 days to unlock bootloader.
Click to expand...
Click to collapse
I've been using magisk on my Note 3 Pro since release and I've never had an issue. Yes, I got my mix 2 today and I'm also waiting for 3 days..

Mighty_Ahti said:
Hi, my Mix2 arrived few days ago and I find MiUI quite nice, yet lacking few things. Those are easily available via xposed, hence I need to root. I'm also not so lucky in these matters so before I start to tinker with it I'd like to learn few things.
What are least dangerous ways to unlock and root phone? (heard sth about magisk, its quite new for me, haven't been rooting phones for couple years now) Is it good?
Suppose I succeed unlocking, rooting and flashing xposed, can I relock bootloader? I want that because ie AndroidPay needs that to work, and I haven't found any working rootcloack or similar (at least on Note2)
How reliable is 'the most official tool' for xiaomi flashing (from eu.xiaomi.com ?)? I mean can it bring back the dead or revert phone back to where I started, without any trace of tinkering?
As a new xiaomi owner are there any critical things I need to know?
Thanks!
Click to expand...
Click to collapse
It's generally considered to be dangerous to relock a bootloader with anything other than perfectly stock/factory firmware installed. It may be ok to do this technically but it sort of "ties your hands" in some ways after making an unofficial modification and makes it a bit harder to recover from a botched situation.
You can have an unlocked bootloader and still use Android Pay. This can be achieved either with a ROM that is built to accomplish this (Epic ROM is an example of this) or by using Magisk, which allows root without any sort of SafetyNet trip in many cases. I don't believe there's *any* way to install Xposed and also use Android Pay or any other SafetyNet apps...the best alternative if you really want Xposed is to use Magisk and then install the Xposed Magisk module...you still can't pass SafetyNet with this setup but Magisk allows you to disable Xposed if you're willing to uncheck it in the Magisk Manager app and reboot the phone, after which time SafetyNet should pass ok...at least with this setup you'll be able to kind of have your cake and eat it too, though it's not ideal as you'll have to reboot if you want to change the status of Xposed.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

Thank you for detailed answer. I didn't know that.
flyer_andy said:
the best alternative if you really want Xposed is to use Magisk and then install the Xposed Magisk module...you still can't pass SafetyNet with this setup but Magisk allows you to disable Xposed
Click to expand...
Click to collapse
I tried AndroidPay few times past few days and it didn't work at all. Perhaps terminals were not compatibile. So lets say I gave up on AndroidPay - can I use regular Xposed along with Magisk? Or does it have to be that module?

Mighty_Ahti said:
Thank you for detailed answer. I didn't know that.
I tried AndroidPay few times past few days and it didn't work at all. Perhaps terminals were not compatibile. So lets say I gave up on AndroidPay - can I use regular Xposed along with Magisk? Or does it have to be that module?
Click to expand...
Click to collapse
Oh! I think I may be able to help you with the Android Pay issue - my phone didn't work right with Android Pay until I made sure *all* Google apps' permissions were allowed via the Apps menu in Settings (along with "Autostart" via the security app)...and also toggled the NFC setting where it lets you select between "embedded secure element" and "HCE Wallet." It probably is on "HCE Wallet" but try toggling to "embedded secure element" and then back to "HCE Wallet" a couple of times. My Mix 2 would not make a terminal connection until I did this...it would just say "card read error." Seems like a firmware bug. Let me know if that helps!
But yeah if you don't want to use Android Pay then normal Xposed should be fine...you wouldn't need Magisk I don't think. Though, I'm not sure but I think the Magisk Xposed module probably functions the same as normal Xposed so I'm not sure there's an advantage in doing so. But of course it's all about personal preference!

Whoah, I'm still new to xiaomi/android7+ policies, where each app's permissions are reduced to bare minimum (messenger not being able to show notifications for example). I will definitely try this tomorrow.
So far I just managed to unlock BL, flash recovery and install magisk. SafetyNet checks ok. Will try xposed tomorrow after some payments ;D Thanks!

HCE wallet worked for me (I had it set to SIM wallet).
If I understand correctly here is the possible solution to xposed+magisk+androidPay.
I'd need phh's su binaries for that and keep crossing fingers for it to work on 7.1
I need to learn more about that stuff before I break something

So as I was expecting I experience troubles in installing Xposed.
I followed official way as in here And got bootloop.
I removed magisk stuff in recovery and fixed bootloop, then installed v89.0 (not .1) and also bootloop.
Im using SDK25, and miui 9 - 7.1.1 so it should be ok I think

Mighty_Ahti said:
So as I was expecting I experience troubles in installing Xposed.
I followed official way as in here And got bootloop.
I removed magisk stuff in recovery and fixed bootloop, then installed v89.0 (not .1) and also bootloop.
Im using SDK25, and miui 9 - 7.1.1 so it should be ok I think
Click to expand...
Click to collapse
Disable hooks from the xposed apps settings before flashing xposed

What hooks? I dont have any modules yet

Mighty_Ahti said:
What hooks? I dont have any modules yet
Click to expand...
Click to collapse
It's a toggle in the settings under experimental, disable resource hooks

Boot took longer but it works. Thanks! Do I have to keep it on all the time ?

Mighty_Ahti said:
Boot took longer but it works. Thanks! Do I have to keep it on all the time ?
Click to expand...
Click to collapse
Yeah, phone won't boot with it on. Don't think it makes much difference anyway

Hi @Mighty_Ahti, how much time was "longer"? it's been loading for over 5 minutes already. Thanks

Certainly below 5 minutes.