⚠️Galaxy A71 Root || Unlock Bootloader || Flash Official Firmware [Binary 1] February

endor43

Senior Member
Jul 15, 2011
66
9
0
Unlocking the bootloader in itself doesn't void warranty.

Make sure you understand and do the following steps in the following order:

->Enable OEM Unlocking in developer settings
->Reboot phone to download mode
->Go to bootloader unlock menu (in download mode, it should tell you how to do that)
->The phone will reboot and wipe data
->Skip setup and then go to developer settings again and make sure OEM unlock is still on
->After that, you will be able to flash any custom firmware.
I did those steps exactly in that order, and the OEM unlock became selected and greyed out as I understand it should.
 

ShaDisNX255

Senior Member
Apr 3, 2014
1,774
926
143
Matamoros
It just failed immediately when flashing stock.... My phone screen looks same as above screenshot (stuck downloading with partial progress bar).
Attached is the Odin screenshot.
I am sorry for all this trouble, but I appreciate the help.
This time I was flashing everything including BL, so risk of brick must be higher.
Should I do the same thing, Vol - and Power then both vol buttons to restart to download mode again? (After I did this on the first phone, it never turned on again).

Thank you!
I understand your concern, don't worry I'll try to help you as much as possible.

Yes, I would try it again. And when flashing with Odin, try to run it as administrator from Windows, can make the difference.
 

endor43

Senior Member
Jul 15, 2011
66
9
0
I understand your concern, don't worry I'll try to help you as much as possible.

Yes, I would try it again. And when flashing with Odin, try to run it as administrator from Windows, can make the difference.
Thank you very much!
Rebooting into download mode worked again, so I will try once more to reflash stock with Odin running as admin....Flashing now, looks like it is going through.
If it works I will try everything once more right away
Will update.

---------- Post added at 08:11 AM ---------- Previous post was at 07:20 AM ----------

I understand your concern, don't worry I'll try to help you as much as possible.

Yes, I would try it again. And when flashing with Odin, try to run it as administrator from Windows, can make the difference.
It worked! I am at NcX2.5 now and going to do 2.5.1 tomorrow morning. It's the middle of the night here.
Thank you so much for your help.
I am not entirely sure, but I would say that maybe it was the Odin in admin mode suggestion that did it.

This means I don't need to waste another 400+ dollars on another phone.
Thanks again very much.
 

ShaDisNX255

Senior Member
Apr 3, 2014
1,774
926
143
Matamoros
Thank you very much!
Rebooting into download mode worked again, so I will try once more to reflash stock with Odin running as admin....Flashing now, looks like it is going through.
If it works I will try everything once more right away
Will update.

---------- Post added at 08:11 AM ---------- Previous post was at 07:20 AM ----------



It worked! I am at NcX2.5 now and going to do 2.5.1 tomorrow morning. It's the middle of the night here.
Thank you so much for your help.
I am not entirely sure, but I would say that maybe it was the Odin in admin mode suggestion that did it.

This means I don't need to waste another 400+ dollars on another phone.
Thanks again very much.
Glad to know it worked! It can be very stressful to do this and watch it not go according to plan, especially when your device already bricked before.
To be honest with you, I highly doubt this was your problem last time. The error you showed on your screenshots suggest that Odin didn't flash a thing, because it wasn't able to "open" anything in the .tar file you were trying to flash.
I usually don't open Odin as admin mode, so it surprised me when you showed me that error. I legit do think you may have gotten a defective unit. Either that or somehow Magisk corrupted your files and damaged your phone, but I don't know the odds of that happening.
 

andreoide

Senior Member
Mar 5, 2013
1,765
259
113
Enschede
Glad to know it worked! It can be very stressful to do this and watch it not go according to plan, especially when your device already bricked before.
To be honest with you, I highly doubt this was your problem last time. The error you showed on your screenshots suggest that Odin didn't flash a thing, because it wasn't able to "open" anything in the .tar file you were trying to flash.
I usually don't open Odin as admin mode, so it surprised me when you showed me that error. I legit do think you may have gotten a defective unit. Either that or somehow Magisk corrupted your files and damaged your phone, but I don't know the odds of that happening.
I think flashing with Odin in admin mode, as well as disconnect from internet and turn off any antivirusscanner while flashing will solve future problems for him...
 

