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
I just bought this tablet and it seems to have updated itself overnight (that or my kid did it) I want to root it , but it says it's running 5.0.1 now.. if it's possible, could someone walk me through this? I've been reading thru the various root threads, and having no luck-I'm on Ubuntu latest and have adb and fastboot installed..anyone feel like helping me out?
unlock bootloader, flash TWRP, then flash SuperSU
Bogdacutu said:
unlock bootloader, flash TWRP, then flash SuperSU
Click to expand...
Click to collapse
I did the above but with a slight change. I just booted CWM instead of flashing it so till running stock recovery but rooted.
I did this from 5.0.1 after unlocking the bootloader which was a piece of cake. There is a great guide on this forum.
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
ImmoralCore said:
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
Click to expand...
Click to collapse
Your DRM keys are lost forever.
TheTeslaCoil said:
Your DRM keys are lost forever.
Click to expand...
Click to collapse
Ok, so they are lost even if I use the first backup that was made by the person I bought it from ?
DRM=Hardcoded=Once unlocked, always DRM free, even if you use the recovery image ?
And the rest of the questions, what am I supposed to do to get stock lollipop?
In the matter of fact it does not matter if its unlocked or locked, I just want legit lollipop, with the possibility to update regularly. (But if root is possible at the same, it can still be rooted)
Thanks for your reply !
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
TheTeslaCoil said:
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
Click to expand...
Click to collapse
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
ImmoralCore said:
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
Click to expand...
Click to collapse
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
gregbradley said:
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
Click to expand...
Click to collapse
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
ImmoralCore said:
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
Click to expand...
Click to collapse
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
gregbradley said:
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
Click to expand...
Click to collapse
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
ImmoralCore said:
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
Click to expand...
Click to collapse
Good luck.
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