Related
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.
Hello,
this is the very first time here at XDA Developers Forum that I do not find clear information about rooting a smartphone. I am talking about this Nokia 3 updated with OREO 8.0. Only a lot of confusion reading your posts, sirs. Nobody that is telling if rooting this model is possibile or not. So... can anyone says if it is possibile and how to do that, in a clear and simple manner?
Thanks and regards!
jimgordon said:
Hello,
this is the very first time here at XDA Developers Forum that I do not find clear information about rooting a smartphone. I am talking about this Nokia 3 updated with OREO 8.0. Only a lot of confusion reading your posts, sirs. Nobody that is telling if rooting this model is possibile or not. So... can anyone says if it is possibile and how to do that, in a clear and simple manner?
Thanks and regards!
Click to expand...
Click to collapse
here you go
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
this thread should be on Q&A.
Hello,
thanks for your reply. I already read this thread.
So since I am on OREO, it seems I have firstly to downgrade to Nougat. Can someone please tell me how to do that, posting links to the official 7.0 rom, the software and a short guide? Somewhere I read you have to use OST, somewhere else SP Flash Tool...
Thanks in advance and regards
Cosimo
Hello again...
I am trying to downgrade my Nokia 3 8.0 to Nougat, in order to unlock the bootloader.
I have searched a lot for an official 7.0 rom... nothing official... I tryed to follow this guide:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Managed to install and get a working copy of OST. Connected and start flashing the rom NE1-147I-ind-0-00WW-B02.nb0 (the one I thought it was the earlier one, since nobody wrote "7, 8, or another number" in the file name). OST got stuck at "Reflash service bootloader..."
Can anyone please write a clear guide on how to proceed to root a Nokia 3 OREO that was never ever unlocked before (i mean with bootload never unlocked)? I am going crazy, really...
jimgordon said:
Hello again...
I am trying to downgrade my Nokia 3 8.0 to Nougat, in order to unlock the bootloader.
I have searched a lot for an official 7.0 rom... nothing official... I tryed to follow this guide:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Managed to install and get a working copy of OST. Connected and start flashing the rom NE1-147I-ind-0-00WW-B02.nb0 (the one I thought it was the earlier one, since nobody wrote "7, 8, or another number" in the file name). OST got stuck at "Reflash service bootloader..."
Can anyone please write a clear guide on how to proceed to root a Nokia 3 OREO that was never ever unlocked before (i mean with bootload never unlocked)? I am going crazy, really...
Click to expand...
Click to collapse
flash UAE version of nb0 if IND doesn't flash, that's Android 7.0 May 2017 Security Patch, unlock and lock bootloader there and apply OTA updates from notification up to latest update. Then follow guide.
SkaboXD said:
flash UAE version of nb0 if IND doesn't flash, that's Android 7.0 May 2017 Security Patch, unlock and lock bootloader there and apply OTA updates from notification up to latest update. Then follow guide.
Click to expand...
Click to collapse
Hi, thanks again for your precious support. Can you give me a link to download the UAE version of the firmware? At this address: https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg I can only find the IND one.
Regards
jimgordon said:
Hi, thanks again for your precious support. Can you give me a link to download the UAE version of the firmware? At this address: https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg I can only find the IND one.
Regards
Click to expand...
Click to collapse
oh they deleted it it was before. I have it on PC, but PC can't turn on.
I have found the file elsewhere... NE1-147C-UAE-0-00WW-B01.nb0
I have tried to upload using OST, and got the same result: stuck at "Reflash service bootloader..."
Is there someone that can help me?
jimgordon said:
I have found the file elsewhere... NE1-147C-UAE-0-00WW-B01.nb0
I have tried to upload using OST, and got the same result: stuck at "Reflash service bootloader..."
Is there someone that can help me?
Click to expand...
Click to collapse
which ost la version you have?
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
jimgordon said:
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
Click to expand...
Click to collapse
you need to unlock bootloader first, and you can PM code i will send you key, use only OTA through notification, don't use OST LA for this guide.
Can you tell the way you downgraded ur Nokia 3
jimgordon said:
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
Click to expand...
Click to collapse
Hi,
can u tell me the method in which you downgraded Nokia 3 from 8.0 to 7, also were u able to unlock the boot loader and root the device. Waiting for your reply as one of my friend also wanna do the same.
Hi
I've been trying to downgrade my S8 from pie to oreo or nougat and no matter what I flash in odin the device stays at android pie.
My goal is to downgrade to oreo or nougat in order to get access to the OEM Unlock button in the developers menu which is nowhere to be found on the current pie system, from then I'd put TWRP and a custom rom on the phone... if I can get this far.
Thanks for any help
Lahpyrcopa said:
Hi
I've been trying to downgrade my S8 from pie to oreo or nougat and no matter what I flash in odin the device stays at android pie.
My goal is to downgrade to oreo or nougat in order to get access to the OEM Unlock button in the developers menu which is nowhere to be found on the current pie system, from then I'd put TWRP and a custom rom on the phone... if I can get this far.
Thanks for any help
Click to expand...
Click to collapse
What model is it? Post a screen shot of it in download mode.
You can still root on android 9 ( Pie )
Downgrading is generally not possible due to Bootloader version numbers.
Generally in the past people have used the date method to to get bootloader unlock option in developers option.
There are many guides out there to do with this.
ie:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
Note: Being on pie unlocking the bootloader in developer menu does not necessary mean that the kg / rmm has change. You can check in download mode.
Backup your device before hand.
spawnlives said:
What model is it? Post a screen shot of it in download mode.
You can still root on android 9 ( Pie )
Downgrading is generally not possible due to Bootloader version numbers.
Generally in the past people have used the date method to to get bootloader unlock option in developers option.
There are many guides out there to do with this.
ie:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
Note: Being on pie unlocking the bootloader in developer menu does not necessary mean that the kg / rmm has change. You can check in download mode.
Backup your device before hand.
Click to expand...
Click to collapse
As far as a picture goes, here's one of the download mode.
It's a SM-G950W, Canadian model.
Download Mode https://i.postimg.cc/MGrR81dC/IMG-20210505-081735.jpg
Lahpyrcopa said:
As far as a picture goes, here's one of the download mode.
It's a SM-G950W, Canadian model.
Download Mode https://i.postimg.cc/MGrR81dC/IMG-20210505-081735.jpg
Click to expand...
Click to collapse
I don't own a snapdragon version model and haven't kept up with threads involved with them.
The snapdragon (US) variants U/ U1/ W you cannot unlock you bootloader. So any conventional means of rooting/custom roms can't be done.
If there is any possible way to root your phone check out threads by extreme syndicate, jrkruse usually found in Samsung Galaxy S8 roms,kernels,recoveries & other threads but i don't like your chances of rooting/custom roms your phone on Android 9 ( pie ).
spawnlives said:
I don't own a snapdragon version model and haven't kept up with threads involved with them.
The snapdragon (US) variants U/ U1/ W you cannot unlock you bootloader. So any conventional means of rooting/custom roms can't be done.
If there is any possible way to root your phone check out threads by extreme syndicate, jrkruse usually found in Samsung Galaxy S8 roms,kernels,recoveries & other threads but i don't like your chances of rooting/custom roms your phone on Android 9 ( pie ).
Click to expand...
Click to collapse
This is the general consensus I have been determining through my queries online that it's either not rootable or will take more skill than I have to do it, it's unfortunate too. The S8 with its original firmware on it is basically a dud to me because I detest samsung's software.
¯\_(ツ)_/¯ Oh well... Move on.
Don't update to the new version with Bootloader V3 because Kernel Source of V2 is released which might be able to be used to unlock the bootloader, and to make custom roms or new TWRP versions
TypicalGellert said:
Don't update to the new version with Bootloader V3 because Kernel Source of V2 is released which might be able to be used to unlock the bootloader, and to make custom roms or new TWRP versions
Click to expand...
Click to collapse
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
neotheone11 said:
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
Click to expand...
Click to collapse
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
neotheone11 said:
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
Click to expand...
Click to collapse
I just keep them paused, I'm not sure if your able to disable it with adb
tavella said:
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
Click to expand...
Click to collapse
Thank for the suggestion. Yes, that is what I meant when I said that I disabled automatic updates in the Developer Options. One of my Galaxy A32 phones kept pestering me to update despite the fact that I disabled the "automatic update" option so I was wondering if there was a better solution.
Do we know the IP addresses of the update servers? I searched online, but could not find the definitive answer.
tavella said:
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
Click to expand...
Click to collapse
My 2nd A326U is on V3 ( T-mobile ) soon bootloader will be unlocked
financeledger said:
My 2nd A326U is on V3 ( T-mobile ) soon bootloader will be unlocked
Click to expand...
Click to collapse
I also have v3 (T-mobile) and am waiting for the same thing as you.
Hello guys. Where I can see bootloader version?
Thanks for answer.
Software version. Settings/About
5th digit from end is bootloader version. For example 3AUF7 is the ending on my version. 3 is the bootloader version.
Setting/about/software information/build number
scottyrick2 said:
Software version. Settings/About
5th digit from end is bootloader version. For example 3AUF7 is the ending on my version. 3 is the bootloader version.
Click to expand...
Click to collapse
Can you take screenshoot?
Ryan.XM said:
Can you take screenshoot?
Click to expand...
Click to collapse
My Screensho is not working properly right now.
Here are Step-by-step directions to find your bootloader version.
1. open Settings on your phone
2. choose About
3. choose Software Information
4. look at the number under the Build Number section
5. the fifth character from the right is the bootloader version
Let me know if you have problems.
Best,
scottyrick2 said:
My Screensho is not working properly right now.
Here are Step-by-step directions to find your bootloader version.
1. open Settings on your phone
2. choose About
3. choose Software Information
4. look at the number under the Build Number section
5. the fifth character from the right is the bootloader version
Let me know if you have problems.
Best,
Click to expand...
Click to collapse
Ok thanks bro,
Here's what I did on my T-Mobile A326U Samsung Galaxy A32 5G
1. Open the Android 11 Settings on your phone
2. Choose About phone
3. Choose Software information
4. Look at the number under the Build number section
5. The fifth character from the right is the Bootloader version
Mine is apparently Bootloader version 6.
I recently got an A12 yesterday and I've bricked it twice trying to downgrade it. It's unbricked now but when I try to put android 10 on it, it fails. The reason I want to downgrade the os is so I can OEM unlock it. It's an sm-a125U1 and it seems no one else is having this issue.
Professorwhiz said:
I recently got an A12 yesterday and I've bricked it twice trying to downgrade it. It's unbricked now but when I try to put android 10 on it, it fails. The reason I want to downgrade the os is so I can OEM unlock it. It's an sm-a125U1 and it seems no one else is having this issue.
Click to expand...
Click to collapse
It's pretty simple actually, you can't downgrade it unless it's the same binary version. Android 10 probably has U1 if you're on Android 11 or Android 12 you're probably higher than that meaning you can't downgrade. If you're binary number was U1 as well you could
Professorwhiz said:
I recently got an A12 yesterday and I've bricked it twice trying to downgrade it. It's unbricked now but when I try to put android 10 on it, it fails. The reason I want to downgrade the os is so I can OEM unlock it. It's an sm-a125U1 and it seems no one else is having this issue.
Click to expand...
Click to collapse
Once you've upgraded the binary number you can't go back to any firmware with lower binary number
Is it possible there is an older Android version with the same binary number as my current one?
Allehandro said:
Once you've upgraded the binary number you can't go back to any firmware with lower binary number
Click to expand...
Click to collapse
I've been trying to downgrade android 10 because I want to OEM unlock it. Do you have any idea how I could OEM unlock it?
Professorwhiz said:
Is it possible there is an older Android version with the same binary number as my current one?
Click to expand...
Click to collapse
You're going to have to check for yourself. Though if android 10 is your goal, forget about it cause there's no way the binary is the same up until now.
Professorwhiz said:
Is it possible there is an older Android version with the same binary number as my current one?
Click to expand...
Click to collapse
Just check the firmware number , there is usually a U there specifying the binary number. Check yours in the settings and then check any firmware online. If it has the same number then you can use it
Professorwhiz said:
I've been trying to downgrade android 10 because I want to OEM unlock it. Do you have any idea how I could OEM unlock it?
Click to expand...
Click to collapse
I have an a125f, so for me it's straightforward. For your model you are going to have to check in the forum.
Allehandro said:
I have an a125f, so for me it's straightforward. For your model you are going to have to check in the forum.
Click to expand...
Click to collapse
I'm flashing android 11 on it right now, From what I've looked through there are no threads or posts about my phone.
Allehandro said:
I have an a125f, so for me it's straightforward. For your model you are going to have to check in the forum.
Click to expand...
Click to collapse
I was able to flash android 11, no OEM but I did search around and still found nothing.