Database Users

chevron unlock mess up official at&t updates?

I have a hd2/hd7 & decided to get a Samsung focus. I just read of pocketnow.com that Microsoft is saying all the people that did nodo un official will be stuck not able to update passed nodo. My question is can I unlock my focus & wait for the official at&t update without worrying about messing my phone up for updates?

it worked fine for me.

@Freddy2Fred what do you mean? My concern is if I unlock my focus when I get it & also install the re-unlock so when I update to nodo will it effect my future updates?
This is what the article says on pocketnow......
"Monday the ChevronWP7.Updater brought the ability to update Windows Phones to the latest build for all those who lost their patience in waiting for the update notification.
A lot has happened since then: the blog post of Chris Walsh no longer has a valid link to the ChevronWP7.Updater -- as in it was pulled! You might have a déjà-vu as the ChevronWP7 unlocker used to jailbreak smartphones was also pulled as the team was in talks with Redmond.
Apparently, Microsoft warns users related to the usage of the ChevronWP7.Updater as it allegedly will put an end to the smartphone's ability in receiving future updates. According to Redmond, re-flashing the device with an original stock ROM would be the only solution to revert from the situation created.
Since Windows Phone 7 stock ROMs aren't available officially the way we got used to them being on manufacturer's websites back in the days of Windows Mobile, you can either stick with NoDO forever or send it back to the factory? What do you think about such an alleged stance?"

Relax... The report doesn't say for sure. It states Microsoft hasn't tested the Chevron Updater and warns its a possibility. HTC phones that used the Chevron Updater reported receiving additional updates almost immediately through Zune for HTC firmware. Regardless, I'm sure the coders like Chevron team and XDA members will provide updates for our current hardware long after Microsoft and the Carriers stopped in order for us to buy new hardware...

djc said:
I have a hd2/hd7 & decided to get a Samsung focus. I just read of pocketnow.com that Microsoft is saying all the people that did nodo un official will be stuck not able to update passed nodo. My question is can I unlock my focus & wait for the official at&t update without worrying about messing my phone up for updates?
Click to expand...
Click to collapse
There's an AT&T update? I haven't seen one thing from them and at this point I'd be surprised if I ever do so I wouldn't be too worried.

Relax
If you read the article you will see that "might" is used three times in the second paragraph of the quote and "possible" used in the third paragraph. As it was being published, many users who had updated through the updater were receiving Zune update notices and re-updating with no problems.

Thanks for the answers everyone. The only thing I want to do is unlock it, apply the un-relock so I can sideload when needed & have my custom ringtone/sms. I will still wait for the official update still because of this article so I don't have to update then re-update in a months time.
"Now that the ChevronWP7 Updater tool is out, letting you force NoDo onto the Windows Phone 7 handset of your choice, there's nothing else we're still waiting around for, right? Well, not quite. While this shortcut may get you copy-and-paste, there are still non-NoDo related updates coming down the pipeline. Chris Walsh, ChevronWP7 team member and creator of that update tool, has tweeted word that there's a Samsung Focus-specific update in the works, including some bug fixes.
Walsh implies that they'll be several bugs targeted, but the only one he singles out deals with Bluetooth support. We've seen reports of users running into garbled sound and volume swings with devices connected to the Focus, so this may be the fix Walsh mentions."
With this update supposed to land "really really soon", it's likely that AT&T could push it out at the same time it gets around to releasing NoDo for its users who have decided to wait for an official channel, almost certainly later this month. If you have a Focus and have been considering the universal update hack, you may want to hold off, as you're just going to have to revert it in order to install this bugfix update.

You know what this shows? It shows that if AT&T weren't sitting on their hands keeping silent then people wouldn't get so antsy to get the update. If they came out and said "we're testing it and you'll receive it within <blah-blah> amount of time," which wasn't the case, then people wouldn't have had to resort to finding ways of getting the update. As it stands, there may never be a day this year or any year that we'll see an update from AT&T.
There may be bug fixes being made by MS, but will AT&T release it? Not over their dead, greedy hands. They'd rather you buy a new phone than run the risk of having their support people actually do their jobs.

I really hope this stuff gets organized soon to where we get straight updates from Microsoft for each phone itself. Do yall think the focus will be the only one that will have expandable memory? That seems to been a worse idea lol I'm going to keep my focus with the memory it comes with. I really want to stick with wp7 but I hope its not a slap in the face lol

