Hello i recently bought a galaxy S7 SM-G930W8 (Canadian / BELL Mobility) and its veen updated to the latest it can which is android 8.0 (oreo) and id really like to root it without havibg to change my stock rom actually id just be glad to get it rooted also the security patch is up2date as of july 1st 2018
The W8 is an exynos model so the bootloader should be unlocked, flash twrp through odin, do a factory reset, reboot to recovery from TWRP itself, flash no-dm-verity zip which should be in your memory card, if you don't have one use mtp in TWRP and copy it to the phone, then install magisk zip and you should be good to go. you can find those two zip files in the forum or just a simple good search.
Did you have any luck rooting the SM-G930W8 on 8.0? I just acquired the Canadian S7 and I'd like to root it, but I know it's different from the American S7's, and all I can find is how to root the Canadian S7 with Nougat.
threehappypenguins said:
Did you have any luck rooting the SM-G930W8 on 8.0? I just acquired the Canadian S7 and I'd like to root it, but I know it's different from the American S7's, and all I can find is how to root the Canadian S7 with Nougat.
Click to expand...
Click to collapse
It doesn't matter which carrier it is, what matters most is the chip and the bootloader, the Canadian variant uses the Exynos soc so the steps are the same just like the international model. Start by unlocking the bootloader and installing a custom recovery, download TWRP for herolte, on your phone enable developer options, then make sure OEM unlock is checked, turn off your phone and boot into Odin, then flash the TWRP image, make sure to uncheck reboot after flash in Odin. Once flashing is done, manually reboot your phone and make sure to enter the recovery mode, do a normal factory reset, the one that asks you to write YES to confirm, then reboot to recovery again, plug your phone to the computer and copy the latest magisk zip then flash it, and that should be it basically.
Salazar33 said:
It doesn't matter which carrier it is, what matters most is the chip and the bootloader, the Canadian variant uses the Exynos soc so the steps are the same just like the international model. Start by unlocking the bootloader and installing a custom recovery, download TWRP for herolte, on your phone enable developer options, then make sure OEM unlock is checked, turn off your phone and boot into Odin, then flash the TWRP image, make sure to uncheck reboot after flash in Odin. Once flashing is done, manually reboot your phone and make sure to enter the recovery mode, do a normal factory reset, the one that asks you to write YES to confirm, then reboot to recovery again, plug your phone to the computer and copy the latest magisk zip then flash it, and that should be it basically.
Click to expand...
Click to collapse
I thought the Canadian variant with Exynos already had an unlocked bootloader? There are already instructions on how to root my exact model, but the assumption is 7.0.
I have rooted other phones before, and sometimes the requirement for a version of Android before rooting is very specific. I have no idea where to start to even verify whether the bootloader is truly unlocked, whether or not I can proceed with rooting despite having a different Android version (in my case, 8.0, not 7.0), etc.
threehappypenguins said:
I thought the Canadian variant with Exynos already had an unlocked bootloader? There are already instructions on how to root my exact model, but the assumption is 7.0.
I have rooted other phones before, and sometimes the requirement for a version of Android before rooting is very specific. I have no idea where to start to even verify whether the bootloader is truly unlocked, whether or not I can proceed with rooting despite having a different Android version (in my case, 8.0, not 7.0), etc.
Click to expand...
Click to collapse
Sorry there, I guess the correct description would be tripping knox rather than unlocking the bootloader, since you're already familiar with the process then I can tell you its totally the same, nougat and oreo aren't different enough for anything to change, allow OEM unlock, install twrp, do a data wipe, reboot to recovery again, install magisk zip and you're good to go. You might need to flash the dm verity bypass before magisk, that's another zip you can download as well.
Related
I am having issues trying to root my Galaxy Note Edge with the following build number:
N915GXXS1DPK2
It has Marshmallow 6.0.1 installed. I try to flash CF root via Odin and it gets to what I think is the last step and fails. I have read a few people saying on other sites that the bootloader needs to be unlocked for it to work and others make no mention of it. I have attempted it several times and have tried using various USB ports but to no avail. Would it be easier trying to flash another ROM in order for it to work and if so, what would I use?
All help would be greatly appreciated.
Sorry if this has been mentioned elsewhere
By the look of it, you got a stock rom, wich provider do you have? I have Telstra for a while now and newer had a locked boot loader,
I'm not sure about the other providers but I believe there BL are not locked either...
to get root on your phone, the best way is, install a custom recovery (preferable TWRP) with Odin, and then flash the latest super su
hingerl said:
By the look of it, you got a stock rom, wich provider do you have? I have Telstra for a while now and newer had a locked boot loader,
I'm not sure about the other providers but I believe there BL are not locked either...
to get root on your phone, the best way is, install a custom recovery (preferable TWRP) with Odin, and then flash the latest super su
Click to expand...
Click to collapse
Yeh I have looked into that but cant seem to locate the right TWRP Flash file. Odin wont recognise ones I have found. Am on Optus
bradles73au said:
Yeh I have looked into that but cant seem to locate the right TWRP Flash file. Odin wont recognise ones I have found. Am on Optus
Click to expand...
Click to collapse
this one worked for me: https://forum.xda-developers.com/note-edge/development/twrp-915fy-915tmo-moment-t3129459
look for your variant, G, get the tar file, not the zip file, if you have problems with the latest version, try V3.0
Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
ben480 said:
Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
Click to expand...
Click to collapse
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Droidriven said:
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
ben480 said:
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
Click to expand...
Click to collapse
I'll explain the "OEM unlock" setting a bit first. The OEM unlock setting does not necessarily unlock your bootloader. On some devices, enabling this setting unlocks bootloader but on most devices it does not actually unlock the bootloader, it only puts the device in a state that the bootloader "can" be unlocked using some form of unlock method after enabling the setting. In these cases, the unlock method would not work without enabling OEM unlock setting before implementing the unlock method.
So, basically, what I'm saying is that even though you have the OEM unlock setting, this does not necessarily mean that your bootloader is unlocked just by toggling this setting, it may still be locked even after toggling the setting. You'll have to verify whether your bootloader is actually unlocked or not. Do some Google searches for:
"Check bootloader status on Samsung devices"
This should give you results to find a method to verify your bootloader status.
Once you have verified that your bootloader is unlocked, you can use the Magisk rooting method. Read the "Boot Image Patching" section in the link below, there are also several other guides all over the internet and videos on YouTube that give instructions on patching your boot.img. As for actually flashing the boot.img, you will be flashing it using Odin. Use 7zip to compress the patched boot.img into a .tar compressed file. When you flash the file using Odin, place .tar file in the AP slot in Odin.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Sent from my LGL84VL using Tapatalk
Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched
Downloads
SM-G781U/U1/W- Model
USERDATA_AIO_S20FE_5G_FORCE_WIPE_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
G781USQS6DUI1_BIT1_SAFE.7z Thanks @markfm
This are odin files and will safely update all image files too bit 4 and keep bit 1 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_G78*_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G78*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G99*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
Xylvion for testing s21
dark11b for testing s21
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7
jrkruse said:
G781U / Twrp
Click to expand...
Click to collapse
Evening
Will this work on the G781B?
Does your version of twrp support the external SD card?
b1k3rdude said:
Evening
Will this work on the F781B?
Does your version of twrp support the external SD card?
Click to expand...
Click to collapse
im sure it will work on that mode. I use afaneh’s twrp so if it works for you then it will work I imagine
jrkruse said:
im sure it will work on that mode.
I use afaneh’s twrp so if it works for you then it will work I imagine
Click to expand...
Click to collapse
I dont follow, did you mean device?
afaneh’s twrp dosent support external SD card access yet (see his thread).
b1k3rdude said:
I dont follow, did you mean device?
afaneh’s twrp dosent support external SD card access yet (see his thread).
Click to expand...
Click to collapse
Then flash different twrp when done. I don’t have the device so im not sure
jrkruse said:
Then flash different twrp when done. I don’t have the device so im not sure
Click to expand...
Click to collapse
Unfortunatly his is the only one that works, hence asking about yours when your thread appeared.
b1k3rdude said:
Unfortunatly his is the only one that works, hence asking about yours when your thread appeared.
Click to expand...
Click to collapse
Sorry but I just use his twrp so I guess the problem will persist
jrkruse said:
Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magisk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
Downloads
SM-G781U/U1- Model
USERDATA_AIO_G781_FORCE_WIPE_NO_BL.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G781_NO_WIPE_NO_BL.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by @afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G78*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G78*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Fix Safetynet
Bluetooth is patched for pairing to survive reboots
Samsung Health working
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
@elliwigy
@klabit87
@Krog18
@me2151
@stang5litre
@Raymonf for modified odin
@rayan-refoua for boot animation
@TheMadScientist
@afaneh92
@kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
@JDBarlow for test S20 stuff
Click to expand...
Click to collapse
Is that this model SM-G781UZBZAIO thats from samsung website for cricket model which I expect shortly. Ive used odin before .
jrkruse said:
im sure it will work on that mode. I use afaneh’s twrp so if it works for you then it will work I imagine
Click to expand...
Click to collapse
So you can make twrp backup in recovery mode to your external storage?
Tigerevo said:
So you can make twrp backup in recovery mode to your external storage?
Click to expand...
Click to collapse
did you even read the above post. I think this has been answered. The answer is no
Van u help me to pay for bootloader unlock fro samsung s20 f3 sm-g78u
CHINOGAMBINO said:
Van u help me to pay for bootloader unlock fro samsung s20 f3 sm-g78u
Click to expand...
Click to collapse
if you got the phone via a network you're paying your monthly bills with money, if you bought the phone outright you paid for it with money. unless you've bought a stolen or lost phone for very very cheap you have money.
Can you pleaseeeee make it for u2????!!!!
Hi, could you please share the method ?
I would like to do the same on G781B with CSC XEF:
Download Samsung Galaxy S20 FE 5G SM-G781B XEF France firmware
All Samsung firmwares for Galaxy S20 FE 5G in France with model code SM-G781B. We offer free and fast download options. Check them out now.
www.sammobile.com
Deleted - dumb question...
So why TWRP cannot access external SD card? Back in the day when I had Motorola X Pure Edition unlocked and rooted with TWRP installed I was using my SD card as the backup location. What differs?
Hitti2 said:
So why TWRP cannot access external SD card? Back in the day when I had Motorola X Pure Edition unlocked and rooted with TWRP installed I was using my SD card as the backup location. What differs?
Click to expand...
Click to collapse
the dev doesn't actually have the phone in his hands and google has changed how android works quite a bit under the hood.
Can you elaborate on how the safetynet is fixed
does it use the kdrag0n module
is this working on SM-G781W ?
I have installed Lineage OS (Android 10) on my phone and TWRP through download mode and ODIN. The instructions I followed had no mention of unlocking the bootloader but it worked. I did not check the bootloader prior to the process nor did I find anything in the settings menu indicating anything about the bootloader. I therefore assume my bootloader is almost certainly unlocked but in the interest of being 100% certain that I will not brick my phone, I would just like to confirm with some more experienced members of the community if this is indeed true. Can I attempt to flash magisk using TWRP? If my phone has a locked bootloader and I attempt to install Magisk, is there any hope of recovery or would my phone be completely unusable? Thank you.
Ali_Shaikh744 said:
I have installed Lineage OS (Android 10) on my phone and TWRP through download mode and ODIN. The instructions I followed had no mention of unlocking the bootloader but it worked. I did not check the bootloader prior to the process nor did I find anything in the settings menu indicating anything about the bootloader. I therefore assume my bootloader is almost certainly unlocked but in the interest of being 100% certain that I will not brick my phone, I would just like to confirm with some more experienced members of the community if this is indeed true. Can I attempt to flash magisk using TWRP? If my phone has a locked bootloader and I attempt to install Magisk, is there any hope of recovery or would my phone be completely unusable? Thank you.
Click to expand...
Click to collapse
Which device?
Samsung didn't need an bootloader unlock until i think Galaxy S5.
Also since you already successfully flashed TWRP and lineage, i assume flashing Magisk won't make any difference
S6 Edge (G925F). I flashed Magisk and it worked. I asked on Reddit as well so a guy told me I wouldn't be able to boot a custom ROM or TWRP if my bootloader was locked so it should be okay. Thanks.
The same here I have Samsung galaxy tab a6 and I flashed twrp using Odin successfuly
and install lineage custom ROM without unlocking boot loader and I install supersu and it worked perfectly but l wented to use magisk and for that l fully unrooted SuperSU and flash latest magisk but the problem is here after flashed magisk successfuly rebooted and magisk app icon is not showing up on homescreen I install it manuly from file manager the app icon uninstalled it self again a don't now what I have to do
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.