Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Damn i have the same issue with the Note8, lez hope that soemone ansers that cuz reinstalling the Stock dosent help with this when try to install TWRP
NikitaSav said:
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Click to expand...
Click to collapse
Did you install smasung multi disabler?
DavidxxxD said:
Did you install smasung multi disabler?
Click to expand...
Click to collapse
oh no **** guess im just dumby ^_°
DavidxxxD said:
Did you install smasung multi disabler?
Click to expand...
Click to collapse
tho crap how im supposed to install it? odin dosent want it and i cant use since ivent got TWRP on it wich i can not install because it says, as u guesst: Only official binaries can be installed no matter WHAT I DO -.- hate samsung by now
NikitaSav said:
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Click to expand...
Click to collapse
And this version of Odin? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
joke19 said:
А эта версия Одина? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Click to expand...
Click to collapse
I have RMM Prenormal
C7TJFVB7-CAZ said:
hate samsung by now
Click to expand...
Click to collapse
Same here, reinstalling full stock should fix it. Also try combiation firmware if that doesn't work. Does your device have a vbmeta partition?
DavidxxxD said:
Same here, reinstalling full stock should fix it. Also try combiation firmware if that doesn't work. Does your device have a vbmeta partition?
Click to expand...
Click to collapse
combination file not working on Binary 8/9 on Samsung Galaxy J4
I've had the same issue on a J330F after Android 9 update - tried to modify, got stuck in the same red text. I don't remember any info from odin mode, but It booted fine again after flashing the same version over it. Though I had to wait 24 hours before trying to modify again. Not sure what's going on in your case, but Samsung security can be real pain, that's for sure.
I wouldn't get any of their newer models to mess around with, compatibility is good and there are reliable methods, but generally everything works better on more generic Qualcomm devices. Just take a look at most MSM845 devices from around 2019 - big diffrence in terms of compatibilty, many of them are supported by newer versions of Linux than what is included with Android, some can even boot Windows 11.
DavidxxxD said:
I've had the same issue on a J330F after Android 9 update - tried to modify, got stuck in the same red text. I don't remember any info from odin mode, but It booted fine again after flashing the same version over it. Though I had to wait 24 hours before trying to modify again. Not sure what's going on in your case, but Samsung security can be real pain, that's for sure.
I wouldn't get any of their newer models to mess around with, compatibility is good and there are reliable methods, but generally everything works better on more generic Qualcomm devices. Just take a look at most MSM845 devices from around 2019 - big diffrence in terms of compatibilty, many of them are supported by newer versions of Linux than what is included with Android, some can even boot Windows 11.
Click to expand...
Click to collapse
I have Android 10
I try all, that i can to try
Same problem
After unlocking your bootloader, you have to allow your device to boot again:
Helix-one said:
I AM NOT RESPONSIBLE FOR ANY DAMAGES DONE BY YOUR MISHAPS
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some cirumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Voila! Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
After flashing TWRP, you may need to wipe data and flash Multidisabler
V0latyle said:
After unlocking your bootloader, you have to allow your device to boot again:
After flashing TWRP, you may need to wipe data and flash Multidisabler
Click to expand...
Click to collapse
I cant even flash TWRP
Kgstate said:
I cant even flash TWRP
Click to expand...
Click to collapse
When you're in Download Mode, look for something that says "KG: Checking". If this says "Prenormal" you won't be able to flash custom binaries, and need to do as I described - boot the device, connect to the Internet, wait for the OEM unlocking toggle to become visible again.
V0latyle said:
When you're in Download Mode, look for something that says "KG: Checking". If this says "Prenormal" you won't be able to flash custom binaries, and need to do as I described - boot the device, connect to the Internet, wait for the OEM unlocking toggle to become visible again.
Click to expand...
Click to collapse
Editing date to make it 7 days later and Connecting the internet just worked, thank you for your help!
Related
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
UPDATE 17.06.2019 - NEW RMM/KG bypass patch
UPDATE 23.02.2019 - Pie and more
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about this guide!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Flashing any custom binary will trigger knox and you may lose your warranty. Make sure you know what you do to your device.
Introduction
December 2017 update (for some even older) brought us a different lock, that creates panic among users as usual. As described here by my friend @BlackMesa123, this is not a lock to developement, rather an advanced lock for theft or scams. This has a bypass too, specially when you`re the owner of the device.
How it works
This lock is in bootloader, but the trigger to it is inside the system, it`s hard to reproduce, but usually happens when you plug another country sim than your firmware country, because changing the country might not seem as a traveling guy and more like a thief. If you are on stock rom all this time, you might not feel the change, as the device reboots and wipes data, but it will eventually boot. The nice thing comes if you already have custom binary installed (rooted kernel or twrp), as you can`t boot anymore because bootloader is preventing you to boot on custom binaries and alter the system.
Devices confirmed to have the lock:
Any other Samsung device manufactured after 2017
Samsung Galaxy S9 & S9+ - SM-G960F & SM-G965F
Samsung Galaxy Note 8 - SM-N950F
Samsung Galaxy S8 & S8+ - SM-G950F & SM-G955F
Samsung Galaxy A8 & A8+(2018) - SM-A530F & SM-A730F
Samsung Galaxy A Series (2017) - SM-A320F/FL, SM-A520F & SM-A720F
Samsung Galaxy Note FE - N935F
How to know if you are locked
There are 3 things at this chapter:
1. "Only official released binaries are allowed to be flashed" message shows up and now you know for sure you got locked outside your phone
2. Missing OEM unlock toggle in developer settings, if your device has FRP
3. "RMM state = Prenormal" in download mode
How to unlock
1. As i personally did, and other users reported, if you face any of the things above, flash latest full stock fw of your country with Odin, boot up, don`t reboot, don`t unplug the sim and don`t disconnect the network connection for 7 full days (168h). It seems that after 7 days of uptime, RMM state resets and you can flash TWRP again without issues. You can see uptime in settings/about device/status.
2. Some users reported this guide was working in first Oreo fw releases, can't guarantee it still works.
How to avoid getting locked again
Unfortunately bootloader can`t be reverted to older revisions, so we need to live with this. My friend @BlackMesa123 made some investigation and found out how to disable this lock. After waiting those 7 days, go to settings/developer option and enable OEM unlock. In order to never get locked again, flash TWRP for your device (install instructions below), boot into TWRP (do not boot into rom yet as you might get locked again), download and flash his fix from here (don`t forget to thank him too for his findings).
You can keep this zip near and flash it after flashing any custom rom, to be sure you don`t get locked again. The zip contains an universal script that disables the services responsable. Can be flashed on any device, if the device has the lock, won`t get locked again, if not, nothing will happend. I like to say "better safe than sorry".
How to safely install TWRP
Considering you are already unlocked (waited those 7 days), follow the next steps carefully:
Make sure you downloaded latest Odin, samsung usb drivers installed, latest RMM-State_Bypass fix (download links are in #2 post) and latest TWRP available for your device
Put RMM-State_Bypass.zip in external sdcard
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Reboot the phone into download mode and connect the usb cable
Open Odin, go into options and untick Auto-reboot and put the TWRP tar file in AP tab of odin, hit Start and wait
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip
Now you can reboot into rom and hopefully never get locked again.
If any of above steps fail, redo from step 1, more carefully this time.
How to safely root
Considering you already unlocked (waited those 7 days) and you have TWRP installed, follow the next steps carefully:
Download root zip and no-verity-opt-encrypt-6.0 (download links are in #2 post) and drop the zips into external sdcard
Boot into TWRP and swipe "Allow modifications"
Go into Wipe menu and select "Format data" - note that this will erase all your data including internal storage
Reboot recovery, swipe to "Allow modification" and flash RMM-State_Bypass.zip
Flash no-verity-opt-encrypt-6.0 zip downloaded at step #1 to disable data partition encryption
Flash root zip downloaded at step #1
Reboot the phone into system
After booting up in setting wizard make sure to uncheck diagnostic data
If any of above steps fail, redo from step 1, more carefully this time.
You can read more about it here here, here, here, here or here.
Credits
@BlackMesa123
@RicePlay33
@Yahia Angelo
@TaifAljaloo
@ananjaser1211
Useful links
Samsung Firmware download - Updato / Sammobile / Samsung-Firmware.org / Samsung-Updates.com
Samsung Usb Drivers
Odin 3.13.1
Latest SuperSU stable or test/beta
Latest Magisk stable or test/beta
NEW-RMM-State_Bypass
no-verity-opt-encrypt-6.0
FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes?
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
{
"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"
}
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: Why not formatting data at twrp install?
A: Phone will boot even if data is encrypted if you don't root. Also system partition is not encrypted meaning you can flash RMM-State_Bypass anyway.
corsicanu said:
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
Click to expand...
Click to collapse
Awesome guide corsi this needs to get around.
Awesome guide from best team
I miss you all
Sent from my SM-G950F using Tapatalk
You need to tag mee also @aelle89 aka cloud569 :laugh:
after long days of waiting i can flashed custom recovery.... then i flashed no-verity-no-encrypt and RRM-state_baypass....then i restored my backup custom rom...the problem is can’t detect my simcard..and sometimes my device lag then reboot itself specially if my wifi is on...how can i fix that?
kobejor said:
after long days of waiting i can flashed custom recovery.... then i flashed no-verity-no-encrypt and RRM-state_baypass....then i restored my backup custom rom...the problem is can’t detect my simcard..and sometimes my device lag then reboot itself specially if my wifi is on...how can i fix that?
Click to expand...
Click to collapse
Same situation mate. You have solution?
DaniPS2002 said:
Same situation mate. You have solution?
Click to expand...
Click to collapse
Now i flashed stock rom via Odin then after quick to download mode again and flashed twrp... it's successful ....and I didn't flash no-verity and RRM_bypass... I flashed magisk but failed...then flashed superu .. it's fine after reboot stack to a5 logo then back to twrp... no OS installed...so I restored my backup custom rom... no Lag so far...but my simcard still not detect
kobejor said:
after long days of waiting i can flashed custom recovery.... then i flashed no-verity-no-encrypt and RRM-state_baypass....then i restored my backup custom rom...the problem is can’t detect my simcard..and sometimes my device lag then reboot itself specially if my wifi is on...how can i fix that?
Click to expand...
Click to collapse
DaniPS2002 said:
Same situation mate. You have solution?
Click to expand...
Click to collapse
kobejor said:
Now i flashed stock rom via Odin then after quick to download mode again and flashed twrp... it's successful ....and I didn't flash no-verity and RRM_bypass... I flashed magisk but failed...then flashed superu .. it's fine after reboot stack to a5 logo then back to twrp... no OS installed...so I restored my backup custom rom... no Lag so far...but my simcard still not detect
Click to expand...
Click to collapse
Custom rom backup might be the issue. Try to clean flash the rom and see if sim is detected.
Sent from my SM-G955F using Tapatalk
my 168H completed a short time ago and I do not know how to thank you !!!! twrp and root successfully !! great job
Soooooo... Make it clear for me: I have RMM set to 'Prenormal' in Odin mode BUT OEM unlock shows in settings. Now if I wait 7 days, it'll reset and I'll be able to flash TWRP normally?
io_gh0st said:
Soooooo... Make it clear for me: I have RMM set to 'Prenormal' in Odin mode BUT OEM unlock shows in settings. Now if I wait 7 days, it'll reset and I'll be able to flash TWRP normally?
Click to expand...
Click to collapse
Yes. As long as you have RMM state = Prenormal in Odin mode, you can't flash anything custom. Wait 7 days without reboot and you can flash TWRP after that. Cheers!
Sent from my SM-G955F using Tapatalk
kobejor said:
after long days of waiting i can flashed custom recovery.... then i flashed no-verity-no-encrypt and RRM-state_baypass....then i restored my backup custom rom...the problem is can’t detect my simcard..and sometimes my device lag then reboot itself specially if my wifi is on...how can i fix that?
Click to expand...
Click to collapse
So you truly have to wait 7 days for this to work?
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
corsicanu said:
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this guide! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Flashing any custom binary might trigger knox and you will lose your warranty. Make sure you know what you do to your device.
Introduction
December update (for some even older) brought us a different lock, that creates panic among users as usual. As described here by my friend @BlackMesa123, this is not a lock to developement, rather an advanced lock for theft or scams. This has a bypass too, specially when you`re the owner of the device.
How it works
This lock is in bootloader, but the trigger to it is inside the system, it`s hard to reproduce, but usually happens when you plug another country sim than your firmware country, because changing the country might not seem as a traveling guy and more like a thief. If you are on stock rom all this time, you might not feel the change, as the device reboots and wipes data, but it will eventually boot. The nice thing comes if you already have custom binary installed (rooted kernel or twrp), as you can`t boot anymore because bootloader is preventing you to boot on custom binaries and alter the system.
How to know if your device has the lock
Well, for sure we know N935F, N950F, A520F, A720F, A530F, A730F have the lock. I assume that every other device that has FRP and gets updated might have this too. Will update the list as soon as i find out of other devices.
How to know if you are locked
There are 3 things at this chapter:
1. "Only official released binaries are allowed to be flashed" message shows up and now you know for sure you got locked outside your phone
2. Missing OEM unlock toggle in developer settings, if your device has FRP
3. "RMM state = Prenormal" inside download mode
How to unlock
As i personally did, and other users reported, if you face any of the things above, flash latest full stock fw of your country with Odin, boot up, don`t reboot, don`t unplug the sim and don`t disconnect the network connection for 7 full days (168h). It seems that after 7 days of uptime, RMM state resets and you can flash twrp again without issues. You can see uptime in settings/about device/status.
How to avoid getting locked again
Unfortunately bootloader can`t be reverted to older revisions, so we need to live with this. My friend @BlackMesa123 made some investigation and found out how to disable this lock. After waiting those 7 days, go to settings/developer option and enable OEM unlock. In order to never get locked again, flash custom recovery for your device, boot into it (do not boot into rom yet as you might get locked again), download and flash his fix from here (don`t forget to thank him too for his findings). You can keep this zip near and flash it after flashing any custom rom, to be sure you don`t get locked again. The zip contains an universal script that disables the services responsable. Can be flashed on any device, if the device has the lock, won`t get locked again, if not, nothing will happend. I like to say "better safe than sorry". About rooting, as you might already know, Nougat encrypts data, so if you root, you need to format data partition. This will lead in data loss, make sure you have a backup before trying to root, make sure you know what you do (more info here).
You can read about it here, here, here, here or here.
Credits
@BlackMesa123
@RicePlay33
@Yahia Angelo
@ananjaser1211
Click to expand...
Click to collapse
So I have to leave my phone home when I live for school for 7 days?
corsicanu said:
Custom rom backup might be the issue. Try to clean flash the rom and see if sim is detected.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
even i flashed the custom rom again,it is not detected. if i on wifi my device started lagging and after that it’s reboot itself....
Required files
So the files needed to load TWRP and then root are the same only you have to wait for 7 days to try again?
A5Y17LTE_EUR_OPEN.pit
AP_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
BL_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
CP_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
HOME_CSC_PHE_A520FPHE2AQF1_CL10911830_QB13837656_REV00_user_low_ship.tar.md5
CSC_PHE_A520FPHE2AQF1_CL10911830_QB13837656_REV00_user_low_ship.tar.md5
Spain free version P.H.E
Odin3-v3.12.7
A5⑦-SM-A520F-TWRP-3.0.2.0 .tar
UPDATE-SuperSU-v2.76-20160630161323
I have another variant but it does not let me upload files, where is the option?
corsicanu said:
Yes. As long as you have RMM state = Prenormal in Odin mode, you can't flash anything custom. Wait 7 days without reboot and you can flash TWRP after that. Cheers!
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Interesting. I'll wait and try. It works on the January patch, right? Maybe this will work on Oreo too?
Thank You
Thank you for this!! Much needed. I'm glad you pointed the scenarios, the clues and how to make sure what's the devices current state which is important before rooting.
Now I feel safe to root my A520F. I have a question: after root, doing stuff like flashing xposed or removing apps from system trigger any weird behaviors?
stii said:
So the files needed to load TWRP and then root are the same only you have to wait for 7 days to try again?
A5Y17LTE_EUR_OPEN.pit
AP_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
BL_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
CP_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
CSC_PHE_A520FPHE2AQF1_CL10911830_QB13837656_REV00_user_low_ship.tar.md5
CSC_PHE_A520FPHE2AQF1_CL10911830_QB13837656_REV00_user_low_ship.tar.md5
Spain free version P.H.E
Odin3-v3.12.7
A5⑦-SM-A520F-TWRP-3.0.2.0 .tar
UPDATE-SuperSU-v2.76-20160630161323
I have another variant but it does not let me upload files, where is the option?
Click to expand...
Click to collapse
does the method root work for A5 2017 with january security patch? Or can i downgrade marshmllow my A5 2017? Can you give me a guide for downgrade please. and can you upload the file please
ps : sorry for my bad english
Amazing guide corsi sar. Appreciated it
sawas.t01 said:
So you truly have to wait 7 days for this to work?
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
So I have to leave my phone home when I live for school for 7 days?
Click to expand...
Click to collapse
You can use your phone, just don't reboot it for 7 days.
kobejor said:
even i flashed the custom rom again,it is not detected. if i on wifi my device started lagging and after that it’s reboot itself....
Click to expand...
Click to collapse
Try to report the issue to the rom developer. If you follow all the instruction with stock rom, all works.
stii said:
So the files needed to load TWRP and then root are the same only you have to wait for 7 days to try again?
A5Y17LTE_EUR_OPEN.pit
AP_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
BL_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
CP_A520FXXS2AQF2_CL10911830_QB13837964_REV00_user_low_ship.tar.md5
CSC_PHE_A520FPHE2AQF1_CL10911830_QB13837656_REV00_user_low_ship.tar.md5
CSC_PHE_A520FPHE2AQF1_CL10911830_QB13837656_REV00_user_low_ship.tar.md5
Spain free version P.H.E
Odin3-v3.12.7
A5⑦-SM-A520F-TWRP-3.0.2.0 .tar
UPDATE-SuperSU-v2.76-20160630161323
I have another variant but it does not let me upload files, where is the option?
Click to expand...
Click to collapse
You need to flash latest 7.0 fw available for your region, wait 7 days without reboot if you have the RMM state in download mode, go in download, flash twrp, in twrp go to wipe-format data, flash no encrypt patch, flash your root option, flash RMM fix zip, boot, setup, profit. The files you posted above are marshmallow, you can flash that too, but it might have different behaviour. Better keep it on 7.0 to avoid other issues.
io_gh0st said:
Interesting. I'll wait and try. It works on the January patch, right? Maybe this will work on Oreo too?
Click to expand...
Click to collapse
Works on all so far. Hopefully will work for Oreo too.
MagnoT said:
Thank you for this!! Much needed. I'm glad you pointed the scenarios, the clues and how to make sure what's the devices current state which is important before rooting.
Now I feel safe to root my A520F. I have a question: after root, doing stuff like flashing xposed or removing apps from system trigger any weird behaviors?
Click to expand...
Click to collapse
As long as you flash the RMM fix zip, all should be ok.
xXxDmCxXx said:
does the method root work for A5 2017 with january security patch? Or can i downgrade marshmllow my A5 2017? Can you give me a guide for downgrade please. and can you upload the file please
ps : sorry for my bad english
Click to expand...
Click to collapse
Yes this works for january too. Even if you downgrade to marshmallow, you can't downgrade the bootloader, so will be useless. I can't give a guide for downgrade as you can't fix the lock with downgrade. What files do you want?
Sent from my SM-G955F using Tapatalk
Hey people,
This is my first post here, so excuse me if I'm posting in the wrong section. Now about the issue - it seems I have fallen into a soft brick boot loop, which happened after upgrading my stock Xiaomi 9T to MIUI 12. There are several factors to this problem, so bear with me.
Phone wasn't modified, ROM wasn't tinkered with
Phone can be turned on as usually, however after displaying Mi logo it shuts down
Fastboot is available
Recovery mode is available
Wiping data with recovery mode stops after 3% and fixes nothing
Bootloader is locked
Developer options are disabled
And here is the worst part:
I can't flash any recovery image (like TWRP) because my bootloader is locked -> I can't unlock my bootloader because developer options are turned off -> I can't turn on developer options because ADB requires root to do so -> I can't operate as root because I can't flash any recovery image
See what I mean? It's also worth mentioning that most of the adb/fastboot commands return errors because of the OEM lock. So I guess my question is "do I go straight to a local Mi Center and ask for help or is it possible to salvage it manually at home?"
@jebacmarcina
Accessing Android's Developer options doesn't require Android got rooted
You must NOT flash a Custom Recovery , you simply boot into it
Phone's Android must NOT be rooted in order to modify / replace its ROM
@jwoegerbauer
When setting Developer Options through ADB I get "Error: closed"
Still can't do that because the device is locked
Maybe I'm misunderstanding things, but if so, could you post a tutorial here or redirect me to one?
@jebacmarcina
As I would do it:
Open MUI12 Settings menu
Goto Additional Settings
Select Developer options
jwoegerbauer said:
@jebacmarcina
As I would do it:
Open MUI12 Settings menu
Goto Additional Settings
Select Developer options
Click to expand...
Click to collapse
At the very beginning I mentioned that I can't turn on my phone, so opening Settings is impossible
jebacmarcina said:
At the very beginning I mentioned that I can't turn on my phone, so opening Settings is impossible
Click to expand...
Click to collapse
Oops, have overseen it. Sorry for this.
My advice: Re-flash Stock ROM.
jwoegerbauer said:
Oops, have overseen it. Sorry for this.
My advice: Re-flash Stock ROM.
Click to expand...
Click to collapse
Tried that too, can't be done when bootloader is locked :/
jebacmarcina said:
Tried that too, can't be done when bootloader is locked :/
Click to expand...
Click to collapse
AFAIK re-flashing phone's Stock ROM ( what in contrast to Custom ROM is digitally signed by OEM/Carrier ) by means of phone's Stock Recovery doesn't require phone's boot-loader is unlocked: a locked boot-loader always loads Stock ROM.
jwoegerbauer said:
AFAIK re-flashing phone's Stock ROM ( what in contrast to Custom ROM is digitally signed by OEM/Carrier ) by means of phone's Stock Recovery doesn't require phone's boot-loader is unlocked: a locked boot-loader always loads Stock ROM.
Click to expand...
Click to collapse
My thoughts exactly; however, when I tried doing that I still got the error "flashing is forbidden in a Locked State" so I decided to send the phone back to customer service. Still, thanks for your help and time.
Thread can be closed.
I have been researching this phone for a bit now and I saw the the a528B/DS was successfully rooted. The issue is I've only seen one in the color I want and I'd like to know if I have any other model options of the same phone (not other phones, I mean A52 5G's with a different configuration or origin which the number reflects.)
If anyone can tell me which models have been successfully rooted, I'd like that.
SM-A526B and SM-A528B can be rooted for sure.
if you can access the firmware to patch it with magisk, it should be rootable!
woffles_ said:
if you can access the firmware to patch it with magisk, it should be rootable!
Click to expand...
Click to collapse
No
In order to even flash patched firmware you need to be able to open bootloader which isn't possible on U.S. models (SM-A526U and SM-A526U1)
ShaDisNX255 said:
No
In order to even flash patched firmware you need to be able to open bootloader which isn't possible on U.S. models (SM-A526U and SM-A526U1)
Click to expand...
Click to collapse
oh damn i didnt know you couldnt even open bootloader on us versions lol.
woffles_ said:
oh damn i didnt know you couldnt even open bootloader on us versions lol.
Click to expand...
Click to collapse
Unfortunately that's the situation with all U.S. phones for years now
Canada calling here: got a A526W .... Can't find the OEM unlock button in developer options, and ODIN just sits at "SetupConnection..." when I try to flash samsung firmware. ODIN shows the blue connectivity thing, but only when the phone is powered on in normal usage, but NOT in download mode...
It does cough this up in ADB .... indicating to me that it SHOULD be possible to OEM unlock, then get on to other things like eventually flashing a GSI or custom rom like LineageOS.
./adb shell getprop ro.oem_unlock_supported ---> returns 1
fuzz500 said:
Canada calling here: got a A526W .... Can't find the OEM unlock button in developer options, and ODIN just sits at "SetupConnection..." when I try to flash samsung firmware. ODIN shows the blue connectivity thing, but only when the phone is powered on in normal usage, but NOT in download mode...
It does cough this up in ADB .... indicating to me that it SHOULD be possible to OEM unlock, then get on to other things like eventually flashing a GSI or custom rom like LineageOS.
./adb shell getprop ro.oem_unlock_supported ---> returns 1
Click to expand...
Click to collapse
Oh yeah I forgot, Canada phones cannot be unlocked either
I am fairly new at this so, allow me to ask, Are you sure?
I am clinging to a last bit of hope that it is possible because of what I read at
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
./adb shell getprop ro.oem_unlock_supported ---> returns 1
I didn't say it would be easy, but it seems to indicate that OEM unlock is possible. No?
fuzz500 said:
I am fairly new at this so, allow me to ask, Are you sure?
I am clinging to a last bit of hope that it is possible because of what I read at
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
./adb shell getprop ro.oem_unlock_supported ---> returns 1
I didn't say it would be easy, but it seems to indicate that OEM unlock is possible. No?
Click to expand...
Click to collapse
To be honest with you, I'm not sure. Recognized developers always say that Samsung phones (both in the U.S. and Canada) can not be unlocked and well, I know the U.S. portion is true but I'm not sure about the Canada portion.
Thanks for your reply. I tried flashing stock Samsung firmware with Odin 3.14 and the latest Samsung USB driver.... if the phone was in Download (ODIN) mode (blue/cyan screen) ... then the ODIN software did NOT show connectivity... but if the phone was in regular usage, then ODIN DID show connectivity, but the flash hung on SetupConnection...
Do you think that this modified recovery that one of the other XDA devs posted
Fastboot for A52 5G
Hi. there is Fastboot recovery to A52 5G Source https://github.com/oli231/Patch-Recovery/tree/fastboot
forum.xda-developers.com
could be used to flash the Samsung stock ROM then possibly I could get the OEM unlock button?
fuzz500 said:
Thanks for your reply. I tried flashing stock Samsung firmware with Odin 3.14 and the latest Samsung USB driver.... if the phone was in Download (ODIN) mode (blue/cyan screen) ... then the ODIN software did NOT show connectivity... but if the phone was in regular usage, then ODIN DID show connectivity, but the flash hung on SetupConnection...
Do you think that this modified recovery that one of the other XDA devs posted
Fastboot for A52 5G
Hi. there is Fastboot recovery to A52 5G Source https://github.com/oli231/Patch-Recovery/tree/fastboot
forum.xda-developers.com
could be used to flash the Samsung stock ROM then possibly I could get the OEM unlock button?
Click to expand...
Click to collapse
No, because in order to flash that recovery posted in that thread you already need BL to be open for the phone to accept that recovery
Ok, I see... without OEM unlock, unlocked, you can't flash of the partitions.
I tried to do a "setprop", but I'm just following design patterns here, to see if I could change the property values directly, but NO did not work.
./adb shell setprop sys.oem_unlock_allowed 1
Failed to set property 'sys.oem_unlock_allowed' to '1'.
See dmesg for error reason
I thought however that I should be able to flash the factory stock versions with ODIN, .... because they're signed (?) ... I'm guessing, but I thought you could basically flash factory firmware on the phone without running into any security measures....
Hmmm.. So if the Canadian version of the phone can't be modded, could you get a model from another country that allows modding, flash the OS, pop in a sim, then USE it in Canada ??
fuzz500 said:
Hmmm.. So if the Canadian version of the phone can't be modded, could you get a model from another country that allows modding, flash the OS, pop in a sim, then USE it in Canada ??
Click to expand...
Click to collapse
It should be possible
Thanks for the input.... I've read you can flash the stock firmware without any unlocking.
ODIN reports connectivity (blue bar) when phone is on in regular use. But when you boot into upload/ODIN mode ( cyan blue screen on the phone)... ODIN does NOT have connectivity... log entry hangs at "SetupConnection..."
Any Idea why I can't flash the Samsung stock firmware with ODIN?
fuzz500 said:
Thanks for the input.... I've read you can flash the stock firmware without any unlocking.
ODIN reports connectivity (blue bar) when phone is on in regular use. But when you boot into upload/ODIN mode ( cyan blue screen on the phone)... ODIN does NOT have connectivity... log entry hangs at "SetupConnection..."
Any Idea why I can't flash the Samsung stock firmware with ODIN?
Click to expand...
Click to collapse
Just make sure you've downloaded the Samsung developer adb drivers
As for Odin not recognizing your phone, sometimes this happens. Just close Odin, try different USB ports, disconnect the phone and reconnect. Sometimes this helps, I get a few issues like this from time to time.