Question Has anyone successfully rooted this? (A32 4G) - Samsung Galaxy A32 4G

I see one post, but it wasn't clear he actually successfully rooted the phone. I've searched, and there are instructions, but there were instructions for the Nokia 7 Plus, but you're not able to unlock the bootloader so you can't root it. So, just because there are instructions , doesn't mean you can do it.

I was able to successfully root my SM-A325F/DS. the DS stands for dual sim, I could not find firmware for dual sim but the stock firmware from samfw.com worked perfectly fine. I used magisk to patch the firmware and flashed it via Odin. Everything worked perfectly. I tried flashing the newest firmware but for some reason it deleted my IMEI and made the baseband version display as "Unkown". Upon flashing a patched version of the older firmware (the second newest version 2021-05-01) everything worked again. I would recommend trying the newest firmware and if you happen to encounter the same issue just flash the older one. I used the Samsung backup in settings and sent all my images over to my pc so restoring my phone took like 10-15 mins.
Edit: Some side notes. Since the SafetyNet update I was unable to pass it which isn't a problem for me but something to keep in mind.
I would also recommend getting an app like "System app remover" from the play store to manually debloat. I tried using a universal samsung debloater but it was a big mess and I ended up having to reflash.

Same, new firmware "auh" causes empty imei. i backed to patched "aug". Imei is back.
SafetyNet passes by this guide

N0body42 said:
I was able to successfully root my SM-A325F/DS. the DS stands for dual sim, I could not find firmware for dual sim but the stock firmware from samfw.com worked perfectly fine. I used magisk to patch the firmware and flashed it via Odin. Everything worked perfectly. I tried flashing the newest firmware but for some reason it deleted my IMEI and made the baseband version display as "Unkown". Upon flashing a patched version of the older firmware (the second newest version 2021-05-01) everything worked again. I would recommend trying the newest firmware and if you happen to encounter the same issue just flash the older one. I used the Samsung backup in settings and sent all my images over to my pc so restoring my phone took like 10-15 mins.
Edit: Some side notes. Since the SafetyNet update I was unable to pass it which isn't a problem for me but something to keep in mind.
I would also recommend getting an app like "System app remover" from the play store to manually debloat. I tried using a universal samsung debloater but it was a big mess and I ended up having to reflash.
Click to expand...
Click to collapse
what about auth error? is magisk bypassing the older-than-device-firmware lock?

Related

[Q] Need to unroot my phone.

So, I recently "rooted" my phone. With the aid of KingoRoot. Which was a bit troublesome at first cause I didn't exactly know how to handle the forever boot loop but it didn't take me long. Anyways.
After I rooted I couldn't use Samsung's Screen Mirror feature. After a couple of quick searches, I learned that I couldn't use the feature because I rooted my phone. It displayed an error which says something about a hardware issue. I want the feature back.
So I decided to unroot. I thought I did. Using, again, KingoRoot. But the error was still there and I couldn't use the feature.
I misread my android version number As 4.2.2 so I decided to update my phone as well (It was actually 4.2.2.). When I went to the software update menu and pressed update now and pressed okay, it says "The operating system on your device has been modified in an unauthorized way. Try downloading software updates using Samsung Kies on your PC, or visit a customer service center."
So I thought the root wasn't fully removed. Once again, I rooted my phone using KingoRoot. but this time used SuperSU to unroot. This also produced the same result and I still have not been able to use the feature.
I tried to use Kies. Tried Firmware upgrade and initialization. Didn't work. Tried several times. It always "fails",
My friend suggested that I use Odin to flash the stock firmware. So I went to Sammobile. Entered my model number and found lots of firmware and was confused cause I couldnt find matching firmware. Anyone know how I could get the right firmware? Or a better way to unroot?
I used "*#1234#" To get this information: AP: N7100XXUFNE1, CP: N7100XXUFND3, CSC: N7100XAFNE1.

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!
If you're in Canada then just flash the Canadian firmware.
ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?
Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html
Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.
LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?
Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:
You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.
I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?
OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.
Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!

Installing OTA updates questions/help

I purchased a Z2 Play (Freedom Mobile in Canada, XT1710-01, retca channel). I proceeded to unlock the bootloader, install TWRP and root (Magisk 13.3, then upgraded to v14). However, doing this obviously makes installing OTAs not possible. Unfortunately I didn't do a stock backup of anything before doing the above.
From my understanding, installing OTAs requires stock recovery and an unmodified system partition. So, I tried installing just the stock recovery from the RETAIL stock ROM (from here. Then I did a full uninstall of Magisk, expecting (hoping) that would put my phone back into a state (unmodified system partition) that would allow me to install OTA updates.
I presently have an OTA update pending (NPS26.118-15 which has July security updates and Moto Mods 2.0 support, among other things).
However, when I try to install it, my phone reboots and it displays the "Installing system update" screen for a few seconds, then goes to an "Error!" screen, with the green android laying down and an red exclamation mark coming out of his belly. OTA failed.
I am able to restart and boot back into Android, and get the message indicating the OTA failed and nothing was changed.
Can anyone offer any other thoughts or help on things I could try to get the OTA updates to apply? (Just for funsies, I did also try Chainfire's Flashfire, but had no luck with that either.)
I have Z2 Play from Freedom Mobile as well. I'm currently at NPSS26.118-19-4. I was bootlooping into TWRP and I had no other choice and took the risk and chanced flashing the ROM from Junior Passos over at his site. Can't post links but Google motozbrasil.
It says XT1710-07 but it's working fine for me. I'm rooted and passing SafetyNet as well. The ROM automatically detected and says retca on software channel and changed the last bit of string on the baseband as NA_Cust.
I can confirm it works but like I said was my only option. Please be careful. I'm not responsible if it doesn't work for you.
Edit: My SKU in Hardware Information displays XT1710-01 as well not XT1710-07.
atheart said:
I have Z2 Play from Freedom Mobile as well. I'm currently at NPSS26.118-19-4. I was bootlooping into TWRP and I had no other choice and took the risk and chanced flashing the ROM from Junior Passos over at his site. Can't post links but Google motozbrasil.
It says XT1710-07 but it's working fine for me. I'm rooted and passing SafetyNet as well. The ROM automatically detected and says retca on software channel and changed the last bit of string on the baseband as NA_Cust.
I can confirm it works but like I said was my only option. Please be careful. I'm not responsible if it doesn't work for you.
Edit: My SKU in Hardware Information displays XT1710-01 as well not XT1710-07.
Click to expand...
Click to collapse
That's great to hear. I've seen his ROM, but had concerns about flashing it on our device. Glad to hear, I'll probably give that a go, then.
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Thanks for sharing this. I was wondering why "nobody" has tried to flashed the RETAIL stock image (which came from a motorola server) and is mirrored at
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
?
romhippo.com said:
Thanks for sharing this. I was wondering why "nobody" has tried to flashed the RETAIL stock image (which came from a motorola server) and is mirrored at
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
?
Click to expand...
Click to collapse
It's one and the same. On Junior's site, the download link he has links the the lolinet.com one.
(http://motozbrasil.blogspot.ca/2017/09/firmware-moto-z-play-xt1710-07-firmware.html)
Junior just has helper files and instructions to make it easy.
TravellingGuy said:
It's one and the same. On Junior's site, the download link he has links the the lolinet.com one.
(http://motozbrasil.blogspot.ca/2017/09/firmware-moto-z-play-xt1710-07-firmware.html)
Junior just has helper files and instructions to make it easy.
Click to expand...
Click to collapse
Ok, great. I guess, when I read "Junior's site" , I had this site in mind at https://www.androidfilehost.com/?w=files&flid=195559&sort_by=date&sort_dir=DESC which basically contains the "stock backup" of his XT1710-07 phone.
I should not have skimmed your posts. My bad
TravellingGuy said:
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Click to expand...
Click to collapse
That's good to hear man. Now that's two so far that were successful including mine. Seems like ROM is cross compatible.
atheart said:
That's good to hear man. Now that's two so far that were successful including mine. Seems like ROM is cross compatible.
Click to expand...
Click to collapse
I also tried this RETAIL image, and it seems cross compatible in my case too. I flashed only the "service.xml" with RSD lite and did not lose any data. Software channel and model did not change either.
TravellingGuy said:
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Click to expand...
Click to collapse
An update from me on this. I mentioned I installed Junior Passos's ROM (the August update one), but then left my phone at stock (no root, no TWRP) to see if OTAs would work. Good news, I got the notification about the September OTA update yesterday, and I was able to download and install it with no issues! Sweet.
TravellingGuy said:
An update from me on this. I mentioned I installed Junior Passos's ROM (the August update one), but then left my phone at stock (no root, no TWRP) to see if OTAs would work. Good news, I got the notification about the September OTA update yesterday, and I was able to download and install it with no issues! Sweet.
Click to expand...
Click to collapse
Do you have updates in English after doing all of this? I just got my Z2 Play from Amazon today and noticed that it is on the RETLA channel and all of my system updates are in Spanish. The phone still functions in English, and so far I have found nothing else that is not in my language. However, it kind of bothers me that my updates are not tied to my region, so I'm really hoping that there is a way to get my phone on the RETUS channel, or at the very least, get my update notes in my language.

Trouble installing stock firmware on samsung galaxy a5 2017 sm-a520f

I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Flash a firmware version that contains S6 or U6 in the middle, it won't work with U5/S5! Not the Samsung phone S5 or S6, but rather, the firmware version.
For cellular, change the modem firmware, or backup and wipe /data/. /data/data/?.
Unless the efs was wiped (probably not if the baseband version isn't there, load a backup then, only if the efs was wiped don't restore it otherwise, and it must not be a backup created with an older twrp, view the recovery log in the backup folder)
julianmunozvaras said:
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Click to expand...
Click to collapse
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
iloveoreos said:
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
Click to expand...
Click to collapse
I tried installing the latest version available and I had the same error.
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Well, I don't know what else could be wrong.
Sent from my Samsung SM-A520W using XDA Labs
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Listen to me, it happened to me 2 days ago, and I came to the conclusion that I was not flash the latest firmware. You need to flash the same firmware with the same bootloader or more recent, the error you receive is because you are flashing an older version of bootloader. Do one thing, type the code *#1234# on the phone keypad
mark the code that gives you on 'AP and look it on Sammobile at https://www.sammobile.com/firmwares/galaxy-a5/SM-A520F/ITV/ select your language and look for the firmware with your own code . You will see that odin flash it.
Samsung A520F Custom Binary Error
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
koolblowkid said:
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
Click to expand...
Click to collapse
Obviously you are frp locked. But I didn't think that blocked from flashing official.

Unlock to TMB FW

Hello,
I just got a SM-N970U1 which I'm trying to convert to TMB FW. There are a couple of threads out there however haven't been updated with actual fixes since being posted in Aug 2019.
Issue I encountered, I used odin v3.14 to flash FW (bl/ap/cp/csc) that I got from Frija. It flashes fine, goes through the motions, however in the end, TMB settings aren't applied, meaning there is no splash screen, no RCS/Video etc. The android did update to V10, with UI of 2.0 (this was older version in stock phone), so that part did work.
I did follow the "put sim in, let do carrier initialization etc.", no changes.
I've attempted to flash a few times but haven't had any luck.
Any ideas for a fix? Hoping someone has come up with something for this as the phone has been out for sometime now.
So if anyone in the future needs this info, I ended up downloading the latest available TMO firmware for SM-970U (which is the carrier version of the phone), and just flashed using odin. Cleared the cache, and boom, works!
Not sure about OTA updates yet, as the FW i've installed has the 03/2020 patch.

Categories

Resources