Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Edit: Flashed Indonesian CSC for the features I need the most. Debloated extensively trough adb. Will probably wait for a TWRP release for this model -- may switch if no rooting is available over a long period.
Jumpkid said:
Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Click to expand...
Click to collapse
I also bought an A52 5G thinking I could unlock the bootloader and root but found no way to do it. A solution may come, but I just returned the phone for a OnePlus 9 5G (not pro) and I am pretty happy. Had it rooted in a couple hours. It was roughly the same price. I just don't like the "wakeup/on-off restart" button placement, coming from an LG V30 which had it centered on the back of the phone. If not for the 5G, The V30 is still a decent daily driver. Let me know if you find a way.
hammeru said:
It was roughly the same price.
Click to expand...
Click to collapse
don't talk nonsense. the 9er costs considerably more.
Hot-Proton said:
don't talk nonsense. the 9er costs considerably more.
Click to expand...
Click to collapse
I suppose your interpretation of price is correct, but it is still reasonable for a non-flagship phone IMHO.
Also buy Samsung A52s and not can rooting, always not starting - very bad :/
hammeru said:
I also bought an A52 5G thinking I could unlock the bootloader and root but found no way to do it. A solution may come, but I just returned the phone for a OnePlus 9 5G (not pro) and I am pretty happy. Had it rooted in a couple hours. It was roughly the same price. I just don't like the "wakeup/on-off restart" button placement, coming from an LG V30 which had it centered on the back of the phone. If not for the 5G, The V30 is still a decent daily driver. Let me know if you find a way.
Click to expand...
Click to collapse
That's strange, because looking around this forum, there's no issue with unlocking bootloader for A52, even the A52s.
With A52s though, there seems to be issue with rooting, according to OP. As a result, I'd suggest not unlocking bootloader unless someone who's already unlocked confirms that rooting works. There's no point in unlocking bootloader until then.
All I can say is my experience was different when trying to unlock the bootloader. I found it very frustrating and Samsung was no help.
I'm planning to buy this phone, but I heard somewhere that oem unlock option is missing from developer options but I dunno which model
Maybe I'll skip samsung phone
specialex said:
I'm planning to buy this phone, but I heard somewhere that oem unlock option is missing from developer options but I dunno which model
Maybe I'll skip samsung phone
Click to expand...
Click to collapse
The option is available with A528B. Maybe only US variants don't have it.
Yes, but still not possible ( unlock bootloader and OEM - OK ) susceful rooted :/
SAME HERE NO LUCK
The OEM unlock option didn't show up for me till I both updated *and* had a password.
I'm also having the bootloop issue after patching boot.img or the AP tarball with magisk.
I tried many times and failed
Jumpkid said:
Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Edit: Flashed Indonesian CSC for the features I need the most. Debloated extensively trough adb. Will probably wait for a TWRP release for this model -- may switch if no rooting is available over a long period.
Click to expand...
Click to collapse
Tôi cũng đã thử mọi cách nhưng không thành công. hy vọng ai đó có thể giúp đỡ, ít nhất twrp cho A528b
Translated by GT: I also tried everything but no success. hope someone can help, at least twrp for A528b
If i would own this device i would look at the steps to get the device rooted on a exiting root method of another phone model of the same manufacturer with nearly the same processor.
That could do the trick especially if there needs to be flashed another zip file to get root like the case is for many android versions on different phones...
I found some sites that claim to have working root-methods, but can't verify they are working.
Site1 Site2 Site3
Can anyone please test this out? I want to buy this phone as it is a really good bang for the buck, but I have to know before if my rooted firewall AND my banking-app will work on that
revnu said:
I found some sites that claim to have working root-methods, but can't verify they are working.
Site1 Site2 Site3
Can anyone please test this out? I want to buy this phone as it is a really good bang for the buck, but I have to know before if my rooted firewall AND my banking-app will work on that
Click to expand...
Click to collapse
These methods do not work. See the description on those websites and compare them with the first post in this thread.
Jumpkid said:
These methods do not work. See the description on those websites and compare them with the first post in this thread.
Click to expand...
Click to collapse
Jap, I also thought that. So I think then we simply have to wait untill some ambitious people find working root methods
I have the same problem, is it resolved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jumpkid said:
Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Edit: Flashed Indonesian CSC for the features I need the most. Debloated extensively trough adb. Will probably wait for a TWRP release for this model -- may switch if no rooting is available over a long period.
Click to expand...
Click to collapse
I have the same problem, is it resolved
Please help me root my phone A52S 5G
The question is, why do you want to root this phone? You will lose your warranty, 2-3 years automatic updates or have to install these manually.
Related
Can someone please explain to me how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!
doubleplay648 said:
Can someone please explain to me
how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!
Click to expand...
Click to collapse
I replied to you on PM, but this may be helpful for others.
Repartitioning has nothing to do with downgrade-ability. The Safe Upgrade won't work for you either, since it includes older TrustZone. N910VVRU2BPA1_StockRestore_Incremented.tar.md5 didn't change any of the critical partitions. You'll need a similar tar for OG5 to be able to downgrade, which isn't available unfortunately.
Click to expand...
Click to collapse
However, you could flash OG5 ROM via TWRP, if you wish.
Cannot install TWRP
hsbadr said:
I replied to you on PM, but this may be helpful for others.
However, you could flash OG5 ROM via TWRP, if you wish.
Click to expand...
Click to collapse
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?
doubleplay648 said:
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?
Click to expand...
Click to collapse
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.
hsbadr said:
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.
Click to expand...
Click to collapse
So i have the developer edition. I sent it into samsung for repair and i mentioned several times about the bootloader being unlocked. I tried flashing the twrp tar you gave me and it gave me a odin fail and my phone says SECURE CHECK FAIL: recovery
The only thing i did when i got my phone back was upgrade the 5.0.1 to your 5.1.1 incremented stockrestore.
Did i do this right?
1. put phone into download mode (power + volume down+ home)
2. plug into pc and open odin.
3. flash the tar via ap, without checking re-partition
So any idea why this isn't working? Samsung had to replaced the motherboard in my phone. Is it possible that when they sent back my phone they updated the SW to a locked bootloader?
Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!
doubleplay648 said:
Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!
Click to expand...
Click to collapse
Your phone is retail. If you want DevEd you will need to talk to one of the few folks at Samsung that know what a Deved is. Convince them that they retailed your phone when they replaced the main board. They should fix this. The only number you should call is the 800 number on your DevEd receipt. If the CSR doesn't know what your talking about, ask for a supervisor, escalate until they know what you have. They need to be clear what you have, or it will return retail again. The good news is they will flash your fuse 2 retail to DevEd.
The number is 800-757-0280
Click on image,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From Odin Download screen it should say "Mode: Developer"
From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
---------- Post added at 02:22 PM ---------- Previous post was at 02:02 PM ----------
anticloud said:
From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
Click to expand...
Click to collapse
and I can't help but mention - if you happened to use one of the safe upgrades to move forward, there is rollback.
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Frank-95 said:
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Click to expand...
Click to collapse
1.install KIES
2.press tools
3.press frimware upgrade and installation
4.device id is your device model and serial number can be found under battery
5. allow kies to download and install the image
Video link for more help : https://www.youtube.com/watch?v=LqoX7wNhotk
good luck
Edit: please remember to enable OEM unlock in developer options next time
Kies cannot link to the device in the downlaod mode unfortunetely
Frank-95 said:
Kies cannot link to the device in the downlaod mode unfortunetely
Click to expand...
Click to collapse
try using smartswitch and see if it detects it
-are drivers installed
-does the pc recognize the phone ?
So, I had already tried with Smartswitch, but it says device not supported and does not link at all.
Moreover yes, the computer could read the phone before the frp lock, and even now, odin can detect it in download mode.
Kies just loads for some minutes and then says "unable to link to the device"
EDIT: no sorry kies raises "the device does not respond"
ok we need to flash using odin , i assume you can't access recovery but if you tried and it worked, look at the top of the screen it must show a code like
<your A3 model> followed by <your country> followed by <frimware date>
If you couldnt, we can use an updated version for your model , please provide us with the model if u can.
I can only acces to odin mode. Via that, I have the following text:
Product name is: SM-A310F
Current binary: Custom (it was rooted)
System status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: 1
RP SWREV: B:2 K:0 S:0
I am sure that the phone had Vodafone pre-installed applications, and looking at mrcrab.net there exist these possible stock firmware:
Android 5
Android 5
Android 6
Android 6
I only fear that if I mistaken the version I will obtain a wipe of my data, which are not vital but are important to me
Actually there is no way to avoid the reset as we don't know anything about the PDA version, install the drivers type in google "USB Samsung drivers"
It must show developer.Samsung.com/....
I'm on phone so I can't provide it as a link, install the drivers and try again, else we will get the latest version
I already have samsung usb drivers, and odin can succesfully detect the phone in download mode; Kies cannot, though
Anyway, if you open one of the links I posted, isn't the PDA shown in the line:
OS Version : A310FXXU1AOLE (chosen one as example)
In that website there is every stock firmware by model, android version, and mobile operator. I know two out of three, and those 4 links are the 4 possible choices regarding android version. If I picked the right one, would I avoid the data reset, wouldn't I?
EDIT: What, if I did how it is explained here with the latest version? I mean download android 6 last upgrade, extract it, rename .tar.md5 in .tar and flah it with odin? Would it be any risk of loosing data?
Hello,
.MD5 lets odin checksum the rom loaded to it to make sure it's not corrupted, however if you are sure of two main things:
that the frimware you are flashing isn't a downgrade as downgrading flashs a old bootloader which gets you in some kind of troubles possibly a brick, to avoid that, grab the latest version
and the second thing you must make sure of is that the file isn't anyway corrupted.
if you think it's all ok, then you can proceed as of i tried it once and it saved a device.
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Frank-95 said:
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Click to expand...
Click to collapse
The build number must be the same regarding the android version, so to keep the files it must be the same as the one in the phone, else a wipe will be performed.
The problem is that you want your data, that maybe lost if we don't have the exact same build.
Just grab the latest marshmallow or nougat -, but the data would be lost then.
Do a hard reset in case something went wrong.
I was able to unlock the phone a mantain the data! Thanks
I have a special problem with an old Samsung Galaxy A3 2016 SM-A310F (Android 7.0 Nougat)
on which the correct combined file cannot be obtained
I have tried perhaps all FRP removal options without success
A310FXXS5CSH3
It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks
Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.
Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.
Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).
relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.
ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.
The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.
Recently my relative purchased used S20 Ultra 5G (Region SKZ). After the factory reset the phone is locked on FRP . I am not able to get in touch the person from whom my uncle bought the phone.
I could have approached official Samsung gallery but since the phone is used there no invoice nor the guy who sold provide original one. Now stucked in hard place and dont know what to do.
However I did following things as a way around.
1. Used frp hijacker by hagard tool but since the model is new one there is no frp support for s20 ultra in that.
2. Used Samfirm to open browser method but no luck there either the Tool is not able to Open browser event action .It is failing.
3. Did try to capture screen shot way too but new updates are blocking to take screenshot.
4.Tried to flash combination file with pit file but getting 'Please get approval for binary files (bootloader). --this is most success way but kinda stucked at this step.
Not sure what can be done..
Please share if any way around on latest security update on FRP.
PDA : G988BXXU5BTJ3 currently installed. let me know if any other details required.
dhirajp3003 said:
Recently my relative purchased used S20 Ultra 5G (Region SKZ). After the factory reset the phone is locked on FRP . I am not able to get in touch the person from whom my uncle bought the phone.
I could have approached official Samsung gallery but since the phone is used there no invoice nor the guy who sold provide original one. Now stucked in hard place and dont know what to do.
However I did following things as a way around.
1. Used frp hijacker by hagard tool but since the model is new one there is no frp support for s20 ultra in that.
2. Used Samfirm to open browser method but no luck there either the Tool is not able to Open browser event action .It is failing.
3. Did try to capture screen shot way too but new updates are blocking to take screenshot.
4.Tried to flash combination file with pit file but getting 'Please get approval for binary files (bootloader). --this is most success way but kinda stucked at this step.
Not sure what can be done..
Please share if any way around on latest security update on FRP.
PDA : G988BXXU5BTJ3 currently installed. let me know if any other details required.
Click to expand...
Click to collapse
Did you try the @ method?
Edit; nvm, it is an old method.
Did you flash full firmware? Idk if that matters...
twismo1 said:
Did you try the @ method? -- which method?
Edit; nvm, it is an old method.
Did you flash full firmware? Idk if that matters...
-- this is will not solve tried this also
Click to expand...
Click to collapse
I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!
I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
i need fastboot driver for win 64
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?