Hi, I have already rooted and unlocked my bootloader then proceeded to flash a custom ROM. I want to try out a different ROM so do I have to re-do the whole root and unlock bootloader process ? I know its just flash one simple zip file in recovery but the reason I ask is my phone got soft bricked last time around.
dannyboy951 said:
Hi, I have already rooted and unlocked my bootloader then proceeded to flash a custom ROM. I want to try out a different ROM so do I have to re-do the whole root and unlock bootloader process ? I know its just flash one simple zip file in recovery but the reason I ask is my phone got soft bricked last time around.
Click to expand...
Click to collapse
Once it's unlocked you don't need to do it again unless you intentionally re-lock it or get a new phone.
Also be careful if you somehow get vzw OTA pushed to your phone (sometimes happens without you knowing it) it will lock your bootloader again and when you go to flash it will say something about taking your phone to verizon. Don't panic as most people do all you have to do is unlock again and everything will be fine
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 ?
Is it possible to pull the 33R OTA package off the OnePlus One site (or anywhere else), and flash the package (via fastboot), on an "exploited" bootloader. In my case, I have an original OnePlus One with the old bootloader, which can be exploited, so that I can do stupid stuff, without unlocking the bootloader. Is it possible to extract the bootloader from a 33R edition (or greater) CM11s ROM, and only flash the /system and other partitions without overwriting my exploited bootloader. (I.e. flash the individual packages via fastboot)
You might ask me why I want to keep the old, unsecure bootloader on my OPO? Cause I don't want to constantly lock/unlock the bootloader after each OTA, and also because I like my OPO that way. (I'm on 25R at the moment)
Why do you think you need to lock/unlock the bootloader for an OTA? That isn't true at all. Just unlock it, leave it unlocked, and you never need to worry about it again.
Transmitted via Bacon
timmaaa said:
Why do you think you need to lock/unlock the bootloader for an OTA? That isn't true at all. Just unlock it, leave it unlocked, and you never need to worry about it again.
Transmitted via Bacon
Click to expand...
Click to collapse
The bootloader is there for a 2nd security measure, in case your phone falls into the wrong hands. After you're done rooting and messing about with the phone, you'd relock the bootloader, so if someone tries to hack your phone via root shell, they would have to wipe the phone. For whatever reason, I want to keep my exploitable bootloader, but also update at the same time. AFAIK, the bootloader has no effect on the Android OS, so I was asking whether I could flash every package, except the bootloader, via fastboot. I know keeping the exploitable bootloader is a stupid thing to do, but it's just as stupid as leaving the bootloader unlocked after rooting.
Desolutional said:
The bootloader is there for a 2nd security measure, in case your phone falls into the wrong hands. After you're done rooting and messing about with the phone, you'd relock the bootloader, so if someone tries to hack your phone via root shell, they would have to wipe the phone. For whatever reason, I want to keep my exploitable bootloader, but also update at the same time. AFAIK, the bootloader has no effect on the Android OS, so I was asking whether I could flash every package, except the bootloader, via fastboot. I know keeping the exploitable bootloader is a stupid thing to do, but it's just as stupid as leaving the bootloader unlocked after rooting.
Click to expand...
Click to collapse
The chances are if your phone was to be stolen, the thief wouldn't even know a thing about what a bootloader is. As what Tim said, there's no reason to leave your bootloader locked again unlocking.
Take a look into cerberus if you want recovery mode protection for anti theft if you're worried. And no it isn't "stupid" to leaving the bootloader unlocked after rooting, re unlocking would cause the phone to be wiped on your part.
Well I'll give it a shot, and see what happens,
Surely the OTA doesn't need to reflash the bootloader, it's just there as an exploit fix.
So i held out taking the otas for a while to avoid losing root and am still on 4.2.2 post camera update. I know, it's sad, but I have root so i haven't been dying to update.
However, i just saw that sunshine will unlock my bootloader, which I'm going to do. What I'm confused about though is once i unlock my bootloader, how do I get to 4.4.4? Can I just revert everything to stock and take all of the otas (and then flash twrp to get root)? I heard that something in one of the otas changed something with the bootloader, so i don't know if taking that would cause problems with an unlocked bootloader or make me lose my unlocked status. Either way, could i just flash a 4.4.4 image directly from 4.2.2? If so where do i get a stock image to flash? Thanks for any help!
Once you have successfully unlocked, make sure you are status 3 unlocked in fastboot.
Once confirmed, you can use the rsd lite, and use the stock firmware from:
http://sbf.droid-developers.org/
Next, flash twrp for the ghost from their website.
Lastly if you want root flash supersu.
So can I flash a different OS version from the site that you linked? Or is that just to return to stock in anticipation of flashing TWRP and using that to flash a later android version?
rule of thumb is you cannot downgrade, only upgrade or revert to the same version you are already on
This seemed like the easiest route to a rooted 4.4.4... Unlock bootloader via Sunshine, and proceed as instructed here: http://forum.xda-developers.com/droid-ultra/general/unlocked-boot-xt-1080-restore-4-4-4-pre-t2883131
Data remains intact, unlocked bootloader warning on boot logo fixed, and TWRP (or Philz) flashed as recovery. Super easy. Good times.
Deleted. Redundant post.
Sent from my DROID Maxx
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
rcji said:
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
Click to expand...
Click to collapse
Yep true. Can't take OTAs with out stock recovery. But it is easy to flash Stock Recovery then back to TWRP after the OTA. Of course safest option is to flash stock fxz without wiping data before taking OTAs.
Personally have my own recovery and logo.bin script I keep for just this reason. Run RSDlite with the stock software take OTA (if no fxz yet for the OTA) then full bit and setup and finally flash the recovery and logo.bin I use.
Many ways of doing it just find its easier for me this way probably cause this is how I learned from trial and error is all. Probably an easier way though.
Ok, I searched for about 2 hours Google and here, I get a lot of don't relock it on twrp or custom recovery or rom. I get why here cause you changed the way the phone boots, essentially.
My question is that since i have only rooted my phone. Can I relock my bootloader. I install updates via local and then let magisk install to inactive after ota to keep root.
Deac0n said:
Ok, I searched for about 2 hours Google and here, I get a lot of don't relock it on twrp or custom recovery or rom. I get why here cause you changed the way the phone boots, essentially.
My question is that since i have only rooted my phone. Can I relock my bootloader. I install updates via local and then let magisk install to inactive after ota to keep root.
Click to expand...
Click to collapse
Magisk is installed in boot partition and for do this, it needs unlocked bootloader or it can't access boot partition. So for answering your question, you can try, but i don't think relocking bootloader with a modified boot img is safe, And why you want to relock bootloader? Simply keep it unlocked
Deac0n said:
Ok, I searched for about 2 hours Google and here, I get a lot of don't relock it on twrp or custom recovery or rom. I get why here cause you changed the way the phone boots, essentially.
My question is that since i have only rooted my phone. Can I relock my bootloader. I install updates via local and then let magisk install to inactive after ota to keep root.
Click to expand...
Click to collapse
Why? Just leave it alone
Was trying to learn, and am going to leave it alone with the answers from here, I also learned why.
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.