Related
While I wait for the arrival of my MXP I have some questions for the community so that I can hit the ground running. First thing, I'd like to unlock my boot loader but I was just curious if there is a way to re-lock it afterwards just in case I need to send in for repairs or something along those lines? Also wondering about VOLTE support. I see some roms that state they have it working but is this a stock feature or do I need to use a custom ROM to get VOLTE to function? Also is there any known method of rooting without unlocking the boot loader just in case re-locking it is not possible? Thanks for the help everyone.
I am coming from a g920a. That phone is torture for someone like me who likes stock Android and rooted devices. Probably the worst phone I have ever had. Can't wait to get my hands on my MXP and leaves this piece of junk behind!
I'm on Verizon and I can confirm it supports advanced calling, which is VoLTE as far as I know but it might require turning it on at the provider level.
Sent from my XT1575 using Tapatalk
I haven't messed with VoLTE yet so I can't answer those questions, but as for your others: The bootloader can be relocked, but the unlock method involves submitting an unlock request code to motorola, and they immediately email you an unlock key, along with a warning about voiding your warranty, so even relocking it does not unvoid your warranty. HOWEVER, it only voids your warranty for software issues. If it's a hardware problem unrelated to the bootloader being unlocked, they'll still handle it, and accidental drops and things are still covered if you buy an accidental damage warrenty. Also, as far as I know there is still no way to root without unlocking the bootloader.
10 characters
squallz506 said:
Volte is only available on stock roms.
Click to expand...
Click to collapse
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
countryfolk07 said:
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Whoops, yeah I guess they fixed it down the line. Sorry, I've been enjoying stock+xposed too much to follow custom development.
Edit: also root without bootloader unlock will likely never happen. We have a root method already, so there's no incentive to find another method.
The answer you seek was right in the first page of this forum....
http://forum.xda-developers.com/moto-x-style/general/moto-x-style-how-to-unlock-bootloader-t3192140
That being said, I would consider waiting until after Marshmallow drops before you unlock your bootloader so as not to interfere with any OTA's. Conventional wisdom is that it is coming within the next few weeks as the "test drive" has already started and a "soak test" should follow shortly.
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
timde9 said:
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
Click to expand...
Click to collapse
Well as to it being a thing, I certainly can't say for sure. But what reason is there to unlock the bootloader if you're not going to root? And once you do that, you almost certainly will not get OTA's. What am I missing? Is there another reason you are looking to unlock?
The one thing I don't know is if there a some type of a "tamper flag" that would require something like triangle away.
You don't think you could just do a fastboot oem lock?
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
I'd still recommend waiting at least a couple of weeks to see if Marshmallow shows up!
I'm coming to the MXPE from a OnePlus One which I have to say was one of the funnest phones I've ever owned. I wasiunlocked, rooted and flashing CM12.1 nightlies about twice a week.
I thought I would miss it, but so far so good on the MXPE without rooting. We'll have to see what happens after MM drops. I'd like to get it rooted, but I haven't done nearly the amount of modding you've done.
Good luck with your phone. I can honestly tell you it's a really nice device!
While its tempting to wait for marshmallow to show I cannot live without root any longer. I have already been without it for months because of this damn s6. I'm sure someone will upload the OTA as soon as it's available so I'll just flash it when the time comes.
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
Well if you're an xposed user you should root immediately with no concern about the 6.0 OTA, since xposed doesn't work on 6.0. I'm not moving to 6.0, myself, until xposed is released for it. I use xposed modules everyday and am not giving it up, not even for doze mode.
That's kinda how I am feeling as well. I can achieve similar results to doze with the xposed app amplify with enough tweaking so its not a big deal.
I've always trusted the devs on this forum and frankly I have no reason to doubt any of them. But I've always wondered how safe and private custom ROMs actually are? How can we know there's no data leaking or a backdoor like we've seen with BLU, Huawei and ZTE sending info to China? How can we trust these devs with all the personal information on our devices? They could have put anything in the code to do anything with them.
I know that sounds like a paranoïd rant ha ha!
But really, given I'm not a dev myself and that, even if I was, checking the code could be really really long, how can we really know?
Prosis said:
I've always trusted the devs on this forum and frankly I have no reason to doubt any of them. But I've always wondered how safe and private custom ROMs actually are? How can we know there's no data leaking or a backdoor like we've seen with BLU, Huawei and ZTE sending info to China? How can we trust these devs with all the personal information on our devices? They could have put anything in the code to do anything with them.
I know that sounds like a paranoïd rant ha ha!
But really, given I'm not a dev myself and that, even if I was, checking the code could be really really long, how can we really know?
Click to expand...
Click to collapse
How sure are you about stock rom not sending any information to non trusted parties?
pijes said:
How sure are you about stock rom not sending any information to non trusted parties?
Click to expand...
Click to collapse
I was expecting that reply especially with the BLU, Huawei and ZTE example and it is absolutely true, we can never be 100% sure.
The difference I see though is that these companies are actually accountable for that sort of thing as is Cyanogen given how big it has grown. If Motorola/Lenovo did such a thing, their brand would suffer and their sales would drop.
But that is not the case for anonymous devs or teams. Plus, it would be hard to hold them accountable (and we'd get the usual and invalid 'they installed it so it's their fault' thing).
You will never be sure, but with all people here using customs roms since several months, with a lot of "power users" / geeks / dev, if there was a big issue regarding security, we should be already aware.
In the other hand i think all these company selling phones are using back doors on their stock roms (especially chinese ones) , sometimes it's the reseller who reflash a rom with malwares ( some resellers on amazon). We know Blu, huawei/honor, Zte, but Lenovo was doing it on their computer ( http://www.makeuseof.com/tag/now-three-pre-installed-malwares-lenovo-laptops/ )
I add that custom roms and custom kernel (especially squid2 if i read release history) are more recently security patched than stock.
fablebreton said:
You will never be sure, but with all people here using customs roms since several months, with a lot of "power users" / geeks / dev, if there was a big issue regarding security, we should be already aware.
In the other hand i think all these company selling phones are using back doors on their stock roms (especially chinese ones) , sometimes it's the reseller who reflash a rom with malwares ( some resellers on amazon). We know Blu, huawei/honor, Zte, but Lenovo was doing it on their computer ( http://www.makeuseof.com/tag/now-three-pre-installed-malwares-lenovo-laptops/ )
I add that custom roms and custom kernel (especially squid2 if i read release history) are more recently security patched than stock.
Click to expand...
Click to collapse
Excellent point (I didn't know that Lenovo did that... Jesus....)
So you would trust custom ROMs over stock?
Prosis said:
Excellent point (I didn't know that Lenovo did that... Jesus....)
So you would trust custom ROMs over stock?
Click to expand...
Click to collapse
Currently yes. The versions and patch level make the point for me. and i havent had any security issue so far.
Prosis said:
I've always trusted the devs on this forum and frankly I have no reason to doubt any of them. But I've always wondered how safe and private custom ROMs actually are? How can we know there's no data leaking or a backdoor like we've seen with BLU, Huawei and ZTE sending info to China? How can we trust these devs with all the personal information on our devices? They could have put anything in the code to do anything with them.
I know that sounds like a paranoïd rant ha ha!
But really, given I'm not a dev myself and that, even if I was, checking the code could be really really long, how can we really know?
Click to expand...
Click to collapse
Most of roms are prerooted, you can run Network Log on them and see if they connect to dodgy IPs behind your back. Firewalls can also log traffic.
minimale_ldz said:
Most of roms are prerooted, you can run Network Log on them and see if they connect to dodgy IPs behind your back. Firewalls can also log traffic.
Click to expand...
Click to collapse
That's a very good point! The same as on Linux distributions.
Can this be done on Cyanogenmod too or I have to root it?
Prosis said:
That's a very good point! The same as on Linux distributions.
Can this be done on Cyanogenmod too or I have to root it?
Click to expand...
Click to collapse
AFAIK CM comes with root as well (you may need to turn it on in Developer's settings).
As everyone on here probably knows, z5 premium will not be getting any further security updates. Its timing couldn't have been any worse either. When I bought this premium phone (which costs almost as much as a flagship iphone), I didn't expect to have my security updates cut in just 2 years. I was planning to hang onto this phone for a few years until something worth upgrading to came out.
So like many who still own this phone, I am wondering is there anyway to keep my phone secure and still use it? My phone is unlocked and rooted and I am running the latest firmware. I unfortunately didn't back up my drm keys so I had to use the hack method to keep my phones functionality (fingerprint sensor, camera...etc) I'm wondering what is the best close to stock firmware to use to get the latest security updates and also how much functionality is lost by using those? It's to my understanding the camera only works the best with the official camera app and 4k only works on the album app and movie app. Will I lose 4k capability by switching to a custom firmware?
Any insight on any of this would be greatly appreciated.
Thanks to all who took the time to read this and a big thanks in advance to anyone who can provide any input.
Mostly updated custom kernel + custom ROMs (Sony Stock ROM + kernel based)
e.g. https://forum.xda-developers.com/z5-premium/development/m-rom-t3781969
and
https://forum.xda-developers.com/showpost.php?p=76269595&postcount=418
well, newer custom kernels will have WPA2 KRACK protection, protection/mitigation against Meltdown/Spectre (a class of timing-based) attacks and other fixes & improvements
updated binaries for e.g. wpa_supplicant might be needed but I haven't really looked into those details yet
Thanks. Is it possible to use a custom kernal like the one you provided in your second link with the latest official firmware (32.4.1.54) since I only care about updating my security?
Mike3009 said:
Thanks. Is it possible to use a custom kernal like the one you provided in your second link with the latest official firmware (32.4.1.54) since I only care about updating my security?
Click to expand...
Click to collapse
sure, flash TWRP (if not already done so),
do a backup of each partition separately (/boot , /data , /system)
and flash the kernel
it'll update /boot and modules in /system
zacharias.maladroit said:
sure, flash TWRP (if not already done so),
do a backup of each partition separately (/boot , /data , /system)
and flash the kernel
it'll update /boot and modules in /system
Click to expand...
Click to collapse
I appreciate the help and sorry for all the questions. Is backing up the partitions still necessary if I already have a backup of the firmware from xperifirm? Yes I already have TWRP because I used it to root my device. Also I'm assuming the kernal I want is on the first post of the second link you shared with me but there are two files to be downloaded and I'm not sure which to use. I'm on a z5 premium e6853.
Thanks again.
Mike3009 said:
I appreciate the help and sorry for all the questions. Is backing up the partitions still necessary if I already have a backup of the firmware from xperifirm? Yes I already have TWRP because I used it to root my device. Also I'm assuming the kernal I want is on the first post of the second link you shared with me but there are two files to be downloaded and I'm not sure which to use. I'm on a z5 premium e6853.
Thanks again.
Click to expand...
Click to collapse
I just flashed over the first one with fastboot. Worked fine. Security is still showing September 2017 though. Is there anyway I can know if I'm more secure now?
Mike3009 said:
I just flashed over the first one with fastboot. Worked fine. Security is still showing September 2017 though. Is there anyway I can know if I'm more secure now?
Click to expand...
Click to collapse
you take a look at the source in github
sorry, the ROM base is the same [and thus you're affected by the vulnerabilities, so best would be to re-enable SELinux which gives quite a good protection itself],
kernel-side however got you covered (well, it really depends how much the kernel is patched up).
You, of course, could try out RR, LineageOS which are somewhat more up-to-date (updates stopped being added November / December last year for Android 7.1.y),
but there you'd lose e.g. picture stabilization on video recording, MHL, MirrorLink, superior post-processing on pictures, etc.
The problem with these device (Snapdragon 810) is that Qualcomm dropped support for the msm8994 platform,
and since we're stuck with 3.10 kernel it's a community effort to get it patched up somewhat.
There'd be the possibility to upgrade & port the kernel to 4.4 but since the API, etc. would mismatch and newer drivers are missing it's basically not worth the effort
zacharias.maladroit said:
you take a look at the source in github
sorry, the ROM base is the same [and thus you're affected by the vulnerabilities, so best would be to re-enable SELinux which gives quite a good protection itself],
kernel-side however got you covered (well, it really depends how much the kernel is patched up).
You, of course, could try out RR, LineageOS which are somewhat more up-to-date (updates stopped being added November / December last year for Android 7.1.y),
but there you'd lose e.g. picture stabilization on video recording, MHL, MirrorLink, superior post-processing on pictures, etc.
The problem with these device (Snapdragon 810) is that Qualcomm dropped support for the msm8994 platform,
and since we're stuck with 3.10 kernel it's a community effort to get it patched up somewhat.
There'd be the possibility to upgrade & port the kernel to 4.4 but since the API, etc. would mismatch and newer drivers are missing it's basically not worth the effort
Click to expand...
Click to collapse
That's too bad. I guess it's as I thought; there's no real perfect solution to staying secure at the time being. Well, thanks for the kernal anyways. I can't believe how much better my phone is now. It has me puzzled why Sony didn't release it like this in the first place.
Mike3009 said:
As everyone on here probably knows, z5 premium will not be getting any further security updates. Its timing couldn't have been any worse either. When I bought this premium phone (which costs almost as much as a flagship iphone), I didn't expect to have my security updates cut in just 2 years. I was planning to hang onto this phone for a few years until something worth upgrading to came out.
So like many who still own this phone, I am wondering is there anyway to keep my phone secure and still use it? My phone is unlocked and rooted and I am running the latest firmware. I unfortunately didn't back up my drm keys so I had to use the hack method to keep my phones functionality (fingerprint sensor, camera...etc) I'm wondering what is the best close to stock firmware to use to get the latest security updates and also how much functionality is lost by using those? It's to my understanding the camera only works the best with the official camera app and 4k only works on the album app and movie app. Will I lose 4k capability by switching to a custom firmware?
Any insight on any of this would be greatly appreciated.
Thanks to all who took the time to read this and a big thanks in advance to anyone who can provide any input.
Click to expand...
Click to collapse
yes! sony treated this device as their step son!
released late 2015, hit market 2016, and was already in LEGACY DEVICES in 2017, the whole series discontinued and after many months they released android 7.1.1 and thats it, no more builds or updates!
feel sorry for the device, it has all the premium features but treated badly!
- the 4k capability depends on which 3rd party rom you are using! , btw not many roms are available for z5p
YasuHamed said:
yes! sony treated this device as their step son!
released late 2015, hit market 2016, and was already in LEGACY DEVICES in 2017, the whole series discontinued and after many months they released android 7.1.1 and thats it, no more builds or updates!
feel sorry for the device, it has all the premium features but treated badly!
- the 4k capability depends on which 3rd party rom you are using! , btw not many roms are available for z5p
Click to expand...
Click to collapse
Yeah I know, it's pathetic really. It's still a very current device as it was a very high spec phone when it was released. High spec phones like these don't get outdated that quickly. It's even more insulting that they cut support right as the meltdown vulnerability came out. They knew what they were doing -it's like a forced upgrade. Problem is: there is nothing released by Sony that really surpasses this phone in specs, or at least not enough for most people to be willing to spend all that cash on a new phone when their current one works perfectly. I don't see any compelling reason to run out and get an xz premium unless my phone breaks and dislike the xz2 premium. Oh well, I'll just have to use caution and hope for the best until a phone worth upgrading to comes out or my phone dies. Whatever happens first I suppose. Thanks for the sympathy.
Mike3009 said:
Yeah I know, it's pathetic really. It's still a very current device as it was a very high spec phone when it was released. High spec phones like these don't get outdated that quickly. It's even more insulting that they cut support right as the meltdown vulnerability came out. They knew what they were doing -it's like a forced upgrade. Problem is: there is nothing released by Sony that really surpasses this phone in specs, or at least not enough for most people to be willing to spend all that cash on a new phone when their current one works perfectly. I don't see any compelling reason to run out and get an xz premium unless my phone breaks and dislike the xz2 premium. Oh well, I'll just have to use caution and hope for the best until a phone worth upgrading to comes out or my phone dies. Whatever happens first I suppose. Thanks for the sympathy.
Click to expand...
Click to collapse
sony never forgets to disappoint their customers by keep releasing unfinished flagships on the frequency of new bulletins!
whole z series abandoned after z5p due to huge billions of book losses to sony in xperia project. the device should have been with 4gb ram! but instead it was kept on 3gb!
z5p is awesome device, stable, stays in control and maintain itself amazinly!
now xzp came out finally with 4gb ram (should have been 6)
where xz2p is coming with 6gb ram and strange bumpy design and misplaced finger print sensor!
i don't know what sony is up to!
What's really disappointing is the lack of roms being developed. The prices are getting pretty nice right now for the z5 premium after support was dropped making it an attractive, affordable 4k smartphone for new comers. Also for those of us who already own it, having at least one decent rom solution would be really nice. It's pretty sad that I'd have to give up some of the functionality that I paid for in order to continue to keep my device secure. I'm going to stick to official firmware with anti-virus along with this updated kernel and hope for the best. I'd very much appreciate it if anyone finds a good custom firmware solution, to please let me know. Thanks in advance.
YasuHamed said:
yes! sony treated this device as their step son!
released late 2015, hit market 2016, and was already in LEGACY DEVICES in 2017, the whole series discontinued and after many months they released android 7.1.1 and thats it, no more builds or updates!
feel sorry for the device, it has all the premium features but treated badly!
- the 4k capability depends on which 3rd party rom you are using! , btw not many roms are available for z5p
Click to expand...
Click to collapse
zacharias.maladroit said:
you take a look at the source in github
sorry, the ROM base is the same [and thus you're affected by the vulnerabilities, so best would be to re-enable SELinux which gives quite a good protection itself],
kernel-side however got you covered (well, it really depends how much the kernel is patched up).
You, of course, could try out RR, LineageOS which are somewhat more up-to-date (updates stopped being added November / December last year for Android 7.1.y),
but there you'd lose e.g. picture stabilization on video recording, MHL, MirrorLink, superior post-processing on pictures, etc.
The problem with these device (Snapdragon 810) is that Qualcomm dropped support for the msm8994 platform,
and since we're stuck with 3.10 kernel it's a community effort to get it patched up somewhat.
There'd be the possibility to upgrade & port the kernel to 4.4 but since the API, etc. would mismatch and newer drivers are missing it's basically not worth the effort
Click to expand...
Click to collapse
How can we enable selinux?
I've been reading the various rooting threads for a couple of days and overall the process seems pretty complicated with many different Nokia 6 versions, and different tools to use, etc.
Is there a way to get root with just the stock bootloader? I only want to do a few sudo operations once in a while, not flash any ROMs. Is this possible somehow? I'm using TA-1003 with 8.0.0 + April security update.
Thanks
leekohlbradley said:
I've been reading the various rooting threads for a couple of days and overall the process seems pretty complicated with many different Nokia 6 versions, and different tools to use, etc.
Is there a way to get root with just the stock bootloader? I only want to do a few sudo operations once in a while, not flash any ROMs. Is this possible somehow? I'm using TA-1003 with 8.0.0 + April security update.
Thanks
Click to expand...
Click to collapse
Your best bet is to return the phone. Nokia has made a really, really bad bet by locking the boot loader. I think that by getting burnt by windows, they decided to jump back into the frying pan again. They don't understand what "OPEN SOURCE SOFTWARE" is. If they had a clue, they would not lock the boot loader. I returned mine because there will not be any active development or roms. I wanted the phone so I could root it, like you, and then unlock the sound features from the sound chip. So, don't bother rooting the phone, just return it or keep it stock.
In a year or two, Nokia will flop or get the idea that they want active development so people will buy their phones. It is a bad way to enter the market.
In principle I agree but I've used the phone for almost a year lol and sadly the power user community is really very small and so there's not much motivation for Nokia to make open phones. This seems especially true to me, since they're offering the phone as an Amazon prime adware phone, for example, so there is in fact a motivation to not open the phone, since it might let users remove the adware from their subsidized hardware... My 2mBTC
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device. ?
Inerent said:
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device.
Click to expand...
Click to collapse
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
trabadura said:
j4nn said:
trabadura said:
Hi j4nn, i see your post in xda for temp root Sony XZ1c with Snapdragon 835 and I figured you could help us for temp root Verizon Google Pixel 2 Xl for Unlock Bootloader?
Click to expand...
Click to collapse
Hi, I am not sure about that - I do not have that phone and cannot get/borrow it for testing either.
Do you know if it is possible to downgrade it's firmware?
Can you point me to earliest fw for download that it can be downgraded to?
What exactly the problem is - bootloader is not possible to unlock because Verizon (is it a mobile network operator?) disabled bootloader unlock possibility while on general not Verizon variant google allows it?
Is it also sim locked to Verizon operator only?
And how do you know that getting temp root would help you?
Click to expand...
Click to collapse
Hi, аs far as I know, it can not downgrade firmware with locked bootloader. With unlocked bootloader no problem.
The problem is in mobile operator. They lock option "OEM Unlock" (stay grayed out) in developer option. In general not Verizon variant no problem option is active and no problem to unlock bootloader. No sim locked only bootloader. Тhere is a lot of writing about the topic I can give a few links in the forum.
Links:
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
Click to expand...
Click to collapse
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
j4nn said:
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
Click to expand...
Click to collapse
You are completely right. And that is the difference between Android and iPhone communities. Every Android user prefer to stay aside of this problem, naively thinking that they would not be affected. In Oreo Google has already put all the Root CAs into the System storage. So Nobody knows what kind of data the phone uploads every day to 3rd party servers. Verizon is just an example there are many companies who do the same. iPhone community is great because everybody know that some day under certain circumstances they can lost their JB. I hope one day some mid-range iOS developer will buy Android phone and start developing a great root tools. Sure it will be quite easy because all the source code is available.
I appreciate your work. Thank you and good luck.
First they came for the socialists, and I did not speak out—
Because I was not a socialist.
Then they came for the trade unionists, and I did not speak out—
Because I was not a trade unionist.
Then they came for the Jews, and I did not speak out—
Because I was not a Jew.
Then they came for me—and there was no one left to speak for me.