Revert????
djc said:
Thanks for the answers everyone. The only thing I want to do is unlock it, apply the un-relock so I can sideload when needed & have my custom ringtone/sms. I will still wait for the official update still because of this article so I don't have to update then re-update in a months time.
"Now that the ChevronWP7 Updater tool is out, letting you force NoDo onto the Windows Phone 7 handset of your choice, there's nothing else we're still waiting around for, right? Well, not quite. While this shortcut may get you copy-and-paste, there are still non-NoDo related updates coming down the pipeline. Chris Walsh, ChevronWP7 team member and creator of that update tool, has tweeted word that there's a Samsung Focus-specific update in the works, including some bug fixes.
Walsh implies that they'll be several bugs targeted, but the only one he singles out deals with Bluetooth support. We've seen reports of users running into garbled sound and volume swings with devices connected to the Focus, so this may be the fix Walsh mentions."
With this update supposed to land "really really soon", it's likely that AT&T could push it out at the same time it gets around to releasing NoDo for its users who have decided to wait for an official channel, almost certainly later this month. If you have a Focus and have been considering the universal update hack, you may want to hold off, as you're just going to have to revert it in order to install this bugfix update.
Click to expand...
Click to collapse
There is no evidence anywhere that you will have to revert anything. Reading other threads and blogs, users in other countries are getting their full updates, including firmware fixes, after using the Chevron Updater to install the update. The new update installs just fine over the hacked update. Others are reporting getting just a firmware update. We really need to see how this plays out but no one knows what will happen and people who are receiving updates after using the hack are reporting positive results. It's amazing that they get the official update and can install it even though their phone is reporting 7390.

Poll: Your Android Update Preferences LG G3

By owning a flagship android device, we always want the latest and greatest software available for this device, but there are only limited number of software engineers that work on android updates for LG flagship devices (around 300-400 engineers) depending on region, so they are not able to provide the users with all the minor android updates Google decides to release. Therefore, they turn their attention on major updates, instead of minor ones to keep their user base happy. Keep in mind that LG honors your device eligibility for upgrade to 24-27 months before dropping support and that we can't always get what we want.
My question to you is... If LG was reconstructing their plans for android updates, which one do you prefer?
1) You want all the minor android updates that Google releases to be released for your LG G3 and receive major ones later.
2) You want faster release of major android updates to the most current version.
To clarify: Choice 1 gives you more frequent small updates and Choice 2 gives you less frequent, but large updates. When your device approaches the support-end date, choice 1 will be one major update behind choice 2 because engineers working on every android updates and won't be able to release the major one in time.

This is a really hard one to call. Recently I received the 20f update from 20e on my D855. It was only a 12mb google patch but didn't change the android version the phone was on, in fact I don't know what it changed! Obviously it fixed or improved something but it would be nice to know what!
I think it is a matter of priority, if we receive a major update, for example going from 5.0 to 5.1.0, which not only has performance improvements but cosmetic and feature additions then I would like to receive this type of update as soon as possible helping my device stay at the cutting edge.
But if this update breaks something... like my wifi becoming unstable or system programmes force closing all the time, I would expect that to become the priority no matter how small the patch update may be!
So to reiterate, my first choice would be option 2 bringing in a touch of option 1 if required!

beastobadness said:
This is a really hard one to call. Recently I received the 20f update from 20e on my D855. It was only a 12mb google patch but didn't change the android version the phone was on, in fact I don't know what it changed! Obviously it fixed or improved something but it would be nice to know what!
I think it is a matter of priority, if we receive a major update, for example going from 5.0 to 5.1.0, which not only has performance improvements but cosmetic and feature additions then I would like to receive this type of update as soon as possible helping my device stay at the cutting edge.
But if this update breaks something... like my wifi becoming unstable or system programmes force closing all the time, I would expect that to become the priority no matter how small the patch update may be!
So to reiterate, my first choice would be option 2 bringing in a touch of option 1 if required!
Click to expand...
Click to collapse
I have to agree with you. I wish there was a happy medium between the two.

Custom Rom

Hello,
is there any custom ROM for the for the Dtek50 available?

The silence in here tells a lot :/

Is there still no custom ROM? I (and many other) would really need it. I am willing to test it. The problem is that there will be no Nougat-update by Blackberry.

stefan5 said:
Is there still no custom ROM? I (and many other) would really need it. I am willing to test it. The problem is that there will be no Nougat-update by Blackberry.
Click to expand...
Click to collapse
I think the biggest problem is that Blackberry/TCL has done a really good job of locking up the bootloader - I don't think any exploits have been identified yet which would allow a custom ROM to be installed, and there definitely isn't any official manufacturer-sanctioned bootloader unlocking tool.
Unless that changes, we'll be stuck with Blackberry/TCL's decisions regarding OS updates and security patches. We're already are pretty sure there won't be any major version upgrades, and it's inevitable that eventually the security patches will come to an end too.

