Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
evjohns said:
Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
Click to expand...
Click to collapse
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
*Detection* said:
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
Click to expand...
Click to collapse
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
evjohns said:
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
Click to expand...
Click to collapse
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
*Detection* said:
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
Click to expand...
Click to collapse
Yep you're right, it's still XEU. I'll try a factory reset. I'm hoping the OTA update may have fixed a few things.
Can you lock the bootloader back?
parnunu said:
Can you lock the bootloader back?
Click to expand...
Click to collapse
I did a factory reset, then flashed the stock ROM again and used CSC, but the boot loader is still unlocked. I don't have the option to re-lock it, so seems like maybe you can't
Just in case this helps anyone else, I did a complete reset of the stock ROM using @rifek4 instructions from https://forum.xda-developers.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963
But i'm still not able to re-lock the boot loader. So going to leave it now and hope the option comes back after 7 days.
rifek4 said:
https://forum.xda-developers.com/showpost.php?p=76388485&postcount=51
Click to expand...
Click to collapse
Thanks for replying. Do you think that method would help me to re-lock the boot loader?
When I go to the settings the OEM unlock says "boot loader is already unlocked"
Basically all I want to do is get safety net to pass again, and it seems that having an unlocked boot loader makes it fail.
Just in case this helps anyone else.
I downloaded magisk 16.7 beta, 16.6 caused my OS (lineage 15.1) to crash, but 16.7 was fine. I installed universal safety net fix for magisk, beta version. Installation said it failed, but when I rebooted it had worked!
Safety net now passes, device is certified in play store and Google pay is working fine. As @rifek4 said, bootloader lock has nothing to do with safety net (although I've seen a lot of people claiming it does).
I waited 7 days then disabled oem unlock in the developer option.
DONE.
None of skip wait time method work for me.
Related
This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app
1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.
1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.
my friend rooted his device but stupidly turned off OEM and now his device won't turn on
I tried looking for an international firmware and flashed it on Odin but it got stuck at recovery.img, been like that for an hour,
Is it because OEM is locked? (so is FRP by the way)
Do I have to enable a setting from Odin?
he has an S9+ G965F dual SIM, he bought it from Spain but says its an international model, he doesn't seem to find the country code anywhere on the box
I need help and everything is appreciated, the sooner the better, thanks!
Check in download mode which version Bootloader the phone is running (B:1 or B:2) and match it with the firmware you are flashing, you cannot downgrade the Bootloader
G960FXXU2BRGA <<< Version 2 BL
Fixed!
*Detection* said:
Check in download mode which version Bootloader the phone is running (B:1 or B:2) and match it with the firmware you are flashing, you cannot downgrade the Bootloader
G960FXXU2BRGA <<< Version 2 BL
Click to expand...
Click to collapse
He managed to fix it himself, I was using Odin with TeamViewer from my computer to his laptop, and I think that messed with something as he repeated the exact same steps after I disconnected and worked flawlessly
Thanks everyone that helped and the community offering help!
Hi there.
I've been stuck with RMM State Prenormal on my Galaxy A8 2018 for 3 months, waiting for this to be gone. Nothing to do, after 3 months of uptime, it still there.
Many tricks with time and date hasn't worked anymore, but finally I just success to bypass this s***.
What I've done :
_Install stock rom from original carrier (BOG for me, I were on XEF for deleting bloatwares).
_At boot, do NOT put your Google account and Samsung account, only Wi-Fi and that's all.
_When install wizard is finished, do NOT activate Developpers Options. Go directly at time and date, set it 8 days before after desactivate "Auto time and date".
_Go to System Update. Then untick "auto update" and check for update.
_Reboot.
_Go back to actual time and date, check again for update.
_Only NOW, activate Developpers Options and OEM Unlock should be there.
It worked for me after MANY MANY tricks, attempts, and hopeless. This way given me another luck to root my phone and now I'm done and free with it.
Sorry if my english is sometimes bad. Hoping I've helped some users.
Regards !
Edit : I did it on bootloader V3 (U3BRJ4).
I hope it actually works with other a530f
because I have a530w and a530w doesn't have rmm prenormal in bootloader, I can't really test this
Yup, canadian and some versions of samsung smartphone (Verizon or something else if I don't mistake ?) doesn't have any method to unlock their bootloaders because they are locked by default and forever. But I've posted it for those who have international variant (SM-A530F for me).
Doghan13 said:
Yup, canadian and some versions of samsung smartphone (Verizon or something else if I don't mistake ?) doesn't have any method to unlock their bootloaders because they are locked by default and forever. But I've posted it for those who have international variant (SM-A530F for me).
Click to expand...
Click to collapse
no, I mean that Canadian variant of a8 is exactly the opposite of what you said, rmm is always unlocked, so oem unlock is always there
and a8 is the only exynos Samsung device in canada so we're lucky we didn't get any snapdragon version or that would be locked forever
Oh, mea culpa. I thought it was like Galaxy S4 who were totally locked (received one from Canada to France, last year, I were disapointed that is not GT I9500 but SGH I337M).
But the result stay the same, this is for unlocked bootloader that can be "locked" by RMM State ^^
Hello, I want to test tous method and I have an dummy question, To install stock rom, I have To flash with Odin an original firmware from sammobile and if it's yes what file I have To flash
Thx
(Sorry for my bad English I'm French ^^)
angy12 said:
Hello, I want to test tous method and I have an dummy question, To install stock rom, I have To flash with Odin an original firmware from sammobile and if it's yes what file I have To flash
Thx
(Sorry for my bad English I'm French ^^)
Click to expand...
Click to collapse
once you downloaded it, extract zip file, then there should be 5 files, dont worry about the HOME_CSC, that leaves us with 4 files, put them in the correct position on odin, AP to AP slot, etc
Hi, I've tried many times with différent BL but nothing To do' OEM doesn't appears and always state Prenormal :/
I'm on bootloader V3
It's a pity that after root we lose all the guarantees through knox
Thread cleaned:
FORUM RULES
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
adek89 said:
It's a pity that after root we lose all the guarantees through knox
Click to expand...
Click to collapse
the only thing that has irritated me so far about knox is losing samsung pay
not correct i'm on a530w and i can't access oem unlock. however i'm frp locked.... anyone know anything i can do to get back into my phone?
vibespredah said:
not correct i'm on a530w and i can't access oem unlock. however i'm frp locked.... anyone know anything i can do to get back into my phone?
Click to expand...
Click to collapse
call samsung or use a third party unlocking service is all im aware of
vibespredah said:
not correct i'm on a530w and i can't access oem unlock. however i'm frp locked.... anyone know anything i can do to get back into my phone?
Click to expand...
Click to collapse
flash stock firmware
ive never turned this thing off for 168 hours and i CAN root it. Prenormal be damned!!
youdoofus said:
ive never turned this thing off for 168 hours and i CAN root it. Prenormal be damned!!
Click to expand...
Click to collapse
Go development settings and if you see the oem and able to check that yes you root.
mchlbenner said:
Go development settings and if you see the oem and able to check that yes you root.
Click to expand...
Click to collapse
oh, i know. this was a statement, not a question
Doghan13 said:
Hi there.
I've been stuck with RMM State Prenormal on my Galaxy A8 2018 for 3 months, waiting for this to be gone. Nothing to do, after 3 months of uptime, it still there.
Many tricks with time and date hasn't worked anymore, but finally I just success to bypass this s***.
What I've done :
_Install stock rom from original carrier (BOG for me, I were on XEF for deleting bloatwares).
_At boot, do NOT put your Google account and Samsung account, only Wi-Fi and that's all.
_When install wizard is finished, do NOT activate Developpers Options. Go directly at time and date, set it 8 days before after desactivate "Auto time and date".
_Go to System Update. Then untick "auto update" and check for update.
_Reboot.
_Go back to actual time and date, check again for update.
_Only NOW, activate Developpers Options and OEM Unlock should be there.
It worked for me after MANY MANY tricks, attempts, and hopeless. This way given me another luck to root my phone and now I'm done and free with it.
Sorry if my english is sometimes bad. Hoping I've helped some users.
Regards !
Edit : I did it on bootloader V3 (U3BRJ4).
Click to expand...
Click to collapse
My friend i try this method also TWRP installed done but when i wipe and format after that still same so please can u tell me what must i do?
i have this file G955FXXU4CRL3 i followed this both post
1st This
2nd this
but still same to same now please give me perfect and working solution.
Thx
Yah, but how to install stock rom from original carrier if we cannot flash it by odin ? As longer oem unlock is not there any more to activate it ? And nothing go throu odin no root no rom or custom recovery ?
Pro Cal said:
Yah, but how to install stock rom from original carrier if we cannot flash it by odin ? As longer oem unlock is not there any more to activate it ? And nothing go throu odin no root no rom or custom recovery ?
Click to expand...
Click to collapse
You don't have oem unlock to use Odin.
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
What software channel does it have listed in about phone settings?
Here
41rw4lk said:
What software channel does it have listed in about phone settings?
Click to expand...
Click to collapse
Its here
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
41rw4lk said:
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
Click to expand...
Click to collapse
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
crpcnt.cpc said:
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
Click to expand...
Click to collapse
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
41rw4lk said:
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
Click to expand...
Click to collapse
I logged into my google account, but it doesn't enable OEM unlock yet, so the mess was big on it.
crpcnt.cpc said:
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
Click to expand...
Click to collapse
I'm in the same situation, I've tried everything, I've had several people helping me, I have the same model and variant and I can't recover at all.
Will I get security patch updates if my bootloader is unlocked?
if not, is it a good idea to relock bootloader?
my device is samsung galaxy a 32 4g (sm-a325f)
jiglex said:
Will I get security patch updates if my bootloader is unlocked?
if not, is it a good idea to relock bootloader?
my device is samsung galaxy a 32 4g (sm-a325f)
Click to expand...
Click to collapse
no once your boot loader is unlocked you will not be able to do firmware upgrades. while it is possible to trick the phone into thinking everything is normal it will always fail while trying to install the update. i have tried and it never worked. Although once you relock the boot loader even with knox tripped you will start recieving updates normally again.
Captain_cookie_200 said:
no once your boot loader is unlocked you will not be able to do firmware upgrades. while it is possible to trick the phone into thinking everything is normal it will always fail while trying to install the update. i have tried and it never worked. Although once you relock the boot loader even with knox tripped you will start recieving updates normally again.
Click to expand...
Click to collapse
Thanks for your reply mate.Can you help me with another thing which is, can I downgrade my stock firmware(flashing older stock firmware with odin) if my bootloader is locked?
jiglex said:
Thanks for your reply mate.Can you help me with another thing which is, can I downgrade my stock firmware(flashing older stock firmware with odin) if my bootloader is locked?
Click to expand...
Click to collapse
yes you can downgrade your firmware as long as the bit number is the same. e.g. there is a number ln each firmware's name like U1, U2
these may be found in the middle of the firmware's name. if the firmware you are downgrading to has a lower bit than of the firmware currently installed it will not work. you will have to choose a firmware with the same bit version. thats why always be on the lookout when upgrading to newer firmwares. for me with SM-A325F the highest bit js U2 and most of the resources are for that firmware so im fine.
Captain_cookie_200 said:
yes you can downgrade your firmware as long as the bit number is the same. e.g. there is a number ln each firmware's name like U1, U2
these may be found in the middle of the firmware's name. if the firmware you are downgrading to has a lower bit than of the firmware currently installed it will not work. you will have to choose a firmware with the same bit version. thats why always be on the lookout when upgrading to newer firmwares. for me with SM-A325F the highest bit js U2 and most of the resources are for that firmware so im fine.
Click to expand...
Click to collapse
That was a lot of help for me brother.
Thanks a lot.
jiglex said:
That was a lot of help for me brother.
Thanks a lot.
Click to expand...
Click to collapse
your welcome