Related
Does unlocking the bootloader give you root?
And in which instances can you flash a custom recovery or customs ROMs?
Rooting means you can install apps that require root access (like titanium backup or setcpu). Unlocked bootloader means you can load any rom, kernel, etc that you like. Unlocked bootloader is usually acquired after rooting.
I'm not sure I totally understand the first reply, so here is my take on it.
Rooting will let you install apps that require root as already stated, but rooting will let you install custom ROMs and do just about any tweak you want. I finally did unlock my bootloader, but the only benefit I gained was being able to change the flash screen, which is the first screen you see when the phone powers on.
I have read that it's harder to brick your phone with a s=off bootloader too.
It is not harder to brick your phone with an unlocked bootloader, just easier to recover from a soft-brick. An unlocked bootloader will allow you to flash using fastboot. So in the case of a corrupt recovery, or something along those lines, you are able to flash it using your computer. It basically allows you to flash different parts of an image separately.
lowandbehold said:
It is not harder to brick your phone with an unlocked bootloader, just easier to recover from a soft-brick.
Click to expand...
Click to collapse
That's pretty much what I meant, I just didn't say it right. Thanks for clearing it up.
How to find my phones' bootloader is locked or not? Because i already flashed different custom ROMs and using it.
Regards,
Cjey
If you are rooted with a custom recovery, your bootloader is unlocked.
lowandbehold said:
If you are rooted with a custom recovery, your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks buddy,
I want to know that what if i flash ROM for locked bootloaders?
Honestly, I didn't know you can root your phone till today I read a few posts here. So thank you all guys for the input
slight confusion over rooted
i had the .67 generic uk firmware, i downloaded the central europe .73 firmware and used flashtool to flash the ftf file,
all worked fine once i installed the drivers on flash tool,
my confusion is...... alot of people are saying there phone is rooted/bootloader unlocked, am i rite in thinking my phone is rooted and not unlocked,
others have also said they have flashed the .img to the phone which i havent done, is there something ive done wrong ?
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
I know a bit of what I'm doing as I have rooted and flashed roms on an htc desire and a samsung s2x (t989).
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Can someone point me in the right direct?
Chris9446 said:
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
Click to expand...
Click to collapse
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
Click to expand...
Click to collapse
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Click to expand...
Click to collapse
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
f69m said:
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
Click to expand...
Click to collapse
Thanks was a lot of great information! I rooted my pad and did a few speed optimization things such as re-trimming and now its much smoother! Maybe I'll try a custom rom later but as for now, I'm happy with the updates that Asus provides
cmendonc2 said:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
Click to expand...
Click to collapse
I'll keep that in mind but I believe there should be more soon as f69m, stated that asus release the kernel for 4.2
I signed that petition in your signature as well
I'd say go for the 'full experience'. Having an unlocked device also allows you to reflash ROMs at will and can also help in a pinch when it comes to backups/restores. Also, if you happen to lose root, it's easily re-rootable through the bootloader.
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
danjng said:
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
Click to expand...
Click to collapse
Well, stay away from the TWRP 2.5.0.0-4.2 provided in some thread today, but TWRP 2.4.4.0-4.2 should still be working fine.
Sent from my TF300T using Tapatalk HD
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
New debloated version with insecure kernel and init.d support, rooted with Chainfire's Beta 2.71 SuperSU credit to SuperR for the help with the updater perms.
FIXED DOWNLOAD ALL APOLOGIES
Skinny Stylo Alpha version
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Saved
Requirements- Unlocked bootloader
Click to expand...
Click to collapse
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
runningnak3d said:
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
Click to expand...
Click to collapse
@runningnak3d
I would prefer to be bootloader unlocked through fastboot oem unlock before doing any mods in 6.0. Every single time I did not I got secure boot error. If you make any system change on 6.0 with locked boot it will not boot.
Thank you for taking the time to do this.
:good::good:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
The main reason I made this was because I can never boot recovery or fastboot manually ( ex. w/hardware buttons) when you have the insecure kernel adb works when at the splash screen so it's easier to recover if you have any problems.
Sent from my LG-H631 using XDA-Developers mobile app
Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
wrenchman76 said:
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
Click to expand...
Click to collapse
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
runningnak3d said:
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
Click to expand...
Click to collapse
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
wrenchman76 said:
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
Click to expand...
Click to collapse
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Waiting on the debloated version.
Sent from my LGMS631 using Tapatalk
runningnak3d said:
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Click to expand...
Click to collapse
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You didn't need to ship it back to LG. Firmware download mode is always available (hold vol up while plugging in USB cable -- just vol up, not vol up + power). Continue holding vol up until FW DL mode displays). Then just use the LG flash tool to flash a KDZ. It is a PITA when you have to go back that far, but you can't brick these phones, not with software at least -- they would need to be physically altered
-- Brian
Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You sent your device in for a soft brick? You should set up the flash tool for our phone with a 10j.kdz before doing anything. Hope you get it back soon.
Debloated version
Fixing some force close problems on a debloated version now, should be up later today or tonight.
@runningnak3d
Flashing the KDZ seems easy enough. But how could I fix it without unrestricted access to a computer? And my stock charger is broken without a USB cable. I had no choice but to send it in for repairs. Guess I'll be stuck on Lollipop for a while longer, at least.
Edubyah said:
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Click to expand...
Click to collapse
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
Can the bootloader be unlocked on the CDMA versions (ex. Boost, Sprint, Verizon)? If you can I will make a variant for it. But if you can't NO.
I just found out that the unlocked bootloader in 6.0 survives even the .kdz flashtool. So once you unlock your boot in 6.0 with fastboot oem unlock you never have to do it again even survived kdz downgrade to lollipop and update to 6.0 stayed unlocked.
JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
works great on metro ms631 just need wifi to stop turning its self off can you guys fix it! h631/ms631 mm kernel works find no errors help needed fixing wifi connection thanks
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.
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.