Apply security updates to ZF3 after root? - Asus ZenFone 3 Questions & Answers

I have a ZF3 that I rooted /unlocked the boot loader long ago. Like, way back when you still got that "modified device" error. If I apply security updates, will it be ok?

Bump, no one has any input?

What do you mean when you say "will it be ok"?
You can install all the latest software updates even though your phone is rooted and has an unlocked bootloader. It will un-root your phone in the process though so be prepared to re-root.

Thanks for the reply. Essentially I was asking if there were any adverse effects, like the phone being bricked somehow. Re-rooting doesn't seem like too much of a pain. Thanks.

Related

[Q] Root Question related later ota

after a few hours searching, I am still a bit confusing on following question:
1. trip rootchecker
If I do not choose do this during rooting, in other word, I only have adb shell root.
a) should I still be able to install twrp and flash other rom? my impression is "yes", am I right?
b) But if I choose do this, then my warranty is gone. If I later flash back the stock,
will this be wiped and "forget"? i.e. the warranty is back?
Or is this "root checker" will send somthing to LG once it is tripped, hence warranty
is permanently voided?
2. ota
It seems once rooted, one can not take any ota, right? even the kitkat in future?
would "trip rootchecker" matter in this case?
even though thanks to thecubed, it seems we do have a solution.
If you choose not to trip the root checker, root will not work properly and neither will the apps that require it.
It doesn't send any info to LG or your carriers. All it does is... If in the future you break your phone somehow and take it into your carrier store to get it fixed, they will check the phone to see if it's ever been rooted. If it's been tripped, it'll give a number code on the screen to tell them it either was rooted in the past but isn't anymore, is currently rooted, or was never rooted.
Then it will be at the store's discretion on whether or not they'll help you out or make you pay full price to fix it or get it replaced.
I don't know how it is for the G2, but I know awhile back some newer HTC phones got S-OFF which allowed them to reset the root checker to make the device think it's never been rooted. Our phones may have a similar method out there somewhere... Though probably not as it'd be fairly big news. I am however, willing to bet that there is a crack team or two working on disabling that for our devices.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

[Q] Advice on installing an update on a rooted Nexus 10

I have a recently rooted N10 on Android 4.4 build KRT16S. I have had the system update to 4.4.2 in my notifications for weeks now. What I wanted to know has anyone installed this update without any problems? and am I likely to lose root? Bit clueless as to how these updates work but saying that I did manage unlock the boot loader and flash my tablet without any issues. Also if I shouldn't install the update how do remove this update. Thanks in advance folks, Phil.
The update may or may not work, it depends on how much you've touched the system files. If you've just rooted it, the update should work. If not, you can flash the factory image (except for the data partition).
You'll probably lose root, but on a unlocked bootloader, that's nothing to worry about, as you can trivially re-root it.
Sent from my Nexus 5 using Tapatalk

Finally rooted then I rebooted...

So hi all, this is my first post on XDA. Finding information these days you think would be easy but alas it's been one big waiting game.
A little background, I've wanted for the longest time to link my ps3 controller (WIRELESSLY) to my s4, but Verizon forced an upgrade to Lollipop, I hate it and it's been a nightmare for me.
I learned I would have to be root to get the controller to work wirelessly, but I wanted root access for other reasons well such as bloatware removal and interface customization.
So I've been skulking around forums like a hawk, finally I found king root but it wouldn't root my phone and I wasn't about to install it on my PC, too risky... so I waited and waited and waited.
several months pass...
New update for King root will now work to root my phone, and I was able to replace it with super-sume, root checker showed I was rooted and Bazinga! Off I was at last. I removed a couple pieces of bloatware but before I continued I thought it might be wise to reboot the phone while rooted to make sure everything is kosher.
Phone comes back up, no problems. but now ROOT ACCESS IS GONE. I read up and discovered that in some cases the boot-loader will unroot the phone everytime you reboot. I don't want to have to re-root my phone over and over again, that's a pain in the arse.
I read up on some laws felt confident if I called Verizon they wouldn't be able to give me a hard-time, I just wanted to know how to disable the boot-loader locking things up.
I ended up with tier two, who they stated all their 4G devices are unlocked... when I got into the nitty gritty regarding the bootloader the techs I spoke with were lost.
I just want to be able to root my phone and KEEP root. I wish I had Kit-Kat because this wouldn't even be an issue but I don't. Can anyone help? I'm so sick of this crap.
HALP PLZ :crying: :crying:
Another small caveat I should mention, when I reboot my phone, it has an unlocked padlock but root checker states that root access in no longer properly installed and I can't do anything that I'd be able to do rooted either. Before the reboot, root was showing as properly installed.
Wrong forum, there is a Verizon subsection.
Verizon phones are all unlocked...... meaning you can insert whatever SIM card you feel like putting into it.
The bootloader, however, is locked. It will remain locked and it's more than likely never going to be unlocked. Write access is dependent on an unlocked bootloader. The security checks are set up as such that if you attempt to alter the system files, they'll just all return to normal on a reboot.
You can use a temp root method on Android 4.4, but as you figured out.... when you reboot, Bye Bye Root!
There is not, nor has there been, nor will there be a bootloader unlock unless somebody cracks Samsung's encryption keys. You have a better chance of winning the Powerball jackpot than doing that.
Use CF root if you wanna perm and thing solved..

Software: Modified... Not rooted... want to be able to get updates

