I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
I also have the Samsung A21 from T Mobile (SM-A21UZKATMB). The phone is unlocked by T Mobile but there is no OEM bootloader unlock button under the Developer mode. Changing the date (forward and backward in time), then run the software update did not solve the OEM bootloader unlock button problem. I suspect the carrier (T Mobile) has disabled this function. You will need to unlock the bootloader to install the stock firmware.
To those who have enabled the OEM bootloader in the A21. Is your phone locked to a carrier in the USA like Verizon or T Mobile?
I also have the SM215DL, using straight talk utilizing verizon service, I also cannot unlock the bootloader. Everything you guys did, I did. Nothing worked.
samsung has done this to all A series phones intended for the U.S. from what i understand
Where there's a will, there's a way... someone has messed with my phone too do doesn't that mean that they're altering the data/data partition to r/w. Did you guys try fastboot flashing unlock vs. fastboot oem unlock. I'm going to contact Samsung about this and let u all know what's up.
And also why would there be a usb debugging port if this phone can't be modded? Idon't know the answer but maybe someone more expediency could come in and help us out. I also wonder if the flash_image command or just dd it would bypass it?
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
MaBo2020 said:
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
Click to expand...
Click to collapse
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
thatha said:
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
Click to expand...
Click to collapse
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
MaBo2020 said:
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
Click to expand...
Click to collapse
Extract boot.img from AP.tar, then use modified-magisk to patched it
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
And this is my U5 patched boot.img
MaBo2020 said:
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
Click to expand...
Click to collapse
I have just made a post here, you can try it
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
... and u shure, it its for the A21s or for A21 ?
The only hope of getting root on this phone is if you find a Dev who's interested enough to build a bootstrap recovery. I've not looked at the firmware & have no idea if there's an exploit that would work for that purpose.
Bootstrap recovery was the only way of getting root/custom recovery back in the days of Motorola D2 & Droid X, the original Droid X. Motorola was THE phone for development... Liberty ROM, Gummy ROM, Simply Stunning, etc.
I would not hold out hopes for that to happen here.
Peace - MS
Seriousfreedom said:
samsung has done this to all A series phones intended for the U.S. from what i understand
Click to expand...
Click to collapse
No, Samsung has done this to ALL North American models ever since the Galaxy S8. The bootloaders are not user-unlockable, like they are on international models. However, some models can be rooted via a software exploit if they're running very old firmware, or some models can even be bootloader unlocked via special files, if their firmware version is old enough
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
Mine is rooted. But you have to buy a token.
o.class.jav said:
Mine is rooted. But you have to buy a token.
Click to expand...
Click to collapse
what token??
[email protected] said:
what token??
Click to expand...
Click to collapse
The one generated by the SamPwns steady.bin flash.
{Mod edit: Quoted post removed}
and where does one get 'TWRP' for the Samsung Galaxy A21S?? Thanks for the post its very detailed with very clear instructions, and i agree with you this is the tried and tested and perfect way of rooting your phone, only problem is that this is an unperect world a world where 'TWRP' for the SM-A217F does not exist
I just received a refurbished SM-S215DL (A21,) not as my provider's solution to the VoLTE soon to be required for 4G devices thing and right now it's a pretty severe downgrade for me since it lacks a lot of basic functionality I'm used to from my 2017 phone running LineageOS. Obviously it's pretty unlikely or probably outright impossible to ever see a real LineageOS ROM for this thing (and even if someone ever does it probably would be insanely unstable or incomplete,) but if I could at least root it (even if I have to manually patch or something) it would really help me out a lot. Has just nothing really been found short of sending some unknown person online some very very key device details and money (which I don't have or I'd be buying something else anyway)? (Also kind of suspicious that whatever method they're using isn't something available to the public anyway...)
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.
Hello, everyone. Im pretty new to all of this stuff so please bear with me. I was trying to root an old phone and as I learned more and more about rooting processes (wanting to use majisk) I realised the particular phone (SM-J737R4) is a crackhead and not a lot of stuff is available for it. Anyways I saw that someone with the same model was able to do it using this thread even though it's for a different model. But to use this guide I needed to have android 8.0 and when I got the phone it already had 9.0. I knew downgrading via Odin was possible on samsungs but when I tried googling the Stock firmware the baseband version for the 8.0 downloads were always different. Current Baseband: J737R4TYS8BTE1. And apparently trying to flash a stock firmware that doesnt exactly match your device bricks your phone, so I'm kinda confused on what to do next. And I may be confused on other things as well. Hopefully someone can help.
Tl;Dr: Trying to flash back to 8.0 from 9.0 on SM-J737R4 but stock firmware downloads dont match device.
Any Samsung device what comes with unlocked boot-loader - or whose boot-loader can get unlocked - can easily get rooted. Rooting a phone's Android doesn't depend on Android version.
jwoegerbauer said:
Any Samsung device what comes with unlocked boot-loader - or whose boot-loader can get unlocked - can easily get rooted. Rooting a phone's Android doesn't depend on Android version.
Click to expand...
Click to collapse
yeah but when I was trying to root with majisk the flash failed and when I looked up a TWRP one didnt exist for this model. The forum was a twrp for my model, but it was made for 8.0.
danalexcoro said:
yeah but when I was trying to root with majisk the flash failed and when I looked up a TWRP one didnt exist for this model. The forum was a twrp for my model, but it was made for 8.0.
Click to expand...
Click to collapse
TWRP is a Custom Recovery used to flash a Custom ROM. Installing TWRP prevents Android to receive OTA updates.
You don't need TWRP, but only the "Magisk Manager" app to root phone's Android.. And, of course phone's boot-loader must got unlocked before.
By means of "Magisk Manager" you create a patched boot.img what you then flash via "ODIN" what requires you have installed latest Samsung USB drivers on Windows computer.
Important: The "patched_boot.img" comes in .ZIP-file format. You have to convert it into .TAR-file format using Windows app "7ZIP" before you can use it with "ODIN".
Load .TAR-file into ODIN's AP-section, flash it.
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
I got it to fastboot mode, but there's no boot image for 11.0.0 available, right? Please help
Is it T-Mobile version or unlocked?
There's MSM tool for T-Mobile version and you can download full ROM for unlocked
If yours is unlocked and you can access recovery, use sideload
Code:
adb sideload
Press spacebar once and drag and drop the ROM onto command window and press enter
This can fix boot as well as making version update
bouyakasha said:
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
Click to expand...
Click to collapse
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
amboyscout said:
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
Click to expand...
Click to collapse
wow .. please upload it to google drive or mega (dot) nz and post the link here .... honestly this gets me very excited ...
mingkee said:
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
Click to expand...
Click to collapse
my bootloader is locked .. thats why MSMDownload tool is a must
edale1 said:
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
Click to expand...
Click to collapse
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a maual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Dimitrimem said:
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
Click to expand...
Click to collapse
If you use the "+ Quote" button, rather than the reply button, it'll create a multiquote, letting you quote and reply to multiple posts all at once (it'll add a "insert quotes" button to the reply box). This eliminates double-posts, which most forums frown upon.
@Dimitrimem here ya go https://drive.google.com/drive/folders/1DzR0uEdyFeBeID4sVaT96z0Y88sMaomL?usp=sharing
Dimitrimem said:
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
Click to expand...
Click to collapse
Tried this today. Now waiting on OnePlus to respond.
bouyakasha said:
Tried this today. Now waiting on OnePlus to respond.
Click to expand...
Click to collapse
Don't wait to long for their reply .. if they don't answer call them on the phone.. it takes less than a minute to have them speak with you ... I dragged it for too long with them waiting 7 days to send me a shipping label than another 5 for another try at it .. another 4 to get the link for download ..after all that they said they don't have it... but this was a while back ... I'd be on that phone fast.. tell them you need your phone as it's the only one ... honestly if you can get the msm tool it would be amazing
mingkee said:
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a manual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Click to expand...
Click to collapse
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
darkghost568 said:
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
Click to expand...
Click to collapse
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
mingkee said:
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
Click to expand...
Click to collapse
Ok so now I'm stuck here as well (saw your comment in the other thread):
mingkee said:
I attempted to flash unlocked ROM on bootloader unlocked T-Mobile version phone
It stuck on products.img. The error stated "not enough space for the partition"
What happened?
Click to expand...
Click to collapse
Any luck getting past this?
darkghost568 said:
Ok so now I'm stuck here as well (saw your comment in the other thread):
Any luck getting past this?
Click to expand...
Click to collapse
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Towards the bottom of that post it talks about getting past that error.
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.