[Q] Anyone have an 8x that received GDR2? - Windows Phone 8x by HTC

I was wondering if anyone who has the GDR2 Update (preferably unbranded, bc I think you will have to run the HTC RUU to get back to pre-GDR2) could preform a little experiment to help some of us that still haven't received it yet. (Thanks, T-Mobile!)
If anyone is helping out, it would be much appreciated!
The Idea:
1. Have someone downgrade their device to pre-GDR2 (I think a hard reset will work?).
2. Set up fiddler to decrypt HTTPS traffic and install the root cert on their htc 8x.
3. point their phone at the fiddler proxy and run windows updates. When it is done installing GDR2, stop capturing traffic and send me the session logs.
4. ????????
5. PROFIT.
I will gladly provide more details if anyone is interested in helping out.

the update is gigantic and i stupidly bought the 8gb phone lol. meant to get 16. att here, installing now

chatch15117 said:
the update is gigantic and i stupidly bought the 8gb phone lol. meant to get 16. att here, installing now
Click to expand...
Click to collapse
it should shrink back a bit after the updates are installed.

Related

Rogers Mandatory Update

For us Magic users who have rooted our HTC Magics and flashed a new rom on it, would it be mandatory for us to update to their rom?
j.lai said:
For us Magic users who have rooted our HTC Magics and flashed a new rom on it, would it be mandatory for us to update to their rom?
Click to expand...
Click to collapse
I was wondering that too. They are saying their are disabling 3G Data on our phones till the upgrade is performed.
I'm afraid it has a perfected SPL.
no need for rooted users to upgrade... i believe the upgrade is just to fix the gps 911 issue. us rooted users dont experience that
Edit: Custom rom users
it's the sense ui upgrade as well.. and apparently one month of free data fees
Hmm according to the screenshot on the HTC website is shows Build number 3.05.631.7 which looks to be newest one I can find.
we need someone to verify what SPL is included with this update. I won't be updating my phone. I don't want to loose root
Yeah that's all fine and nice that we aren't affected with custom ROMs but did you guys not read the fine print?
Customers who have not downloaded this software update could have problems accessing 911. As a result, we are taking the precautionary measure of temporarily disabling internet access for Dream and Magic users on Sunday January 24 at 6:00AM (EST). Voice and text messaging will not be impacted. By disabling internet access, we can ensure that 911 calls are completed for all our Dream and Magic customers. Once a customer completes the software update, his/her internet access will be re-enabled within 24 hours.
Taknarosh said:
Yeah that's all fine and nice that we aren't affected with custom ROMs but did you guys not read the fine print?
Customers who have not downloaded this software update could have problems accessing 911. As a result, we are taking the precautionary measure of temporarily disabling internet access for Dream and Magic users on Sunday January 24 at 6:00AM (EST). Voice and text messaging will not be impacted. By disabling internet access, we can ensure that 911 calls are completed for all our Dream and Magic customers. Once a customer completes the software update, his/her internet access will be re-enabled within 24 hours.
Click to expand...
Click to collapse
hmm very strange so basically they are forcing everyone to update ...interesting...
I guess we'll have to see HOW they can know that we haven't updated.
Here's a link to the "about" for this version btw: http://www.htc.com/us/img/ca/HTC Magic (Rogers)/image001.png
does anyone know if rogers is able to check your build?
becuase in the instruction manual below step 4.
"Refer to the image and note the build number version listed. if you have the same build number version there is no need to update this software."
I looked inside the update file's rom.zip files and it appears to have a 1.76.0010
SPL
Well it's about time we got the Sense UI update... but I don't like the idea of being forced to update and getting perfected spl. I'll hold off on it until I get my internet disconnected.
The RUU has radio version 6.35.10.18, build 3.05.631.7... hmm
can anyone host the RUU I can sent it.
^Uploading now.
edit: beaten to it.
hboot_7200A_1.76.0010_100114.nb0
Radio_Signed_Sapphire_63.18.55.06K_6.35.10.18.img
more info soonish
i uploaded to my work's temp data storage web server
Code:
URL no longer available
I can't add url's apparently so just copy and paste.
Just got an SMS tell me to update... I don't want a perfect SPL.
DaMonk said:
I looked inside the update file's rom.zip files and it appears to have a 1.76.0010
SPL
Click to expand...
Click to collapse
I'm willing to bet that's a perfected SPL...
Hopefully i won't get one as I already have a 1.6 rom loaded.
Rogers must have a way to verify connected phones rom versions.
fatcow167 said:
does anyone know if rogers is able to check your build?
becuase in the instruction manual below step 4.
"Refer to the image and note the build number version listed. if you have the same build number version there is no need to update this software."
Click to expand...
Click to collapse
I just phoned in and asked about the update. The fella didn't seem TOO savvy about it at all - he didn't know what a custom rom was.
He did, however, say that rogers is able to check what version you have through your "IP when you connect", and he wasn't 100% sure about what would happen to custom roms.
Frankly I'd take it with a grain of salt.

