Will Fingerprint always pose a problem for custom roms (LOS especially)? - OnePlus 6T Questions & Answers

So i've been reading threads and trying to decide between 6/6t. I would run OOS for a while i'm sure but would want to migrate to LOS eventually. I wouldn't ever use a FaceID type authentication. I use max password length and only use fingerprint once booted/decrypted.
My question is am i better off just going for the 6 with the tried/true established fingerprint scanner, or if it is likely that LOS or other popular roms will have full-functionality with onscreen print anytime soon (spring/summer 2019?)
Similarly, how soon can it be roughly estimated that we will know whether a tmobile full conversion to International is permanent / can relock bootloader beyond 9.0.7 ? Is it simply a matter of waiting for the next OTA?
I'm a bit of a newb and i apologize. I'm not pushing for faster development or anything at all. I generally donate to the projects i make use of. I would appreciate some insight to this.
It might be a bummer to get the 6 and then a couple weeks later see that the 6t is in fact a better phone for my purpose.

Fingerprint will be 100% working within a few months. Just gotta be reverse engineered.

me2151 said:
Fingerprint will be 100% working within a few months. Just gotta be reverse engineered.
Click to expand...
Click to collapse
i thank you for your insight. What a guy.

Related

Just purchased a MXP and have questions

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.

OnePlus Security: Think Before You Buy