I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
My phones info;
Software status: Modified
Android Security patch level: May 1 2016
Baseband version: M8992_1253331 .29.01.88.02R SUPER_NA
Kernal Version: 3.10.84-perf-g329ac5f
[email protected] #1
Thu Apr 21 00:11:23 CDT 2016
System Version: 24.221.4.clark_retus.retus.en.US.retus
Build Number: MPHS24.49-18-4
The pending update: New version:24.221.8.en.US
Thank you.
u need to flash official factory image inorder to get the updates
i hardly recommend you to use fastboot and install stock firmware from this site
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick...
install the latest firmware and then check for updates
if u have any queries then go through this.... make sure that u don't mess up
https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Cjet said:
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
Click to expand...
Click to collapse
If I understand your post correctly, and the COMPLETE firmware image was flashed, then you should have no issues taking an OTA update... the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt.
Try this, before you accept and download the update, boot into stock recovery and wipe cache. Or better yet, do a full factory reset and accept the update and apply it, then let it boot fully, do another factory reset and then set it up clean.
I don't know why this happens... it just seems like a few every update won't take it no matter what we do, and for we do not have the latest full factory image yet so there isn't much we can do to find another way.
Thank you both for your reply. However, I am still not clear on something.... there seems to be confusing/conflicting advice regarding the Software "Modified" status and it's role in accepting updates.
1. "if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick..."
2. " the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt."....... If the Software status says "modified" doesn't that mean that the system is indeed modified, and that trying to load the OTA in this state will result in a bootloop? .
u neee to flash official firmware.... the only way to remove modified and change it to official....
it actually doesn't matter that if bootloader is unlock u can install the updates...... i was on may patch and i also wanted to change the software status from modified to official in order to get sept patch... but in moto firmware center the latest was feb 2016.... so i had to downgrade... i tried and it worked... then i was eligible for ota and yes im on sept patch
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Prazaar said:
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
I disagree... it CAN go back to Official, I had several ROMs on my device, then flashed stock image and somehow mine went back to Official. Was mine a fluke? I don't know, but it is clearly Official now. Note the picture clearly shows the bootloader was unlocked (Status 2) and I had at least dozen different ROMs flashed over time before going back to stock using the May 2016 security image and then successfully OTAing up to October security update.
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.
I know what you mean. My Software status is with LineageOS "official" i can flash every rom an the status stuck in official.
Factory img is no warranty for official status but also makes no difference for ota
Getapatalkt vom meinem Moto X Style
thebaconbox said:
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Click to expand...
Click to collapse
Because I am new to all of this and don't know anything about custom Roms. All I want to do is get this thing back to stock.
[/QUOTE
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.[/QUOTE]
Wow, thanks everyone for the suggestions and patience!
OK, so the software status does not affect OTA update installation. Software status being modified does not necessarily mean that the SYSTEM is modified. Yet if the SYSTEM is modified then taking the OTA update will cause a softbrick.
How can I tell if my SYSTEM is modified before deciding on taking the OTA update?
I have had the official Motorola firmware flashed/reinstalled previously by friend's son, and that didn't take the OTA update. It caused soft brick (No Command error bootloop)
I then went to the Motorola site myself, downloaded the firmware and flashed/reinstalled it. This is where I am currently, trying to decide if I should take the update or put it off until I have a couple of hours free to troubleshoot in case the OTA softbricks this thing again (it takes me much, much longer to figure this stuff out than it does for you guys. )
And if that does soft brick it again, then I am not sure what I am doing wrong with the flashing. So, is there any way for me to check to see if the SYSTEM is modified before I try the update.? Thank you!
Sagar_1401 said:
u neee to flash official firmware.... the only way to remove modified and change it to official....QUOTE
This was done twice and still says modified
Click to expand...
Click to collapse
Status modified will change to official after an OTA update.
Sent from my XT1572 using Tapatalk
Anyone? No one knows if there is any way for me to check to see if the SYSTEM is modified before I try the update.?
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Prazaar said:
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Click to expand...
Click to collapse
I don't understand what you are saying. I cannot see "what" if it is modified? Edited - removed earlier rant.
(Sorry)
SOLVED.....
Today I backed everything up, bit my lip and hit "install update". It did update the phone and it did change the software status to "Official". I did this with the bootloader unlocked, and it worked . It does say Status Code 3, and the bootloader unlocked warning screen on startup appears, both of these I am guessing is normal. Everything seems good.

How to OTA update from 6.0.1 with "modified software" (rooted) to Nougat?

So I've been using 6.0.1 since I got this phone last year. I rooted it pretty much immediately, but then Samsung pushed out one of their security patches, which basically "bricked" the software. Whenever I try to update the phone, I get a fine:
The operating system on your device has been modified in an unauthorized way. Try downloading software updates using Smart Switch on your computer or visit a customer service center
Click to expand...
Click to collapse
Basically I rooted my phone, so OTA updates aren't available.
Apparently the new Nougat update is now live in Denmark, so I really want to update my phone, but I don't want to lose my apps, documents, images, and so on. I basically want to do an update, just like I never rooted my phone. I don't care about keeping my root.
How do I go on about this? I just want to "remove my root" and do an OTA update to get Nougat the most legit way possible.
Thanks!
EDIT: I should probably also say, that when I open SuperSU, I get a:
There is no SU binary installed, and SuperSU cannot install it. This is a problem
Click to expand...
Click to collapse
Since that security update from Samsung last summer, my root magically disappeared, but it's still there apparently.

Categories

Resources