bought phone from becetech wont update firmware

im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Benno81 said:
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Click to expand...
Click to collapse
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Benno81 said:
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Click to expand...
Click to collapse
Are you trying to update via the phone update feature? If so this won't work as rooting disabled the ability Update using ota
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Benno81 said:
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Click to expand...
Click to collapse
From what I can tell you have a g920v variant if the phone Shows Verizon but the sure fire way to know what variant you have is turn the phone off once off hold home-power-volume down, this will take you to download mode but should tell you your variant. You don't need to root a phone to refurbish It, you can flash Stock firmwares via Odin. I really don't know why they would have Rooted It tbh, you'd need to contact them, but I know for sure you can manually download the latest Verizon firmware and the phone should work. Maybe they Rooted it as part of making it network unlocked, o really can't say
Ok I tried that and a bright blue screen came up warning about custom OS then press up volume for download and down volume for reset? I just pressed down as there was no other info on the screen but it does say it's a sm-g920v in the settings as well as the root checker app. Another thing was I did ring samsung support gave them the serial number and IMEI and they said an authorized modification had been done on the phone but could offer no other support as it wasn't an Australian phone. I'll keep trying to get some info out of the company I bought it off and try to sort it out thanks for your help :good:

H90022b Software update,October 12, 2017

I just upgraded two ATT LG V10 to H90022b released on 10/12/2017.
I thought it's just security patch but somehow I feel both get snappier.
And power seems improved a little bit. But I am not sure... maybe it's because it reinstalled all apps during upgrading ?
anyone has any issue or any improvement after upgrading to H90022b ?
ajutama si pe mine te rog frumos cu ultimul firmware lg h900
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
am probleme de securitate dupa update android 6 pe lg h900
am nevoe de firmware ATT LG V10 la H90022b si nu stiu de unde sa downlandez
poate daca fac update la lg h900 cu H90022b mi se va rezolva problema
Have 2-week-old Lg v10 H900, new, unlocked. It would not upgrade with LG Bridge or OTA, saying "device may be rooted". So went online and found Marshmallow KDZ file and uploaded to phone. It shows the Marshmallow is up but now I get errors like "com.android.settings has stopped", "LG VPN has stopped", and "lock screen settings has stopped". I cannot configure/initiate fingerprint scanner, and device reboots when I uninstall an app.
I have cleared all caches and reset to factory (recommended by LG tech help...waiting for additional solutions from them), all to no avail.
Any ideas??
I have the same problem I am facing the same error in setting app if you fix these
If you fix these error please help me out
can someone with this update share it please as some of are not getting the update ota.
wow, it's been a year.. not solution yet? i wish i had this read these threads before updating to MM ...
Me too..
Wish someone with H90022b is generous enough to extract the partitions of the device so we can flash it using Qfill. As long as I have the device, I promise to do my best to provide the other files such as the loader and xml files.
I dont really understand the purpose of these partitions, so we need all except modemst1 modemst2 fsg (where imei is stored), cache, and of course no userdata. The total size will be around 4GB but will be around 2GB compressed.
No harm but will help a lot for many of us.
If anybody wants to help but not sure what to do, feel free to contact me.
Thank you!
ardian1899 said:
Me too..
Wish someone with H90022b is generous enough to extract the partitions of the device so we can flash it using Qfill. As long as I have the device, I promise to do my best to provide the other files such as the loader and xml files.
I dont really understand the purpose of these partitions, so we need all except modemst1 modemst2 fsg (where imei is stored), cache, and of course no userdata. The total size will be around 4GB but will be around 2GB compressed.
No harm but will help a lot for many of us.
If anybody wants to help but not sure what to do, feel free to contact me.
Thank you!
Click to expand...
Click to collapse
Problem with extracting partitions once on 22b would probably require root (at least for methods that I know of, such as Wanam's 'Partitions Backup & Restore'. Besides, most users who rooted it on lollipop never upgraded the software, users who would have 22b installed can't achieve root, and developers who could really help with this have already moved on. I just bought the AT&T version of this phone to use with the $10 Unreal Mobile unlimited monthly plan and realized that there is no root after MM update. I could live without root but I am also stuck with outdated 21z.
Android# said:
Problem with extracting partitions once on 22b would probably require root (at least for methods that I know of, such as Wanam's 'Partitions Backup & Restore'. Besides, most users who rooted it on lollipop never upgraded the software, users who would have 22b installed can't achieve root, and developers who could really help with this have already moved on. I just bought the AT&T version of this phone to use with the $10 Unreal Mobile unlimited monthly plan and realized that there is no root after MM update. I could live without root but I am also stuck with outdated 21z.
Click to expand...
Click to collapse
Fortunately there's another way.
We have to get the phone to Qualcomm 9008 mode.
There are 2 safe way to do it, I said safe because I did both a thousand times (hyperbolic, lol) without any problem or effect to the phone if it just "reading/extracting".
The 1st way is to connect 2 points on the board while connecting the usb cable to the computer. Of course the board need to be taken out from the phone.
I understand if the 1st way may not comfortable enough for some, then the 2nd way is using a deep flash cable, which is an easy mod to a spare usb cable.
If I have a 21z or 22b device, I can create these files in less than an hour and potentially help many 90021w user.
Both may not an easy thing to do. So will be great if anyone willing to lend a hand.
ardian1899 said:
Fortunately there's another way.
We have to get the phone to Qualcomm 9008 mode.
There are 2 safe way to do it, I said safe because I did both a thousand times (hyperbolic, lol) without any problem or effect to the phone if it just "reading/extracting".
The 1st way is to connect 2 points on the board while connecting the usb cable to the computer. Of course the board need to be taken out from the phone.
I understand if the 1st way may not comfortable enough for some, then the 2nd way is using a deep flash cable, which is an easy mod to a spare usb cable.
If I have a 21z or 22b device, I can create these files in less than an hour and potentially help many 90021w user.
Both may not an easy thing to do. So will be great if anyone willing to lend a hand.
Click to expand...
Click to collapse
per your request I have taken screenshot of the service menu and uploading as attachment with this post.
Android# said:
per your request I have taken screenshot of the service menu and uploading as attachment with this post.
Click to expand...
Click to collapse
Hello,
Thank you for your efforts. Sorry I was a bit busy these days.
Initially I'm trying to get my luck by googling up what I see on your screenshots, but no luck.
Now I'm still trying to get a script to copy the phone's partitions. Seems like will taking a while.
I'll let you know if it's ready, hopefully won't be long.
Thank you again!
ardian1899 said:
Hello,
Thank you for your efforts. Sorry I was a bit busy these days.
Initially I'm trying to get my luck by googling up what I see on your screenshots, but no luck.
Now I'm still trying to get a script to copy the phone's partitions. Seems like will taking a while.
I'll let you know if it's ready, hopefully won't be long.
Thank you again!
Click to expand...
Click to collapse
You welcome. I also tried to download a kdz for my firmware by using LG Bridge's 'update error recovery' option but it gives me error that "Your phone information cannot be checked. For more information, contact LG customer service". But if i use just 'Software Update' it tells me that I can update to latest version "V21W_00" through update center settings in my phone. I think that LG Bridge database only have up to V21W as the latest OS for LG H900 and it doesn't recognize that my phone has more updated version, so even if someone had Nougat they got OTA, they wouldn't be able to use LG Bridge or PC Suite to help us this way.
I am just tired of this phone and gonna sell it and buy a T-Mobile version. Good luck to you, hope you find a way to upgrade software on your phone.
Android# said:
You welcome. I also tried to download a kdz for my firmware by using LG Bridge's 'update error recovery' option but it gives me error that "Your phone information cannot be checked. For more information, contact LG customer service". But if i use just 'Software Update' it tells me that I can update to latest version "V21W_00" through update center settings in my phone. I think that LG Bridge database only have up to V21W as the latest OS for LG H900 and it doesn't recognize that my phone has more updated version, so even if someone had Nougat they got OTA, they wouldn't be able to use LG Bridge or PC Suite to help us this way.
I am just tired of this phone and gonna sell it and buy a T-Mobile version. Good luck to you, hope you find a way to upgrade software on your phone.
Click to expand...
Click to collapse
I read somewhere that after 21w, at&t keep the firmware on their server, maybe that's why the only way to update is through OTA.
When will you sell the phone approximately? I may finish the script before it..
Maybe it will change something if we get the H90022b .. i'm little skeptical though. Because our issues with H900 MM started because we Flashed a H900 ROM over a H901 or VS990 board. the way i see it, even if AT&T releases Nougat, we still gonna have issues, even worse.. we kinda screwed..
i've been thinking, maybe the H90021w was somehow corrupted or missing some files...
Also, i've been reading some threads, people talking about reflashing the correct ROM, either a H901 or VS990 ... but i'm not ready to dry that considering none has done that succesfully..
For me, the solution would be find a solution to go back to Lolipop... at least it no issues. outdated maybe, but everuthing was working fine on my phone.
https://cdn-cf-3.xda-developers.com/images/smilies/cool.gif
Going back to Lollipop is not possible because of antirollback. And I dont think if there's anybody ever found code board H900 on the pcb. Eventhough it seems not right but vs990 is the correct pcb board, it just the bad firmware (v21w). And there's no KDZ or TOT newer than v21w around as far as I know.
I think I found the solution, but I need a volunteer with v21z or v22b firmware on his phone
Android# said:
You welcome. I also tried to download a kdz for my firmware by using LG Bridge's 'update error recovery' option but it gives me error that "Your phone information cannot be checked. For more information, contact LG customer service". ....
Click to expand...
Click to collapse
Here is the test point. Is it visible?
can anyone please post H90022b kdz file or something newer?

WARNING to potential buyers of the Nokia 8

I just got done chatting with Nokia support (both chat and email) about getting the required unlock.key file that you need to unlock the bootloader for the Nokia 8, which they said they would unlock. First, a little background. The process Nokia wants you to go through to get the file is to download an apk of theirs which will analyze your phone a bit and then generate a code which you put into a form on their website to get the file emailed to you. Rather clunky but alright. I do so, but then I get an error when the apk runs. "Error messages: Device not support." Very well. I then talk to support. Chat had no idea how to fix it. Email fared just as well. I will copypaste the entire exchange. (Save for the original email I sent as I forgot to save it. Sorry about that.)
Nokia said:
Welcome to Nokia Mobile Care ,
​Thank you for your time writing us and thanks for using our Nokia 8 products. We understand why you came to us thats why we will try our best to assist you !
In order to assist you better and more accurately we would like you to provide us a little bit more information :
​
​- Could you please provide us the screenshot with the error message? Thank in advance!
​- How are you unlocking bootloader ? in which step are you at ?
​Additionally we will provide you the steps unlocking bootloader below :
​
1-Go to https://www.nokia.com/en_int/phones/bootloader, accept the terms and sign in
2-Scroll down until you see the phone validation form.
3-Download and install NokiaPhoneUnlockBootloader.apk, there is an included link on the page.
4-You will receive a validation code that must be entered into the form on the website along with the email used, note the validation code is only valid for 30 minutes.
5-You will receive an email containing a link to download a file, the name will contain your IMEI number and have an extension .key, it should be renamed to "unlock.key"
6-Start the phone in download mode.
7-Download and set up ADB
8-Start an ADB shell and run the following commands, unlock.key must be in the platform-tools directory from the ADB setup
fastboot flash unlock unlock.key
fastboot oem unlock
You should then see
Unlock success!
9-then run the command
fastboot reboot
​
Remember that you are important to us and we're looking forward to your response.
If you have questions or face any difficulties, please contact us at your convenience.
Wish you all the best.
Best regards,
Nokia Mobile Care
-----------------------------------------------------------------------------------------------------------------------------------
© 2019 HMD global All rights reserved.
Nokia is a registered trademark of Nokia Corporation.
HMD global is the exclusive licensee of the Nokia brand for phones and tablets.
-----------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
S5Guy said:
I have downloaded the official apk from Nokia to get the verification code to put on the website form. When I launch the app and put in my email though, it merely shows the error message shown in the attachment.
Click to expand...
Click to collapse
Nokia said:
Thank you for getting in touch with Nokia Mobile Care. It's important for us to have you as our customer.
I can see that you are trying to unlock your phone's bootloader, you have already downloaded the app and you are receiving the message saying that "device not supported".
​
HMD Global allows the bootloader on certain Nokia phones to be unlocked, allowing for customizations. This feature is intended for developers only.
​
Once the device is being unlocked, it is no longer covered by the manufacturer's limited warranty provided by HMD Global.
If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message "Device not Supported" this mean that your device is not supported to have the bootloader unlocked.
If you are facing some issue with your phone, you can send it to a repair center, out specialists has the information on how to handle it. Note that Nokia only provides the possibilities to unlock bootloader to developers.
We hope that the above information is useful.
Any other question you may have are always welcome. Please feel free to contact us again.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
S5Guy said:
"If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message 'Device not Supported' this mean that your device is not supported to have the bootloader unlocked."
^ This is not correct at all. At least for the Nokia 8. https://twitter.com/sarvikas/status/1045298106818949120
I have followed the prior instructions rigorously, but since the apk does not work, I must ask you for the needed "unlock.key" file. I am very well aware of the consequences of unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for getting back to us. ​I'm sorry to hear that the previous solutions didn't make any difference.
I can see that you are not happy about the previous answer you have had. I understand that can be frustrating sometimes.
As explained before the allowing will depend on many factors, as market, for example. If you have the app running well, if you have tried all the steps to have your bootloader unlocked and still receiving the message "device not supported" there is no other reason than that the app itself is saying the device you are trying to unlock is not supported.
Did you tried to uninstall and reinstall the app? did you tried to restart the process?
Note that here we are a customer care for technical issues customer may face with their device, we do not produce the rules or the policy we just follow then. There is no other advise to you at this moment.
If you have any other question not related to bootloader, please feel free to get back to us any time.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
-
So basically, to sum up, if you're thinking of unlocking the bootloader at all for any reason, steer WAY CLEAR of this phone. My phone may for whatever reason have fallen through the cracks perhaps, but a lot more people than me are reporting this issue. On top of that, I've checked my phone's IMEI to be sure it wasn't stolen or fake and it was perfectly fine and legit. Honestly, I hate that I have to post this message because the Nokia 8 actually has some features I like that aren't really on other phones, but because of this software travesty, I can't recommend it at all.
Nokia, if you're out there, this is a disgrace in both software and support. Please fix this.
Hi
I have the Nokia 8 TA-1012 but I have not tried to unlock the BL. I am currently on Pie so see no reason for doing so as I am happy with the OS.
As most people do not buy a phone to modify the OS I see no problem not recommending this phone for normal use.
Sent from my TA-1012 using Tapatalk
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
The only solution that doesn't rely on Nokia might be to tear apart their apk and use a rooted phone or an emulator to fake the properties it reads, so the app thinks it runs on a security patch that is supported.
But this approach requires people to send their IMEI to random people on the internet so there are additional risks.
ironman38102 said:
While I didn't unlock through official methods
Click to expand...
Click to collapse
I have heard someone else mention this as well. How did you unofficially unlock the bootloader?
THMSP said:
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
Click to expand...
Click to collapse
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
frankoid said:
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
THMSP said:
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
Click to expand...
Click to collapse
I'm your man. With nothing left to lose. o_o Will report back with the results ASAP.
I'm back and with bad news. The update process via the recovery menu seemed to run into an error where it complained about the timestamp on the update zip being too old, but for whatever reason, it proceeded anyway. OK, wiped the data (what data?) and did a factory reset, now it's booting up. I check the system information to be sure and it is 8.1.0. Installed the apk. Ran it. AND THEN...
Device not support.
I'm gonna try this with the zip mentioned in frankoid's post and do another update again, but honestly, it looks like Nokia just wants to be an asshole at this point.
!!!!!!!!!!!!!!! SUCCESS !!!!!!!!!!!!!!!!!!
This update zip is what you need: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
Thank you apple boy for this topic.
100% troll.
S5Guy said:
*snip*
Click to expand...
Click to collapse
Great to hear that you got it working! My zip likely not worked because it just throws you back half a year (where official unlock didn't even exist) - you would have to update until you find a security patch that works.
But if November patch worked for you thats great! Since the May OTA worked for you that also means that people could choose to use the unofficial (paid) unlock method so Nokia doesn't know about whether they are locked or unlocked (warranty reasons).
Those OTA zips are model-agnostic btw. Whether they say TA-1004 or TA-1012 doesn't matter, they are the same. Only google makes that distinction on their servers, the software doesn't.
foxbatul said:
Thank you apple boy for this topic.
100% troll.
Click to expand...
Click to collapse
What's less useful...
A detailed set of instructions aimed at helping other forum members
... Or your post?
On mine that option is greyed out...
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
theviking33 said:
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
Click to expand...
Click to collapse
Did you touch the option in the past at all? If you did, it will be greyed out. As long as it's switched on though, it's fine. (I heard it will "ungrey" itself after a week, but there you go.)
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
theviking33 said:
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
Click to expand...
Click to collapse
I'm assuming you have a brand new TA-1004? And yeah, you should have gotten back a code long ago.
Try some of these options. https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
It could be though that it's just been flat out disabled due to region or whatever. If the solutions in the above link don't work, try downgrading back anyway and then using the apk as explained in an earlier post of mine.
It seems to be a case of "flat out disabled". I did a factory reset already and this setting won't change. I actually bought 2 of those phones and on both is the same.
How do I see or find out what region they are for?
And for the booloader, seems I have to go the old fashion way now...
---------- Post added at 11:38 ---------- Previous post was at 11:25 ----------
I have the TA-1004 DS which is International. So wouldn't understand why ist greyed.
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
Mine has same problem and I've also been through similar online-forum attempts to help.
Model: TA-1012
Hardware version: 3.1
Patch level: 1 Jan 2019
Build No: 00WW_5_11A, 00WW_5_110_SP01
Downgrade your phobe and you can unlock, i have the same phone and this is what i did. I downloaded my phone firmware,i place the update file on my external sd card, i reset my phone to factory stock, i shut down my device an while shut down i press vol + and plug in my cable, i wait for the no comand screen and press power while holding vol up and get in recovery where i update from sd card and boom oreo

Official Pie Update for SM-N950U?

Can someone send me the official link for the official stable Pie update? Cuz my phone which is Unlocked AT&T Note 8 has a problem updating.
When I go into settings>>software update>> it always says "Current software is up to date". Same thing happens when I use Samsung Smart Switch on Windows it says the same thing.
I would try to flash the .zip file on the stock recovery.
I would provide the other details below if you need cuz I'm unsure what update file should I use. Thanks!!
There are threads available to help you with that, just need to do a little bit of searching.
kangi26 said:
There are threads available to help you with that, just need to do a little bit of searching.
Click to expand...
Click to collapse
Affirmative!
When the August security update comes out for the U.S., will my Cricketwireless SIM allow me to get the AT&T update? Or, do I have to put an AT&T SIM in the phone. Could I just take the SIM out & connect to wifi instead?
Thanks.

Categories

Resources