So, OnePlus is going to release a new phone! People are excited and have forgotten about everything bad that happen with the previous devices. The PR machine started publishing "amazing" photos from the 5T camera (they did the same with the not-that-good OP5) and everyone is ready to open their wallets.
I just wanted to remind everyone about OnePlus privacy and security "mistakes", something that is usually ignored by the fancy YouTube reviewers and android related websites. This week we have a new security issue:
OnePlus Accidentally Pre-Installed an App that acts as a Backdoor to Root Access
Last month we learned that OxygenOS is Allegedly Data-mining Personally Identifiable Information for Analytics... And back in February someone discovered a bootloader issue that worked as a backdoor.
These days we use our phones for more than simple voice calls. We use apps that have access to important parts of our lives (banking, social networks, IoT, etc) and store a lot of information on our phones.
Security is important and it should be taken into consideration when buying a new phone.
I think most people here go out of their way to unlock their bootloader and root anyways.
So I'm pretty sure this topic in general here is pointless.
Nonetheless it is a valid point, though its not that meaningful here.
If you are really worried about security you'd go with a blackberry out a pixel
@Expliciate What I've seen with the 3/3T is that while many users use custom ROMs and are not affected by OOS issues, others just unlock their bootloader and use root, but stay on stock OOS or OOS beta.
I agree with you... the people that should be warned about these issues will not read this thread. Anyway, if we are aware of the problem maybe we will think twice before buying, suggesting or using Oneplus hardware or software.
@worldsoutro You don't have to be "really worried" about security to understand that something is wrong when people keep finding security holes on Oneplus software.
Three points keep me from jumping on board
No new snapdragon
Fingerprint sensor on the back
And finally ...what about jelly?
My two cents
I am wondering if anyone knows about any vulnerabilities/backdoors in the phone, outside of the Oxygen OS, such as in the aboot, sbl, etc.
Oxygen OS can be done away with, albeit by the power users.
This kind of app must be preinstalled on all devices by Google !!
Without root Android phone is useless for me, I would better to use nokia 3310 instead than.
I hope oneplus will rewrite this app and keep it for all generation of their phones.
S4turno said:
You don't have to be "really worried" about security to understand that something is wrong when people keep finding security holes on Oneplus software.
Click to expand...
Click to collapse
I actually prefer people finding/reporting bugs with OnePlus caring for resolving the mentioned issues to people not finding/reporting bugs and/or a company which ignores them.
x111 said:
This kind of app must be preinstalled on all devices by Google !!
Without root Android phone is useless for me, I would better to use nokia 3310 instead than.
I hope oneplus will rewrite this app and keep it for all generation of their phones.
Click to expand...
Click to collapse
My phone is rooted, it's one of the first things I do when I buy a new phone, but let's not turn another security fu** up into a good thing.
Oneplus devices are not just for "nerds" anymore. In the UK, for example, a network (O2) sell their phones just like they sell iPhones and Galaxys. They advertise on newspapers, trains, etc. Normal users, that use their phones for many things, don't know what TWRP or a custom ROM is. This is an issue.
By the way, the guy who found this app keeps posting new stuff on twitter: https://twitter.com/fs0c131y/status/930773795656396801
Rosa Elefant said:
I actually prefer people finding/reporting bugs with OnePlus caring for resolving the mentioned issues to people not finding/reporting bugs and/or a company which ignores them.
Click to expand...
Click to collapse
And I agree, no software is bug free or completely secure and we all benefit when bugs are found and fixed.
The problem here is that some of these issues should never be there in the first place. Looking at the security holes from the past 2 years, it's clear to me that software is one of OnePlus weak points. For example, the bootloader problem that was fixed earlier this year was an amateur mistake... either that or they don't even know it could be an issue.
And it's not like people are not trying to find issues on Google's new Pixel or on Samsung's flagships... there's even a big market for that! But it's harder to find issues because these companies have people that know what they are doing.
I think something is wrong when using an aftermarket ROM is safer than using OxygenOS. We should be aware of these issues when buying something from them.
S4turno said:
And I agree, no software is bug free or completely secure and we all benefit when bugs are found and fixed.
The problem here is that some of these issues should never be there in the first place. Looking at the security holes from the past 2 years, it's clear to me that software is one of OnePlus weak points. For example, the bootloader problem that was fixed earlier this year was an amateur mistake... either that or they don't even know it could be an issue.
And it's not like people are not trying to find issues on Google's new Pixel or on Samsung's flagships... there's even a big market for that! But it's harder to find issues because these companies have people that know what they are doing.
I think something is wrong when using an aftermarket ROM is safer than using OxygenOS. We should be aware of these issues when buying something from them.
Click to expand...
Click to collapse
While I can see a use for this you have to keep something in mind. All devices sold from China based companies will always have something like this. Mainly die to the laws requiring monitoring software to be installed. This comes from their right to monitor everything their citzens do on line and with their mobile devices. It is part of the reason most China OEM are not allowed in places with high security needs.
Actually....I think Oxygen OS is ONEPLUS's biggest differentiator.
And it's excellent.
It's fast, it's smooth, no-one does updates better.
They will have to double down on security but nobody does software like ONEPLUS.
kolembo said:
It's fast, it's smooth, no-one does updates better.
Click to expand...
Click to collapse
"Fast and smooth" are two of the major gains of Android 7. Even my old(ish) LG is still adequately fast and smooth. :good:
kolembo said:
Actually....I think Oxygen OS is ONEPLUS's biggest differentiator.
And it's excellent.
It's fast, it's smooth, no-one does updates better.
They will have to double down on security but nobody does software like ONEPLUS.
Click to expand...
Click to collapse
That is open for debate. I personally think it is one of the worst available. If you really think it is fast and fluid you should try an aosp based rom.
How do the Slim ROMs perform on OnePlus?
zelendel said:
While I can see a use for this you have to keep something in mind. All devices sold from China based companies will always have something like this. Mainly die to the laws requiring monitoring software to be installed. This comes from their right to monitor everything their citzens do on line and with their mobile devices. It is part of the reason most China OEM are not allowed in places with high security needs.
Click to expand...
Click to collapse
So, all these issues are related to OOS. Is it likely to be present in custom ROMs too as they too use kernel codes released by Oneplus? Thinking of buying OP 5T.
unos21 said:
So, all these issues are related to OOS. Is it likely to be present in custom ROMs too as they too use kernel codes released by Oneplus? Thinking of buying OP 5T.
Click to expand...
Click to collapse
Not all issues are OS related. For example, the bootloader issue from Feb 2017 couldn't be fixed with a custom ROM.
Things like analytics and shady apps are not present on very well know custom ROMs not based on OxygenOS (LineageOS, OmniROM, Paranoid Android, etc), but keep in mind that the camera quality will never be as good as stock.
unos21 said:
So, all these issues are related to OOS. Is it likely to be present in custom ROMs too as they too use kernel codes released by Oneplus? Thinking of buying OP 5T.
Click to expand...
Click to collapse
Yes but most of the code is not kernel related. Very little of it is. It is in the format of "services" and hidden apks like the last one found.
Not gonna lie, I purchased a OnePlus One because of the development community. I usually flash a different ROM straight away.
I bought a OnePlus 5 hoping that would be the same situation. It's not. Don't get me wrong, it's not bad, but it's not like my Nexus phone.
The OnePlus 5T? My understanding is that until the 21st of November, there is a media embargo. After that, there will be more information about the device.
I'll make a decision after that.
ToucanSam said:
My understanding is that until the 21st of November, there is a media embargo.
Click to expand...
Click to collapse
Depends on how usual the reviewer models are.

bit of update concerning kernel development

Hey there,
Most of you have noticed there is no to very low development for our devices.
For what is worth, there is development, and it is awesome.
We have a very nice device and with great kernel I can assure you that you will be amazed by the performances and battery life for this device.
*I'm currently testing a custom kernel (Hex), and even if it's still a bit of a pain to flash it (twrp need to be installed on one partition and kernel on the other "side") so you need a PC to get it flashed.
So. Please be a bit patient and it will be awesomely rewarded
I wrote this post to all fearing no dev. For the mia2, there is, and damn it's DDucking awesome
Have a nice day!
Regards,
H.
Thanks :good::good:
Wow! It's good to know this,
I would like to see the growing number on the development for this device to the point like other popular device such as my old Redmi Note 4 (its running awesome when installed LOS Oreo). The thing is this A/B partition on MiA2 seems to be complicated and have a high risk if you do wrong from my perspective. With that reason I still keep my phone as it is for now, looking forward for more development and tweaks tho
mark.dx said:
I would like to see the growing number on the development for this device to the point like other popular device such as my old Redmi Note 4 (its running awesome when installed LOS Oreo). The thing is this A/B partition on MiA2 seems to be complicated and have a high risk if you do wrong from my perspective. With that reason I still keep my phone as it is for now, looking forward for more development and tweaks tho
Click to expand...
Click to collapse
Yes, me too, even just try to unlock and just enable camera2api without root can turn in a briked device. So i will wait for an oficial TWRP that don´t transform my A2 in to a brick. like this user:
https://forum.xda-developers.com/showpost.php?p=77825415&postcount=13
ki69 said:
Yes, me to even just try to unlock and just enable camera2api without root can tur in a briked device. So i will wait for an oficial TWRP that don´t transform my A2 in to a brick. like this user:
https://forum.xda-developers.com/showpost.php?p=77825415&postcount=13
Click to expand...
Click to collapse
Mmh, it's definitely way too early to use any tool. God knows what the tool will do (it's just an automated batch based on ADB/fastboot aka. Platform tools) ?
Again, it's currently a pain to flash anything but at least, it's now 100% stable (if manually flashed with correct ADB (last) version.
?
Just a question of time that everything goes to the "noob-world" <- no offense we, just another way to say "bulletproof secure"
I got mine converted to Mi 6X (wayne) and I have only A partition slot. A/B it's ****. I also earned some internal storage space (around 4 Gigs) by doing this. I flashed back AEX and all is good! There is also a fixed vendor coming up which will allow to run every GSI image out-of-the-box without any bugs, thanks to Manish!
If you want guys, I can make a step by step guide on how to root and use magisk, substraum and gcam
It is very easy in my opinion, can be done in 5 minutes
I think that could be actually great. It took me some times to harvest all Infos and find a way which was making some sense. No rant on devs. But a clear way step by step would be great. At least to answer the 2000 message I get on "how-to do it" ????
For substratum not needs always root....Andromeda + substratum works very fine on stock devices(Andromeda cost is very small)
A2 certainly needs an official twrp,first than all....perhaps it will come soon, the device is still new...
mark.dx said:
The thing is this A/B partition on MiA2 seems to be complicated and have a high risk if you do wrong from my perspective.
Click to expand...
Click to collapse
It was an issue in the past, but now that there's wide support for the Google Pixel (which even has official LOS) things just got a lot easier. A/B is a non-issue for the end-user, the developer does need to check how things are done in the Pixel (which takes valuable time), but shouldn't be a deal breaker as everything is already public.
IMHO the real issue is the fact the Mi A2 wasn't really that popular to begin with (among the kind of enthusiasts that would only ever run a custom ROM, that is). When it launched, those enthusiasts preferred the whyred (which already had great support, namely official LOS). Shortly after, Poco happened.
I honestly think this device will be like most others, custom ROMs will either come straight from GSI (when vendor is fixed) or only after the Android One support ends (aka. when we'll be pressed to do something).
It's not too bad at all, it's just slightly disappointing because (1) Xiaomi timed their product releases poorly, not giving enough information to make an informed purchase; and (2) we kinda of expected a little more from Android One than to be grounded to stock or (now) a GSI.
At the end of the day it is up to us (everyone in this community) to do something about it (ie. start working on the device instead of expecting someone else to pick that job). Harsh words, but true nonetheless.
enapah said:
It was an issue in the past, but now that there's wide support for the Google Pixel (which even has official LOS) things just got a lot easier. A/B is a non-issue for the end-user, the developer does need to check how things are done in the Pixel (which takes valuable time), but shouldn't be a deal breaker as everything is already public.
IMHO the real issue is the fact the Mi A2 wasn't really that popular to begin with (among the kind of enthusiasts that would only ever run a custom ROM, that is). When it launched, those enthusiasts preferred the whyred (which already had great support, namely official LOS). Shortly after, Poco happened.
I honestly think this device will be like most others, custom ROMs will either come straight from GSI (when vendor is fixed) or only after the Android One support ends (aka. when we'll be pressed to do something).
It's not too bad at all, it's just slightly disappointing because (1) Xiaomi timed their product releases poorly, not giving enough information to make an informed purchase; and (2) we kinda of expected a little more from Android One than to be grounded to stock or (now) a GSI.
At the end of the day it is up to us (everyone in this community) to do something about it (ie. start working on the device instead of expecting someone else to pick that job). Harsh words, but true nonetheless.
Click to expand...
Click to collapse
This should be stickied somewhere, this is exactly what happened and what needs to be done. True words
by any chance will this work with mi 6x?
mugentech said:
by any chance will this work with mi 6x?
Click to expand...
Click to collapse
Some have tried, it doesn't unfortunately ?
Aww. Was hoping it would work on 6x since it's faster atm
Ähm.. mia2 + Hex Kernel is soooo faster than mi6xx ? and 6-7h of SOT on wifi (5-6h on 4g)
Again, a bit of patience, it will be all good. It is already for motivated flashers
dodjob said:
Ähm.. mia2 + Hex Kernel is soooo faster than mi6xx and 6-7h of SOT on wifi (5-6h on 4g)
Again, a bit of patience, it will be all good. It is already for motivated flashers
Click to expand...
Click to collapse
with this statement, will not buy 6x and wait for A2
saves me trouble of flashing PE on 6x
:fingers-crossed:
dodjob said:
Ähm.. mia2 + Hex Kernel is soooo faster than mi6xx and 6-7h of SOT on wifi (5-6h on 4g)
Again, a bit of patience, it will be all good. It is already for motivated flashers
Click to expand...
Click to collapse
Is the Hex kernel being done in collaboration with the X-team?
Their extreme kernel for the Mi A1 is crazy good.
Can you point me to the kernel file? I would like to test and report
enapah said:
It was an issue in the past, but now that there's wide support for the Google Pixel (which even has official LOS) things just got a lot easier. A/B is a non-issue for the end-user, the developer does need to check how things are done in the Pixel (which takes valuable time), but shouldn't be a deal breaker as everything is already public.
IMHO the real issue is the fact the Mi A2 wasn't really that popular to begin with (among the kind of enthusiasts that would only ever run a custom ROM, that is). When it launched, those enthusiasts preferred the whyred (which already had great support, namely official LOS). Shortly after, Poco happened.
I honestly think this device will be like most others, custom ROMs will either come straight from GSI (when vendor is fixed) or only after the Android One support ends (aka. when we'll be pressed to do something).
It's not too bad at all, it's just slightly disappointing because (1) Xiaomi timed their product releases poorly, not giving enough information to make an informed purchase; and (2) we kinda of expected a little more from Android One than to be grounded to stock or (now) a GSI.
At the end of the day it is up to us (everyone in this community) to do something about it (ie. start working on the device instead of expecting someone else to pick that job). Harsh words, but true nonetheless.
Click to expand...
Click to collapse
I agree with what you said. Its just unfortunate that this device got a lot of bugs despite its being an Android One phone. I'm sitting here just waiting for October update or Android Pie update so I can use my device without worries.

Temp root achieved on first Snapdragon 835

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.

918j... ? for possible upgrade to nougat or oreo...

i've done a lot of research but still want to ask for assurances...
i might get another v20... best to get 918, 996 and/or 990DS in that order if had a choice for spare parts or double the fun?
i know oreo has been crapped upon but is is that bad? tell or refresh me the major pros and cons if i want to experiment pleasel..
and last i've looked over a lot of threads and am curious about upgrading from j to a higher letter on nougat minimum if oreo is that bad. i would like stay stock/rooted, but try magisk since i have not done any tinkering for awhile. any recommendations for best letter to upgrade to since you can go back and forth either way now on many models. up until i found out the restrictions on certains models like 918 and sprint version, it seemed p was the best. can i go higher?
last, don't forget I want to stay stock but go custom as much tweaking as I can if the upgrade is worth it. the phone is a DAP now and the research i have done doesn't seem like any updates brought serious improvements, mostly security patches.
anyways, just hoping to get a few seasoned answers. can't believe I am having this much phone with a phone 4 years later. much of that has to do with the swappable battery. :good: oh and the DAC.

Categories

Resources