I've read a few posts stating the bootloader exploit for the S4 would be relatively easy to patch by At&t and my concern is that they may do so before my upgrade on June 7. If at&t does patch it before then would it be possible to use Odin to downgrade the phone to an earlier firmware release that doesn't have the patch? If not I'll have to figure out a way to get the phone as soon as possible.
calvin35 said:
I've read a few posts stating the bootloader exploit for the S4 would be relatively easy to patch by At&t and my concern is that they may do so before my upgrade on June 7. If at&t does patch it before then would it be possible to use Odin to downgrade the phone to an earlier firmware release that doesn't have the patch? If not I'll have to figure out a way to get the phone as soon as possible.
Click to expand...
Click to collapse
I don't see how anyone could know that for sure at this point. However, if a patch is released (OTA) or if newer firmware is put on the phones that patches the vulnerability itself, then it seems realistic that ODIN probably will not be able to fix the issue. Once it is patched, you probably won't be able to go back. Of course, another exploit might be found or Adam's attempt at a more permanent bottloader unlocker might find a solution. OTA updates can be fixed by just not taking them until they are cleared as OK. Newer firmware on the phone would probably need another fix. But nobody knows how long it will be until AT&T / Samsung patches the vulnerability.
Related
Hello all! I know that on NK2 and lower there's been the ability to downgrade and upgrade firmware using Odin. However, with the Lollipop update coming soon is it possible that that could be fixed and the bootloader could be updated to fix that? Also, is it possible that (if it is a bootloader update that would fix that) that there would be an exploit left in there for the bootloader to be unlocked, and if there is what are the odds of someone finding the exploit?
With every update has come tighter and harder to crack security. Right now the chances of the bootloader being unlocked are slim to none. With the lollipop update, I would think those chances would fall to below zero and into the negative probability.
landshark68 said:
With every update has come tighter and harder to crack security. Right now the chances of the bootloader being unlocked are slim to none. With the lollipop update, I would think those chances would fall to below zero and into the negative probability.
Click to expand...
Click to collapse
With Lollipop any phones that are in proximity to your Samsung device will have their boot loaders locked as well.:laugh:
mrjiggywiggy said:
Hello all! I know that on NK2 and lower there's been the ability to downgrade and upgrade firmware using Odin. However, with the Lollipop update coming soon is it possible that that could be fixed and the bootloader could be updated to fix that? Also, is it possible that (if it is a bootloader update that would fix that) that there would be an exploit left in there for the bootloader to be unlocked, and if there is what are the odds of someone finding the exploit?
Click to expand...
Click to collapse
being able to downgrade firmware isnt asomething they might "fix" since it is not something broken, it was meant to be that way.. now them making L to where it is not downgradeable is very likely since it will be a whole new OS/Firmware than 4.4.x with a slightly new file structure/runtime.
I think its time to realise that the S5 will NOT have an unlocked bootloader and if it does it will not happen until weve most likely moved on to other devices. The only hope for an unlock is if a dev working on the Note 4 or another ddvice find an exploit that also works on our S5 since I havent heard any devs still working on it with our device.
I believe root will be possible on L if you are patient and dont take the OTA and wait for a dev to push a L rom.zip and odin firmware. (Theres no reason I can think of as to why this would not work as it always has)
What can i do to solve this problem? is there a way to restore a previous version without rooting it? because i obviously can't do that... N900VVRSEPL1 is the version i have.
See page 3 of "Official Verizon Update???" thread
https://forum.xda-developers.com/verizon-galaxy-note-3/general/official-verizon-update-t3538935
This (PL1) update appears to be a security patch release, so it's probably not surprising that former rooting methods for OB6 & OF1 no longer are working - that's the point of security updates.
Same experience here. I would bet that however these tools are getting root will probably work on PL1. It seems that in running the tools, the tools simply don't recognize PL1 as a working version and don't try. I don't know that for certain, it's just a guess.
LSkeeno said:
What can i do to solve this problem? is there a way to restore a previous version without rooting it? because i obviously can't do that... N900VVRSEPL1 is the version i have.
Click to expand...
Click to collapse
Just get to sammobile and search your device then select 5.0 OF1 and flash whit odin, the it gonna get back again you will get root by using arabicktool. Saludos!!
Has anyone received this update? My wife just got it tonight, and she INSTANTLY accepted it. I can't find a single reference to it and I'm a little nervous about the nature of it. Can anyone confirm that this is a legitimate version of the software?
Received last night, everything works as usual, security patch level March 1st
Also Received
I also received however, mine has Android security patch level 2/1/2017. Just letting you know your wife's not alone in getting the patch.
Its April and there sending out a February Security Patch, epic fail. LMAO LG
just keep in mind that this DOES patch dirtycow so no root will be possible.
Possible to revert to original?
Even though this blocks rooting, would it be possible to revert to an older update that is still rootable?
hattwj said:
Even though this blocks rooting, would it be possible to revert to an older update that is still rootable?
Click to expand...
Click to collapse
No because there is no KDZ for an older version.
I was wondering how many and what updates everyone else have received and when?
I'm currently on the April 2017 security update and I received that in early June I believe.
I'm hoping Huawei can at least be excused by the fact they're working on an Oreo update instead of doing security updates and bug fixes (highly doubtful though). Mine is a Nordic unlocked model by the way.
So are anyone else receiving security updates?
Not here, in Spain. The thing is, I don't see any security patch coming till next EMUI version arrives, hopefully before the end of the year.
Not sure if this helps, but I found some way opening another security gap
As far as I figured out, you need 3 files for the update to work:
update.zip
update_full.zip (or update_full_WAS-XXX_hw_eu.zip)
update_data_full_public.zip
I am sure, FirmwareFinder or any other tool might come in handy doing so. The next thing you'd need would be TWRP which is available as some beta build somewhere on this forum. Then you'd have to unlock the bootloader and root your device to get TWRP on it. I'd recommend doing some research on this as you might have to get some code for "fastboot oem unlock"...
Flash the files listed above the way they're listed.
Hello XDA community,
This is my first post on here and I hope I'm not doing something wrong in terms of protocol, but I have a rough idea on finding a root for this phone that needs support and refining from you guys, the XDA community.
My idea is this: If we can find a way to downgrade the phone software back to before the December 2016 security patch, we can run a Dirty Cow root exploit (, which is ready to go on GitHub, ) to temp root this device (or any device, in theory). Once we have temp root, we could run a program like SunShine or whatever else to turn that temp root to perm root. (SunShine currently says that, to full root this device, it needs some kind of temp root.)
Now going back to the first part about downgrading the software to before the December 2016 security update, I initially thought we could achieve this through mfastboot or RSD Lite, since they allow flashing of officially signed Motorola firmwares. However, I read that when upgrading the Moto Z, and presumably all other variants, from Android MM to Android N, the (locked) bootloader is updated, too, and will not allow downgrading, resulting in a prevalidaton error. This is where I need your help.
The question is: How can we downgrade the firmware back to MM, or some other before-December firmware, to use Dirty Cow for root. Please leave ANY suggestions in the comments.
Thank you for your time and help. I have faith that we will be able to solve this together.
I don't think you can downgrade. But i've been running this for the past 9 or so months to prevent the forced updates: https://forum.xda-developers.com/moto-z-play/themes/app-moto-z-play-apps-stop-ota-motocare-t3538812
(no idea if that would work on the z force)
Well I know there are many videos on YouTube claiming to downgrade certain Moto devices through RSD Lite or mfastboot for different budget Moto devices, but I suspect they are all fake. Nonetheless, I hope there is a legitimate way to downgrade.
I forgot to mention that if you can get a replacement Moto Z Force from Verizon, which is very easy to do in my area, they ship you a refurbished replacement, which runs marshmallow and has no updates installed, but I don't have the opportunity to get another replacement, so for anyone else, that's one way you could "downgrade" and try Dirty Cow to root the device.
I'm just going by this topic https://forum.xda-developers.com/moto-z/how-to/dont-upgrade-to-nougat-ota-t3524456
but i don't really know for sure
Wow. Now I wish I'd known about this MUCH sooner. Its too late for me. Well, in that case, try to see if you can revert back to marshmallow if you unofficially upgraded to nougat and check what month of security patches you are on. If it's before the December 2016 security patch, then you can run Dirty Cow and get temporary root. With temp root you can most likely find a way to make it permanent root.