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
Hey XDA, I haven't been on here since my Samsung S2 years ago. I picked up a new moto Z for daydream, (amazon 499 special, 64 gb luna grey unlocked, retus software, 650-03). I bought it from the american amazon, and I am in canada. I popped in my Sasktel sim card and it works perfectly.
My questions are:
How do I manually flash nougat?
If I flash to the rogers 45 firmware, will I still be able to use my Sasktel sim?
How long until nougat comes out regardless? Should I just wait?
If I do flash to this "rogers 45 nougat", can I go back to my "vanilla" stock later? ( i just want daydream now, i bought the headset already. then when my area gets nougat, ill flash back to my phones nougat.. or does it make a difference?)
Sorry for the really random questions. I couldn't find the answers to these on the forums or on google. (reddit has been saying just wait, and don't flash)
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
pixelens said:
...
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
enetec said:
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
Click to expand...
Click to collapse
Going to start a new thread so as not to hijack this one
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own - opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Yes very good tutorial, I really likes to write something like this but I'm not good in English
Thanks again
erfanoabdi said:
...
Thanks again
Click to expand...
Click to collapse
Ahahahaha, this is only "chatting" in not-so-good-English ... :laugh:
Thanx for you *great* development here instead! :highfive:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Wow! Thank you for the response! This answered pretty much all of my questions, but also sparked a few more. The Moto Z was a pretty big purchase for me so I am in no hurry to lose functionality. A lot of people are using translators on here, so I'll be simple (sorry if it comes off as blunt or rude, typing with translators in mind)
I want to stay on android 7. Downgrading to 6.0 is not a worry for me.
I want to get future updates from my carrier. (official android/moto updates and security patches. I want to be able to use the "Google Tango" mod, if it comes out)
I want to be able to use the projector mod and daydream.
I do not plan on rooting my phone (maybe later), and I do not want to unlock my bootloader.
Will the retmx nougat be different then the copy of nougat I would get from retus?
Finally, is there any benefit to waiting for the OTA? Or am I getting the exact same copy of nougat on XDA, that I would in three weeks from OTA? I already bought the daydream headset, am I waiting for nothing?
*two more questions I guess*
Do I need a SD card?
do I need to unlock my bootloader to do this upgrade?
( http://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095)
(http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245)
Sorry for all the questions. I have looked all over XDA and haven't been able to find an answer (reddit, and google too :/). I am hoping that other people will be able to read this, and have their questions answered as well.
Again, thank you. You guys are really smart.
pixelens said:
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Porcelainfog said:
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Click to expand...
Click to collapse
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Based on your expressed needs... I'll just wait your OTA. Nothing more. It's only a matter of weeks anyway...
Sorry for being a newb and asking here but I'm finding it difficult to get my head around this.
I was originally on MM and upgraded to Nougat on unlocked I international Moto Z.
I then decided to install TWRP, root and try a new ROM. If I want to go back to stock Nougat can't it just be a case of flashing the Nougat update I have download on my computer through ODIN or is it going to be a little more complex than that?
Thanks for any help
pixelens said:
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Click to expand...
Click to collapse
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Porcelainfog said:
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Click to expand...
Click to collapse
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
pixelens said:
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
Click to expand...
Click to collapse
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Dawnhawk said:
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Click to expand...
Click to collapse
LOL, of course they did!
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
Porcelainfog said:
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Click to expand...
Click to collapse
Cool. And ya re ADB haha
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
You could just test the code in fastboot: fastboot oem unlock UNLOCKCODE
If the code is incorrect, for some reason, it will say Password incorrect. Else it will bring you to the yes/no unlock screen on phone. DCs unlock code should always work as it doesn't need the correct imei/imei2/sn/product combo when generating unlock code.
There's no real point in staying on xloader 01 anymore, every update (except a few unapproved firmware) after 02 started appearing has been 02.
Downside is that you can't downgrade, but you could replace fastboot in latest fw with the one from may/June and you'd have DC working again. But there's also service firmware available for free on androidhost.ru which can be used if phone should brick. There's also testpoint (only one person has tested this) which can be used to downgrade to any firmware (even xloader 02 to 01).
Before unlocking, backup everything as unlocking will wipe data.
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
ums1405 said:
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
Click to expand...
Click to collapse
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
debbuger said:
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Click to expand...
Click to collapse
Thanks, that's worth the entrance fee alone as they say.
Pretoriano80 said:
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
Click to expand...
Click to collapse
Thank you for taking the time to put me right.
I'll go back to your Unofficial TWRP post and go through it A to Z.
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
ums1405 said:
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
Click to expand...
Click to collapse
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
ums1405 said:
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
Click to expand...
Click to collapse
Well, you can't stay on xloader01 forever, at least not if you want to update your device.
The cons is that once on xloader02, you can't go back to xloader01.
Pretoriano80 said:
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Click to expand...
Click to collapse
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
ums1405 said:
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
Click to expand...
Click to collapse
All except userdata, system and vendor (these are large and can be found on stock firmwares, so can be skipped).
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
ums1405 said:
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
Click to expand...
Click to collapse
You can use HWOTA8 or HuRUpdater! Beware that if you update to a firmware with patch 01, simply flashing Magisk won't work anymore and you will have to patch the stock ramdisk with Magisk Manage (keep encryption and preserve dm_verity must be enabled) , then flash the patched image with fastboot.
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 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...)