Hi everyone,
My Razer Phone 2 has just gotten an update for November 2020 Security Patch. The build number is P-SMR6-SGT-RC001-RZR-201030.3682.
I am planning to root my device using the latest boot.img file on Razer Developer website, but I realized that the build number is slightly different, it being P-SMR6-RC001-RZR-201022.
I was wondering if flashing the boot.img file on the Razer website (with magisk) works for my particular build number - they're both MR6, but mine seems to be slightly different. I have never rooted/ flashed anything nor unlocked the bootloader before.
Cheers!
Well if the bootloader isn't unlocked then your phone will force a wipe before it can unlock. At that point you can just run the flash-all from the mr6 factory image and the build number will then match.
Related
Hello,
I still haven't got the 7.1.1 OTA update. Every month I keep getting the security updates for the 7.0 version. I checked my build version and compared it with the one mentioned on google's site and my version is NBD92D ( Mar 2017 ) which according to google is the build for ATT only. I am not using ATT , Infact I don't even have ATT in my country!
Does anybody else have this problem? Do I have to sideload the Image?
Yes, just sideload the image.
taranvohra said:
Hello,
I still haven't got the 7.1.1 OTA update. Every month I keep getting the security updates for the 7.0 version. I checked my build version and compared it with the one mentioned on google's site and my version is NBD92D ( Mar 2017 ) which according to google is the build for ATT only. I am not using ATT , Infact I don't even have ATT in my country!
Does anybody else have this problem? Do I have to sideload the Image?
Click to expand...
Click to collapse
I do have the same problem, last night I received update and applied it, after that I've checked the version is also NBD92D(AT & T). My Nexus 6 is bought in HK but not HK official goods and sourced from Australia. However, I am not able to verify my Nexus 6 is not AT & T version and the only way is to trust the Google update program version check, luckily until now no problems notice on the phone.
In the meantime, I do also consider to update to 7.1.1 (N6F26U) but my phone does not popup any update on the system update check, and right now the N6F26U update is removed. Now I plan to wait and see any further action/update from Google on Nexus 6.
@mega23mac: The AT&T Nexus 6 has the Death Star logo on the back and has its service locked to that carrier. If you had one where you are, it wouldn't work at all if locked and if unlocked likely wouldn't get LTE. To verify the model, enter the bootloader. In your case you want to see model number XT1100 in the display.
With that out of the way, if you want the latest 7.1.1 on your device, go to Google's developer pages, download the latest OTA image, and flash it. Waiting for an OTA is pointless with a Nexus device.
Strephon Alkhalikoi said:
@mega23mac: The AT&T Nexus 6 has the Death Star logo on the back and has its service locked to that carrier. If you had one where you are, it wouldn't work at all if locked and if unlocked likely wouldn't get LTE. To verify the model, enter the bootloader. In your case you want to see model number XT1100 in the display.
With that out of the way, if you want the latest 7.1.1 on your device, go to Google's developer pages, download the latest OTA image, and flash it. Waiting for an OTA is pointless with a Nexus device.
Click to expand...
Click to collapse
That's the suspicious part, my Nexus 6 doesn't have the "Death Start" logo on the back, and I can get LTE, and I do see the model no. of XT1100 in the bootloader. But from the Settings > About phone > Build number, what i saw is NBD92D (the update is from OTA).
However, I am consider to flash the N6F26U as the Android Pay failure is not important to me as I use it not much.
Thanks, Strephon.
mega23mac said:
That's the suspicious part, my Nexus 6 doesn't have the "Death Start" logo on the back, and I can get LTE, and I do see the model no. of XT1100 in the bootloader. But from the Settings > About phone > Build number, what i saw is NBD92D (the update is from OTA).
However, I am consider to flash the N6F26U as the Android Pay failure is not important to me as I use it not much.
Thanks, Strephon.
Click to expand...
Click to collapse
How will you flash that update? Google pulled the image immediately after they got to know about the android pay failure
taranvohra said:
How will you flash that update? Google pulled the image immediately after they got to know about the android pay failure
Click to expand...
Click to collapse
Google seems just remove the link but not the file, u can find the link from this forum easily. In addition, now Google release the link again.
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
VarunAgw said:
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
Click to expand...
Click to collapse
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Mr. Nerd_ said:
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Click to expand...
Click to collapse
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
VarunAgw said:
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
Click to expand...
Click to collapse
You probably need to use "mfastboot" instead of "fastboot" command. Download this: https://androidfilehost.com/?fid=962187416754477464
Unpack it and place the boot.img in same directory. Open Command Prompt in that directory. Correct command is: mfastboot flash boot bootimagename.img
Here you can also find the correct patched boot.img: https://forum.xda-developers.com/moto-g6/how-to/guide-magisk-patched-boot-image-opw27-t3794977
Got the S too
Hi,
I bought my new Motorola G6+ Evert last week here in Mexico. (where I live)
It's fully unblocked
Version PVT1, SKU XT1926-6
Running Oreo 8.0
But I wondered me about that Build Number.
While every tutorial is saying that I can just flash TWRP with that Build-Number : OPW27.113-45-4
Because I have: " OPWS27.113-25-4 "
I've upgradet OTA and it still says, that I have the latest security patch (1. June 2018) and so on....
So I wonder if I can unlock the bootloader, flash OPW27.113-45-4 or OPWS27.113-45-4 to be able to install TWRP Recovery from
https://forum.xda-developers.com/showpost.php?p=76501832&postcount=3
Purpose:
I can't wait to get my new babe rooted to install the real hot Stuff on it.
But it's still confusing why I got that different Build Number.... Maybe it's because of my location.
But i'am not shure if it is safe to root it and to flash SuperSU and TWRP. With my B-Number.
So may some one got the right Firmware for me ?
Sunny Greetings
B2DR
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Junior Passos said:
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Click to expand...
Click to collapse
And what about the "-25" vs "-45"? I have the same firmware here (Argentina): OPW27.113-25
Thanks!
Also what about this version OPW27.113-89 with security patch level 1 July 2018 for Australia.
I have the XT1900-1 android one version. Before unlocking my bootloader, I had the December 2018 security update. I unlocked my bootloader to get lineageOS, but decided to go back to stock using muchy_cool's guide. But now the security patches are going up to November 2018, and then it says its up to date.
Is there a difference between the stock firmware from the guide and the stock firmware upon buying the phone? I would assume so because if I relock the bootloader again, the warning message on boot changes to "device has loaded a different operating system". But then this is still stock firmware. Why don't the updates get detected?
Paximonium said:
I have the XT1900-1 android one version. Before unlocking my bootloader, I had the December 2018 security update. I unlocked my bootloader to get lineageOS, but decided to go back to stock using muchy_cool's guide. But now the security patches are going up to November 2018, and then it says its up to date.
Is there a difference between the stock firmware from the guide and the stock firmware upon buying the phone? I would assume so because if I relock the bootloader again, the warning message on boot changes to "device has loaded a different operating system". But then this is still stock firmware. Why don't the updates get detected?
Click to expand...
Click to collapse
Well it sounds like the OTAs ARE working if you're still on the November update. (My non-Pie phone is still on October update and Android 8.0)
It sounds like you just haven't gotten the December update yet. So did you first get September, October, and November?
As I am aware, even if you got the update it will fail at the moment of installation. There is no official stock recovery available so far that's why even if you lock the bootloader you are using the modified system warning shows at the time of booting.
Hello guys.
So I recently got a phone that's stuck with the August 2021 security patch. I wanna flash the latest software so had 2 questions:
1. Should I flash the most recent software update or considering I've never actually updated my phone, should I flash all the previous updates from August first before I flash the latest one.
2. I wanted to know if anyone has experience flashing SM-G998U1 firmware on a SM-G998U phone. I heard you can flash "U1" or carrier unlocked firmware on a "U" or carrier locked phone. Just that you'd lose all your data. I have an SM-G998U locked to Verizon and since I'm not in the US Verizon says they can't unlock it for me. So my only option is to flash new firmware updates. But I can't for the life of me find any Verizon SM-G998U firmware from after August 2021 (that's my latest security patch) online. So wanted to hear from anyone with experience that's flashed "U1" firmware on a "U" phone.
Flashing FW is no solution to unlock phones.
OnnoJ said:
Flashing FW is no solution to unlock phones.
Click to expand...
Click to collapse
I'm not trying to unlock my phone. It's usable cause it doesn't reject simcards. Just denies me OTA updates. All I want is new software.
Is there another option apart from flashing new firmware if I want to update it? I'd love to unlock the phone but all the websites keep talking about generating codes. My phone doesn't request a code. And I can still use it. If there isn't another option for unlocking, can you assist with the questions I've asked?
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
OnnoJ said:
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
Click to expand...
Click to collapse
Thanks so much for all the help Yeah I've seen that thread before. But only firmware available until November 2021. Nothing after. So think I'll try the U1 to U option for now.
Hello,
I am trying to root my S21 Ultra and have tried following multiple tutorials with no success. Looking for assistance to see if anyone knows what I am doing wrong.
Model: SM-G998U1
CSC: XAA
I have downloaded the latest firmware via Frija flashed it onto my device via Odin. I then put the AP file onto my device downloaded Magisk and patched the file to create the Tar file. I then tried to flash the device again with the same files except I swapped the AP file with the Tar file Magisk generated. It gets almost all the way to the end but then fails on "vbmeta_system.img" and my Device shows "secure check fail: vbmeta(1)". Does anyone know what this error means. I tried googling it with no success. Sorry I am a total noob when it comes to this stuff. Any assitance is greatly appriciatede.
Thank you.
@Puffnstuf
You have the Galaxy S21 Ultra's US carrier unlocked variant (U1).
Unfortunately, Samsung doesn't allow unlocking the bootloader of US and Canadian Galaxy devices. There exists an unofficial bootloader unlock method, but you can only use it if your Galaxy S21 is on the v1 bootloader.
Without an unlocked bootloader, you can't flash third-party binaries (such as the Magisk-patched boot image).
@SkandaH
How do I tell if my device is on the v1 bootloader? I am guessing its not if I have updated the device. If its not is there anyway to downgrade to the v1 bootloader?
If I am unable to unlock the bootloader should I avoid updating my device incase a new way to unlock the bootloader is released in the furture?
@Puffnstuf
The fifth character from the right end of the build number is the bootloader version. For example, the latest available firmware for the SM-G998U1 model is G998U1UES5CVF5. Its bootloader version is v5.
There is no known way to downgrade the bootloader version.
You may start deferring updates, but it's really difficult to predict the future. If you want to tinker with your device, it's always better to get one that comes with an unlockable bootloader.