djcmn

Senior Member
Oct 27, 2012
64
22
0
New Hope, MN
Just bought an unlocked galaxy s10 a few days ago and plan on returning it tomorrow since it cannot be rooted due to it being the Snapdragon. I plan on getting this phone instead. I assume this method will work on the A71 unlocked 5G model. I absolutely cannot deal with not having root along with Adaway and Viper4Android. My old rooted s4 with Viper4Android absolutely KILLS the s10 in the audio department. If Samsung had any brains at all, they would get with the developers of that outstanding Viper4Android app and hit a licensing deal.
 

canedera

New member
May 4, 2018
2
0
0
I tried everything. With the new version of magisck, I didn’t keep going until my ringtone cost me making it work I really want to root my room and the most resent with one ui 2.5. I did it all and even followed your video on you tube. brack my cellphone cost click the rom on it again. will be what I'm doing wrong I tried to modify with magisck the boot the image did not work with the ap of the rom also it did not always ta damage failure
 

ShaDisNX255

Senior Member
Apr 3, 2014
1,774
926
143
Matamoros
Just bought an unlocked galaxy s10 a few days ago and plan on returning it tomorrow since it cannot be rooted due to it being the Snapdragon. I plan on getting this phone instead. I assume this method will work on the A71 unlocked 5G model. I absolutely cannot deal with not having root along with Adaway and Viper4Android. My old rooted s4 with Viper4Android absolutely KILLS the s10 in the audio department. If Samsung had any brains at all, they would get with the developers of that outstanding Viper4Android app and hit a licensing deal.
From what I understand, all Samsung phones are bootloader locked in the U.S. no matter what.
If you want a Samsung rooted phone, you're going to have to get one imported.
I hope this confirms that Samsung has no brains at all :)
 

djcmn

Senior Member
Oct 27, 2012
64
22
0
New Hope, MN
Thank You.

From what I understand, all Samsung phones are bootloader locked in the U.S. no matter what.
If you want a Samsung rooted phone, you're going to have to get one imported.
I hope this confirms that Samsung has no brains at all :)
Thanks! I am currently looking at a Motorola - moto edge 5G 256GB (Unlocked) as a replacement for the S10. From what I have read, this seems more promising.
 

DonAndress

Senior Member
Mar 16, 2010
861
91
0
Kraków
Just bought an unlocked galaxy s10 a few days ago and plan on returning it tomorrow since it cannot be rooted due to it being the Snapdragon.
Say what? Snapdragon makes it impossible to unlock bootloader?

From what I understand, all Samsung phones are bootloader locked in the U.S. no matter what.
Does that mean that bootloader is impossible to unlock?
I once had an idea to buy a phone in US [emoji6]
 

ShaDisNX255

Senior Member
Apr 3, 2014
1,774
926
143
Matamoros
Does that mean that bootloader is impossible to unlock?
I once had an idea to buy a phone in US [emoji6]
Yeah, phones sold in the US are impossible to unlock bootloader for free, I think there is a service now that does it but it costs money and I'm not sure how much. You're better off doing some research if you want to buy a US phone.
 

andreoide

Senior Member
Mar 5, 2013
1,765
259
113
Enschede
Yeah, phones sold in the US are impossible to unlock bootloader for free, I think there is a service now that does it but it costs money and I'm not sure how much. You're better off doing some research if you want to buy a US phone.
In XdaLabs choose APPS
Find App called US GALAXY BOOTLOADER UNLOCK and read from there.
 

Lil_Boudy

New member
Nov 17, 2020
3
0
1
I don't understand this part! Someone help

To boot in recovery or boot the system with Magisk installed:

1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery

Another question: I have already unlocked the bootloader, does it clear my data when doing the root steps?
 

yunseok000_

New member
Dec 12, 2019
4
0
0
To anyone having bootloops:

Code:
MAKE SURE THE PHONE IS TURNED OFF!

