Question Reinstall firmware with locked bootloader - Samsung Galaxy A52s 5G

Hello, I tried to flash the non-touch TWRP on my phone and after I entered TWRP, I used my OTG cable to find a way to exit TWRP recovery, the phone went to a bootloop after rebooting system. When I go to Download mode I could barely see the KG state and OEM lock: On, but after downloading and installing firmware via Odin, the app says Fail and fails to install firmware. What went wrong?

Maybe you downloaded the wrong firmware. Try the latest one from here: https://samfw.com/firmware/SM-A528B/DBT
(no idea what country you are in so i chose germany

JanBoyGamer23 said:
Maybe you downloaded the wrong firmware. Try the latest one from here: https://samfw.com/firmware/SM-A528B/DBT
(no idea what country you are in so i chose germany
Click to expand...
Click to collapse
I downloaded the firmware for Serbia, South East Region (SEE), but I don't know if it could be possible to install stock firmware with locked bootloader.

NickDeveloper said:
I downloaded the firmware for Serbia, South East Region (SEE), but I don't know if it could be possible to install stock firmware with locked bootloader.
Click to expand...
Click to collapse
Follow these instructions and all should be fine WITH a locked bootloader.
https://www.sammobile.com/wp-content/themes/sammobile-6/assets/static/instructions-fw-5file.pdf

Related

[q] help major porblem my phone wont boot

okay so i was trying to install bootloader through twrp , it failed (tried clearing dalvik and cache but it still failed) so i gave up on it and pressed reboot, once that happened, the device name appeared for a split second then dissapeared then appeared then dissapeared (keeps appearing and dissapearing) I CANT ACCCESS TWRP MENU , OR BOOT ONLY DOWNLOAD MODE, WHAT DO I DO D:
OmarKnows said:
okay so i was trying to install bootloader through twrp , it failed (tried clearing dalvik and cache but it still failed) so i gave up on it and pressed reboot, once that happened, the device name appeared for a split second then dissapeared then appeared then dissapeared (keeps appearing and dissapearing) I CANT ACCCESS TWRP MENU , OR BOOT ONLY DOWNLOAD MODE, WHAT DO I DO D:
Click to expand...
Click to collapse
Generally speaking: Install bootloader only with Odin.
You should now flash firmware using Odin to save your device. Maybe Kies could restore also.
Androidwizzard said:
Generally speaking: Install bootloader only with Odin.
You should now flash firmware using Odin to save your device. Maybe Kies could restore also.
Click to expand...
Click to collapse
how exactly do i do that? can you provide any links?
OmarKnows said:
how exactly do i do that? can you provide any links?
Click to expand...
Click to collapse
HERE you may find firmware for your country/device, download.
Start Odin, connect your phone in download mode to pc, see if Odin shows up com-port and flash firmware in tab PDA/AP.
There are several guides on youtube/google
Cant Find my carrier
my carrier is international, only countries are on that list, I dont know which one to choose, also if im gonna flash firmware is it possible to flash 4.1.2? or 4.2.2/4.3?
OmarKnows said:
my carrier is international, only countries are on that list, I dont know which one to choose, also if im gonna flash firmware is it possible to flash 4.1.2? or 4.2.2/4.3?
Click to expand...
Click to collapse
Depends on your last firmware. What was the bootloader version? If above MJ5, you can't downgrade so you are free to flash eg latest 4.4.2
Androidwizzard said:
Depends on your last firmware. What was the bootloader version? If above MJ5, you can't downgrade so you are free to flash eg latest 4.4.2
Click to expand...
Click to collapse
I have no idea what bootloader i have
OmarKnows said:
I have no idea what bootloader i have
Click to expand...
Click to collapse
Great, and which one didya try to flash through TWRP?
Androidwizzard said:
Great, and which one didya try to flash through TWRP?
Click to expand...
Click to collapse
The MJ5 bootloader, i found one that said it would be flashable through a recovery menu
OmarKnows said:
The MJ5 bootloader, i found one that said it would be flashable through a recovery menu
Click to expand...
Click to collapse
1. Never flash bootloader through recovery
2. I assume that you have had newer bootloader than MJ5 before flash, so you soft bricked your device
3. To regain full funtional device follow post #4
Androidwizzard said:
1. Never flash bootloader through recovery
2. I assume that you have had newer bootloader than MJ5 before flash, so you soft bricked your device
3. To regain full funtional device follow post #4
Click to expand...
Click to collapse
im having trouble , check my post here : http://forum.xda-developers.com/gal...m-via-odin-t2868125/post55256421#post55256421

Updated Bootloader: Bootloop, cannot access recovery, can access download mode !

After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.

Help! Cant flash TWRP

Cant flash TWRP or root.
What download mode says:
ODIN MODE
DOWNLOAD SPEED:FAST
PRODUCT NAME: SM-A520F
CURRENT BINARY: SAMSUNG OFFCIAL
SYSTEM STATUS: OFFICIAL
RMM STATERENORMAL
FAP LOCKFF
SECURE DOWNLOAD :ENABLED
CCIC=
WARRANTY VOID=1 (0X0500)
RP SWREV: B:2 K:1 S:1
DID: 07344e3b5304
ONLY OFFICIAL BINARIES ARE ALLOWED TO BE FLASHED(RECOVERY)
---------------------------
build number:NRD90M.A520FXXU2BQK1
oem unlock and usb debugging are on
Unfortunately you upgraded your firmware to last version and this update blocked the bootloader.you can t root or use custom recovery ,your phone will remain stock. i have the same problem , we can t do anything.
Maybe one user from xda will find a method..
tibigabi27 said:
Unfortunately you upgraded your firmware to last version and this update blocked the bootloader.you can t root or use custom recovery ,your phone will remain stock. i have the same problem , we can t do anything.
Maybe one user from xda will find a method..
Click to expand...
Click to collapse
which frimware, is it all or just one?
I think the last firmware.And doesn t work if you flash an old version , or install 6.0.1 , i tried.
tibigabi27 said:
I think the last firmware.And doesn t work if you flash an old version , or install 6.0.1 , i tried.
Click to expand...
Click to collapse
I installed the Turkish version of A520FXXU2BQJ6 with november patch and all working great!
In Europe latest firmware's are locked so you can't flash TWRP via Odin.
But countries like India, Turkey etc.... there isn't any problem.
ChARCOOL said:
In Europe latest firmware's are locked so you can't flash TWRP via Odin.
But countries like India, Turkey etc.... there isn't any problem.
Click to expand...
Click to collapse
I didn t know this , i will install now and i will edit my post.
EDIT: IT WORKS GUYS.Thanks for your info !
Try this method:
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
I can't flash custom recovery
I have a520F I changed custom rom then I back to stock rom... I changed country firmware then I try to flash again custom recovery but everytime I flashed its failed.. what to do?
Twrp fail To Flash in A520f Nougat
I Have The same Problem when I Flash it Fail.
And Said That Only official Frimware Are Allowed To Flash.
What I Do Plz Helpp....
Thankss In Advance
:crying:
sajjad haider said:
I Have The same Problem when I Flash it Fail.
And Said That Only official Frimware Are Allowed To Flash.
What I Do Plz Helpp....
Thankss In Advance
:crying:
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
I want to ask, if we are using ROM XID (indonesia) and paired with a botloader from the Brazil ROM, will it work or not ??

OEM Locked whilst with custom rom

OK I have officially screwed up...
So it was all going smoothly flashing a tweaked custom rom and twrp successfully and then I decided to back to stock...
I accidentally (ok maybe not so accidentally) flipped the OEM unlock switch and now I am locked out of my phone since I still had the custom binary on the phone.
I tried to flash the latest stock firmware for the s9 BTU found from samfirm but odin seemed to have not liked the firmware or something and it gave me an a red message on the odin mode screen.
When I try to flash everything at once I get "REV Failed Check (Bootloader)"
When I try to flash just AP I get "REV Failed Check (Kernel)"
At the moment when I boot up I get the message telling me to use emergency software recovery but Smart Switch does not seem to recognise the device either in the emergency recovery page however it does try to connect on the home page.
I'm not too sure what to do, any help would be nice?
Thank you
You cannot downgrade the bootloader, check which version your phone has in Download mode (BL: xx) and check which version the firmware you are flashing has G960FXXU1BRF8
*Detection* said:
You cannot downgrade the bootloader, check which version your phone has in Download mode (BL: xx) and check which version the firmware you are flashing has G960FXXU1BRF8
Click to expand...
Click to collapse
OK I think I have found the BL version from the line that says...
"RP SWREV B:2 K:2 S:2"
But what firmware has the BL Version 2? They all seem to have a BL version of 1 from what you've said?
If there are no firmware which match this, what do I do? Is my phone redundant?
Delks123 said:
OK I think I have found the BL version from the line that says...
"RP SWREV B:2 K:2 S:2"
But what firmware has the BL Version 2? They all seem to have a BL version of 1 from what you've said?
If there are no firmware which match this, what do I do? Is my phone redundant?
Click to expand...
Click to collapse
OK
I saw on another thread that was replied to about the Hong Kong version having been already upgraded to BL 2 so I am going to give flashing that a go and I will report back.
Delks123 said:
OK
I saw on another thread that was replied to about the Hong Kong version having been already upgraded to BL 2 so I am going to give flashing that a go and I will report back.
Click to expand...
Click to collapse
Yea you'll either have to do something like that, or wait for your region firmware to have it's BL updated
Tried it out with a BL2 BTU firmware from SamMobile and the flash went smoothly however now I'm stuck in a bootloop when I'm trying to boot up.
I know this could be anything but I can't get any form of logs as the only mode I have is Odin mode available to me...
The way I flashed it was by doing BL first followed by AP, CP then CSC separately with auto reboot and one other one checked that was instructed by SamMobile. I tried to do them together but I keep getting an error of not being able to read a line.
What should my next step be?
What could be the reason for this bootloop as according to Odin the flash went well?
Thanks in advance
Delks123 said:
Tried it out with a BL2 BTU firmware from SamMobile and the flash went smoothly however now I'm stuck in a bootloop when I'm trying to boot up.
I know this could be anything but I can't get any form of logs as the only mode I have is Odin mode available to me...
The way I flashed it was by doing BL first followed by AP, CP then CSC separately with auto reboot and one other one checked that was instructed by SamMobile. I tried to do them together but I keep getting an error of not being able to read a line.
What should my next step be?
What could be the reason for this bootloop as according to Odin the flash went well?
Thanks in advance
Click to expand...
Click to collapse
You might need to check "Repartition" in ODIN only, flash all 4 parts at the same time, use CSC and not HOME_CSC
Make sure you are using ODIN 3.13.1
Oh yea forgot the update...
I got it working, I think I unchecked repartition and auto reboot whilst flashing all of them together to get it working
So yea this is now solved

SM-A720F (A7 2017) Flashing INS firmware over XSG - Odin Error

I have a Samsung A7 2017 (SM-A720F) brought from UAE having latest Oreo update. While I tried to flash an INS version over this Odin detects the phone. But after hitting start it takes some time and gives error like failed. I also tried to root it with CF-AutoRoot file. Those also have the same error. Developer mode, USB debugging and OEM unlock are ON. Trying with windows 10 + Odin 3.13 (latest). Any solution ?
Combination file successfully flashed. But, still not able to flash another country File. Can I proceed with original country file (i.e XSG stock firmware) ?
Please help me
MajjuBhai said:
I have a Samsung A7 2017 (SM-A720F) brought from UAE having latest Oreo update. While I tried to flash an INS version over this Odin detects the phone. But after hitting start it takes some time and gives error like failed. I also tried to root it with CF-AutoRoot file. Those also have the same error. Developer mode, USB debugging and OEM unlock are ON. Trying with windows 10 + Odin 3.13 (latest). Any solution ?
Click to expand...
Click to collapse
Root with twrp and magisk, cfautoroot is OG in my opinion . Try flashing just CSC_home or whatever it is called in Odin.
SnowFuhrer said:
Root with twrp and magisk, cfautoroot is OG in my opinion . Try flashing just CSC_home or whatever it is called in Odin.
Click to expand...
Click to collapse
I'm able to flash Combination file, original country (XSG) file and also flashes TWRP. But, I can't get access to TWRP after flashing it. Always it replaced by Stock recovery. And apart these 3 files nothing flashes, including CSC file alone...
MajjuBhai said:
I'm able to flash Combination file, original country (XSG) file and also flashes TWRP. But, I can't get access to TWRP after flashing it. Always it replaced by Stock recovery. And apart these 3 files nothing flashes, including CSC file alone...
Click to expand...
Click to collapse
When you flash twrp, untick auto reboot in odin. Boot straight into twrp without booting system.
SnowFuhrer said:
When you flash twrp, untick auto reboot in odin. Boot straight into twrp without booting system.
Click to expand...
Click to collapse
Ok Boss. One last question. After rooting my phone Can I able to flash any country Firmware on my phone ?
If Yes, Any precuations to be taken ?
(Currently it is on RMM State : Prenormal, I will try flashing TWRP after a couple of days.)
MajjuBhai said:
Ok Boss. One last question. After rooting my phone Can I able to flash any country Firmware on my phone ?
If Yes, Any precuations to be taken ?
(Currently it is on RMM State : Prenormal, I will try flashing TWRP after a couple of days.)
Click to expand...
Click to collapse
It won't help change the csc. But hadesrom oneui has a huge selection of csc's you can select when flashing it.
SnowFuhrer said:
It won't help change the csc. But hadesrom oneui has a huge selection of csc's you can select when flashing it.
Click to expand...
Click to collapse
If I flashed HadesROM OneUI with 'INS' CSC can I able to downgrade it with INS Stock firmware in future ?
Is the binary thing really need to consider while flashing that ?
PS : I looked on HadesROM. It is temptating. But, the real problem is with VoLTE which affects the network badly here... The VoLTE only network is a large mess here... And thanks for your unconditional Help & Support :fingers-crossed:
MajjuBhai said:
If I flashed HadesROM OneUI with 'INS' CSC can I able to downgrade it with INS Stock firmware in future ?
Is the binary thing really need to consider while flashing that ?
PS : I looked on HadesROM. It is temptating. But, the real problem is with VoLTE which affects the network badly here... The VoLTE only network is a large mess here... And thanks for your unconditional Help & Support :fingers-crossed:
Click to expand...
Click to collapse
It should work to change csc with Hades and then flash stock. Just make sure you don't reflash csc then because it could change.

Categories

Resources