I hear this is a rebranded idol 4 by TCL. If that's true maybe see if your phone is supported by the TCL flashing program SUGAR QCT_SP_Gotu2

PizzaG said:
I hear this is a rebranded idol 4 by TCL. If that's true maybe see if your phone is supported by the TCL flashing program SUGAR QCT_SP_Gotu2
Click to expand...
Click to collapse
It's certainly possible, but I'd be afraid to try it out. Blackberry has really focused on a security model which puts a high priority on ensuring that no unsigned OS code can ever be allowed to run.
I would hate to accidentally discover some sort tamper protection feature which might leave me with a bricked device.

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.

A thought experiment on T-Mobile OxygenOS and bootloader in general

Just like it says on a tin can, I have a few questions I am wondering about to ask myself, and yeah, be warned, there is a few angry rants about Verizon's fraudulent practice of locking down the phones. Anyways, here we go...
I have been taking a stab at asking T-Mobile a few questions (via their Tweeter account, of course), regarding their stance on bootloader, and whether they will go the way of Verizon and perma-lock their phones in the future (Sprint have been rather infamous for that too, and don't get me started on Verizon, they still boil my blood), and I was told they have no reason to do so for the risk of losing a lot of customers which is sensible. In the other word, I can expect to see to it that T-Mobile phones will remain unlockable for good. (I will tell you why Verizon boil my blood; they permanently lock everything they touch under the Sun, except for the Nexus 6 of course, and get it, they will refuse to unlock it "for customer service experience" which is a rather lame excuse which anyone would blow through like a piece of paper tissue easily, and for this reason, I have intense hatred for Verizon for a very good reason because perma-locking the bootloader in the phones we buy with our cold, hard cash is a bona fide fraud. As you can see what's obvious; I left Verizon for T-Mobile for this reason.)
Anyhow, I wonder why is OnePlus starting to do something weird with the bootloader and Linux kernel in the recent OxygenOS update so that International version will not boot on converted T-Mobile OnePlus 6T phones (the infamous hardware mismatch warning which is also starting to happen with couple of custom OSes, nevertheless it CAN be bypassed so the OnePlus 6T phone will just continue to boot up normally), which is frankly a strange way to screw the sleeping dog because both T-Mobile (A6013) and International (A6010) versions are virtually the same hardware, absolutely no difference at all, except for the modem configuration, it's very expensive to respin the motherboard just to screw the customers.
(Except for both Samsung and Motorola, they don't care about the customers, all they want is money which the hateful Verizon have a lot of to make it so the identical phones are made with sneaky surprises inside so that a custom OS won't work on, nevertheless it usually won't work because LineageOS community prevails anyways. Still, I am disappointed about all that mess. I wonder why Verizon haven't been punished for perma-locking the LTE phones as their Block C LTE agreement clearly says that locking down the bootloader is forbidden. Full stop. Still, OnePlus is doing the right thing here, by allowing the customers to have choice. And shame on you, Google, why do you perma-lock the Verizon Google Pixel phones? C'mon, you know better than that.)

Still, T-Mobile telling me that they will refuse to lock the phones down is a good news in a way because the computer security is moving at alarming clip now (which means we will must unlock the bootloader to continue to be protected against future dangerous exploitations by continuing to be up to date especially with LineageOS which exists for this reason, and that's where a few carriers, especially Verizon, fall short in term of the computer security, and most newer Superuser managers, like Magisk, are password protected nowadays, which is absolutely mandatory). I am glad they made the commitment on it, thus I will be T-Mobile customer for a good while.
Sent from my OnePlus 6T using Tapatalk

Dr. Mario said:
Anyhow, I wonder why is OnePlus starting to do something weird with the bootloader and Linux kernel in the recent OxygenOS update so that International version will not boot on converted T-Mobile OnePlus 6T phones (the infamous hardware mismatch warning which is also starting to happen with couple of custom OSes, nevertheless it CAN be bypassed so the OnePlus 6T phone will just continue to boot up normally), which is frankly a strange way to screw the sleeping dog because both T-Mobile (A6013) and International (A6010) versions are virtually the same hardware, absolutely no difference at all, except for the modem configuration, it's very expensive to respin the motherboard just to screw the customers.
Click to expand...
Click to collapse
I'm on a converted T-Mobile 6T on OB15 and didn't have a problem booting when updating to this most recent. Is this just something they are starting the ball rolling on to where the International version will not boot on converted T-Mobile OnePlus 6T phones or have some run into this problem already with the hardware mismatch warning? And if this happens on the next update how can it be bypassed to be able to boot into the OS? Sorry if I'm behind the times on this but it is the first time I'm hearing about this.

Interesting, I will give recent ROM update a shot at aome point soon. Hope I don't get the warnings as a few people are starting to get the warning on their converted T-Mobile OnePlus 6T phones, so right now I am holding off on the update so I can be sure I don't run into this problem.
I flashed the OxygenOS 9.0.15 on both slots so I can update to recent LineageOS 16 and put some bootloader vulnerabilities to bed. It's the recent Android Quindim beta version that started to display the hardware mismatch warning, so I got nervous about the OxygenOS 9.0.15 bootloader which could have this type of check, as well as how recent custom OSes handle this situation.
Sent from my OnePlus 6T using Tapatalk

I'm in a TMO converted that's not paid off and I'm bootloader and Sim unlocked as well as running latest with no issues at all. Never ran into this hardware mismatch issue at all. I haven't really messed with custom ROMs on this though.

Dr. Mario said:
Interesting, I will give recent ROM update a shot at aome point soon. Hope I don't get the warnings as a few people are starting to get the warning on their converted T-Mobile OnePlus 6T phones, so right now I am holding off on the update so I can be sure I don't run into this problem.
I flashed the OxygenOS 9.0.15 on both slots so I can update to recent LineageOS 16 and put some bootloader vulnerabilities to bed. It's the recent Android Quindim beta version that started to display the hardware mismatch warning, so I got nervous about the OxygenOS 9.0.15 bootloader which could have this type of check, as well as how recent custom OSes handle this situation.
Sent from my OnePlus 6T using Tapatalk
Click to expand...
Click to collapse
Another thing also...I found that just doing the lighter OTA updates that I would sometimes run into some kind of bug here and there. Like after I did the OB14 OTA my FP sensor was buggy as hell...So I started downloading the full updates from the OP site and doing the local update. This has been working better for me...Phone has been working great since I started doing that. But yeah I did hear that about the Q beta on the T-Mobile phones now that you mention it...So I have steered clear of that.
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
jestyr8 said:
I'm in a TMO converted that's not paid off and I'm bootloader and Sim unlocked as well as running latest with no issues at all. Never ran into this hardware mismatch issue at all. I haven't really messed with custom ROMs on this though.
Click to expand...
Click to collapse
I'm sim unlocked but haven't unlocked the bootloader yet as I'm happy with the OS and don't want to see the bootloader unlocked nag screen when I boot up. But I have been tempted to do it just to be able to play around with the phone more.

So along with this.. is this hardware mismatch issue something I managed to avoid by doing the unlocked bootloader and Sim unlock months ago? Whenever I've tinkered and messed something up I've just used the first release patched msmtool to fix it followed by flashing whatever the latest update is and I've never had any issues. I also keep the first release bootloader unlocked and rooting tool from here and again have had no issues unlocking and rerouting. Can someone clarify what circumstances this hardware mismatch is occurring in so that I can avoid it if possible..

Jeffro64 said:
Another thing also...I found that just doing the lighter OTA updates that I would sometimes run into some kind of bug here and there. Like after I did the OB14 OTA my FP sensor was buggy as hell..
Click to expand...
Click to collapse
That's why I usually do the full fastboot / TWRP flash, as I have been dealing with somewhat oblivious bugs and obvious ones on OTA updates before, and in rare case, it can actually brick a phone. AES 256 / SHA 256 encryption checksums are usually useless in special cases like OTA updates because you will never know what you get. Like that fingerprint scanner bugs.
Also, Jestyr8, you are good, that warning only have occurred recently, but sometimes bootloader can be pretty weird that it allows the specific OS to boot without warning. I am wondering if wiping the modem configuration to remove that SIM lock affects the Linux kernel in a way that it thinks that it's installed on the bona fide international version (A6010) so everything is hunky dory, allowing it to boot up normally. If that was the case, it usually is impossible to patch the SIM configuration, because if they did, they will have hard time assigning the IMEI to it in the factory due to how the Snapdragon modem firmware works (Qualcomm prefer to keep things simple for obvious logistical reasons).
Sent from my OnePlus 6T using Tapatalk