- Hold [VOL+] + [POWER] FOR STOCK RECOVERY
	WHEN IN STOCK RECOVERY:
		1) MOUNT SYSTEM THEN REBOOT SYSTEM AND HOLD [VOL+] + [POWER]
		2) BOOTLOADER WARNING: PRESS [POWER] THEN SAMSUNG LOGO
		3) HOLD [VOL+] UNTIL RECOVERY
		4) RECOVERY MODE: REBOOT SYSTEM
		5) BOOTLOADER WARNING: PRESS [POWER]
		6) SAMSUNG LOGO (THE DEVICE WILL BOOTLOOP)
		7) WAIT
 

andreoide

Senior Member
Mar 5, 2013
1,765
259
113
Enschede
To anyone having bootloops:
Again a piece of info nobody know what to do with it.
If you post in this thread, at least give info when such assumed bootloop occurs, what you did before causing it, and finish the "code" as you call it here, wich is in fact just a piece of info you just simply copied from somewhere maybe not even trustworthy place on internet, and pasted here.
Name your sources if you copy.
In my opinion the posting is useless, threadfilling garbage "code " wich is not code at all.
 
Last edited:

yunseok000_

New member
Dec 12, 2019
4
0
0
Again a piece of info nobody know what to do with it.
If you post in this thread, at least give info when such assumed bootloop occurs, what you did before causing it, and finish the "code" as you call it here, wich is in fact just a piece of info you just simply copied from somewhere maybe not even trustworthy place on internet, and pasted here.
Name your sources if you copy.
In my opinion the posting is useless, threadfilling garbage "code " wich is not code at all.
DUDE, I followed this tutorial like months ago, everything worked fine then yesterday I had to restart my phone and then I got into a bootloop, dude. Then I looked at this thread and I remember this dude posting some kind of fix for another dude. So I followed it and the bootloop is gone. I need to thank this dude. Dude. Also, I just used the "code" tag just so I can reformat it because most of dudes in this thread don't know how to write text and guides properly. Using the code tag doesn't mean I'm writing code, dude.

Also, the post in question:
Okay, this method is working for me except the last, but i solved it:
I patched the AP file in Magisk Manager, copied back to my pc, opened the tar file with 7zip and deleted all files except recovery.img and vbmeta.img.
I opened the original prepatched AP file in 7Zip and extracted the boot.img.lz4 and dragged it to lz4.exe.
I copied the uncompressed boot.img to my phone and patched it in magisk manager, copied back the patched file to my pc and put it in the tar file, flashed with odin (before flashing I unticked the auto reboot), after it's done, I pressed and held volume down and power and when the screen went off, quickly changed to volume up and power button and hold until the bootloader warning appeared, I released the buttons, and I pressed the power button to continue to samsung logo, and my phone got bootloop (after a few seconds).
After it restarts and the screen went off I quickly pressed and held the volume up and power button until the bootloader warning appeared again, pressed the power button, and after the samsung logo appeared, quickly pressed and held the volume up until the stock recovery does not appear -> stock recovery -> mount system -> reboot to the system -> hold volume up and power button (!) -> bootloader warning - press power button to continue -> samsung logo -> press and hold the volume up until the recovery does not appear -> recovery -> reboot to the system -> wait until the bootloader warning (and do not press and hold volume up and power (!) ) -> press the power to continue -> samsung logo, and wait and the phone is booted and working with magisk root. If you reboot the phone or shutdown it, magisk root is still working without pressing volume up and power.
 

andreoide

Senior Member
Mar 5, 2013
1,765
259
113
Enschede
DUDE, I followed this tutorial like months ago, everything worked fine then yesterday I had to restart my phone and then I got into a bootloop, dude. Then I looked at this thread and I remember this dude posting some kind of fix for another dude. So I followed it and the bootloop is gone. I need to thank this dude. Dude. Also, I just used the "code" tag just so I can reformat it because most of dudes in this thread don't know how to write text and guides properly. Using the code tag doesn't mean I'm writing code, dude.

Also, the post in question:
You just "dude" too much, keep that blabla away from XDA, it is offending inpolite.
If you can't stand critics on your "code" past_posting dont post it in the first place
Learn to use proper language, politeness and respect to others, and post things in the right order:
-DESCRIBE THE PROBLEM YOU ENCOUNTER
-THAN DESCRIBE YOUR SOLUTION
Posting that way, everybody gets your intention and understands right away what you are pasting and why.
 
Last edited: