So, I recently got a Galaxy s3 and i noticed that when I boot, It says samsung custom with a little lock that is unlocked. Is my bootloader unlocked somehow? Im new to samsungs so i dont know much about the bootloaders and such. It is running the latest firmware with 4.4.2 and rooted with towel root.
johnny567 said:
So, I recently got a Galaxy s3 and i noticed that when I boot, It says samsung custom with a little lock that is unlocked. Is my bootloader unlocked somehow? Im new to samsungs so i dont know much about the bootloaders and such. It is running the latest firmware with 4.4.2 and rooted with towel root.
Click to expand...
Click to collapse
If your on 4.4.2 your more than likely not unlocked. 4.3 and 4.4.2 are both locked bootloaders. To be sure you can post a screen shot of your about phone screen here
Sent from my Nexus 5
Related
Hi,
I have an S3 I'd like to get setup for a gift to my father. I have an unlocked S3 running an older rom. I'd like to get the most recent stock Verizon rom all setup on the phone will keeping the unlocked bootloader.
Can anyone please point me in the right direction?
Thanks so much!
Anyone know what options are availible for S3 opwners with and Unlocked boot loader?
You can only get the TW(Touchwiz) 4.4.2 NE1 rom in locked bootloader form. It's truly up to you if you want to update to the latest version while looking your bootloader down
From my CM11 S3
Is there a way to pull out the piece of the rom that's re-locking the bootloader? No I do not want to re-lock it just have a up to date rom on it. hmm?
Boss428man said:
Is there a way to pull out the piece of the rom that's re-locking the bootloader? No I do not want to re-lock it just have a up to date rom on it. hmm?
Click to expand...
Click to collapse
Nope. Many devs have tried and no one was successful. I wouldn't suggest trying to yourself
From my CM11 S3
Ok i recieved my galaxy s3 in the mail today and look up how to root it.I found a very easy way by using towel root with supper something to do some binary configuring so it would be a good root.Any way after my device was rooted i decided to get CWM so i could install a custom rom.I tried odin but when i tried it it failed to flash.So then i went on the play store and got rom manager and installed it through there.I then tried to get into CWM and saw this message "Verizion has detected 3rd party software bring it to a verizion shop" something like that.Anyway idk what to do now.Do i unlock the bootloader now? is the bootloader even the problem? if i unlock the bootloader will my device be okay and will i be able to get into CWM? i really need help its been a while since i rooted the last time i rooted it was a samsung galaxy player 5.0 and i was able to get CWM and root i digress.Thanks in advance.
im running 4.2.2
Nitrosolid said:
Ok i recieved my galaxy s3 in the mail today and look up how to root it.I found a very easy way by using towel root with supper something to do some binary configuring so it would be a good root.Any way after my device was rooted i decided to get CWM so i could install a custom rom.I tried odin but when i tried it it failed to flash.So then i went on the play store and got rom manager and installed it through there.I then tried to get into CWM and saw this message "Verizion has detected 3rd party software bring it to a verizion shop" something like that.Anyway idk what to do now.Do i unlock the bootloader now? is the bootloader even the problem? if i unlock the bootloader will my device be okay and will i be able to get into CWM? i really need help its been a while since i rooted the last time i rooted it was a samsung galaxy player 5.0 and i was able to get CWM and root i digress.Thanks in advance.
im running 4.2.2
Click to expand...
Click to collapse
Your going to be upset but you have a locked bootloader. You cannot have custom recovery or most custom roms. I suggest you return it if these things are important to you and get an at&t or t mobile s3 because neither of them have locked bootloaders
Datboi459 said:
Your going to be upset but you have a locked bootloader. You cannot have custom recovery or most custom roms. I suggest you return it if these things are important to you and get an at&t or t mobile s3 because neither of them have locked bootloaders
Click to expand...
Click to collapse
I'm almost sure the att version has a locked bootloader also. Att phones for the most part are similar to VZW ones
Sent from my Nexus 5
ShapesBlue said:
I'm almost sure the att version has a locked bootloader also. Att phones for the most part are similar to VZW ones
Sent from my Nexus 5
Click to expand...
Click to collapse
What S3 device doesnt have a locked boot loader?
Datboi459 said:
Your going to be upset but you have a locked bootloader. You cannot have custom recovery or most custom roms. I suggest you return it if these things are important to you and get an at&t or t mobile s3 because neither of them have locked bootloaders
Click to expand...
Click to collapse
Yeah your right.I really wanted to get a custom rom and over clock do all this nice stuff and make my device as awesome as i can make it.i hate verizion and any carrier who locks bootloaders :/.i guess im just gonna un-root it and try to get it back the way it was.Do you know how i can get that verizion message to go away and unroot?
Nitrosolid said:
What S3 device doesnt have a locked boot loader?
Click to expand...
Click to collapse
The t-mobile and sprint version for sure have unlocked bootloaders
Datboi459 said:
The t-mobile and sprint version for sure have unlocked bootloaders
Click to expand...
Click to collapse
That's true but I'm not sure about the att one
Sent from my Nexus 5
ShapesBlue said:
That's true but I'm not sure about the att one
Sent from my Nexus 5
Click to expand...
Click to collapse
The at&t galaxy s3 bootloader is unlocked. They started locking the bootloader when the s4 came out: http://www.ubergizmo.com/2013/08/att-stops-unlocked-bootloader-support/
Datboi459 said:
The at&t galaxy s3 bootloader is unlocked. They started locking the bootloader when the s4 came out: http://www.ubergizmo.com/2013/08/att-stops-unlocked-bootloader-support/
Click to expand...
Click to collapse
Right its an older baseband/update that's unlocked just like the VZW S3 running 4.1.2 was unlock able but newer versions are not unlockable
Sent from my Nexus 5
ShapesBlue said:
Right its an older baseband/update that's unlocked just like the VZW S3 running 4.1.2 was unlock able but newer versions are not unlockable
Sent from my Nexus 5
Click to expand...
Click to collapse
On the AT&T S3 (i747) once you take the 4.3 update (MJB) the bootloader is restricted in that you can not down grade it, or any subsequent updates. (It is my daily driver phone)
It is not locked in the sense that you are prohibited from rooting, flashing custom recoveries, custom ROMs, etc. Once you upgrade to the NE4 bootloader and modem you must keep the version numbers for the bootloader and modem matched. It is possible to run custom JB roms on the KK bootloader and modem, although you may need to edit the updater script to get the custom recovery to flash the rom. People are running JB, KK, and LP ROMs on firmware from 4.3 upwards. These ROM are TW mods, AOSP, CM, and CM derivatives.
dawgdoc said:
On the AT&T S3 (i747) once you take the 4.3 update (MJB) the bootloader is restricted in that you can not down grade it, or any subsequent updates. (It is my daily driver phone)
It is not locked in the sense that you are prohibited from rooting, flashing custom recoveries, custom ROMs, etc. Once you upgrade to the NE4 bootloader and modem you must keep the version numbers for the bootloader and modem matched. It is possible to run custom JB roms on the KK bootloader and modem, although you may need to edit the updater script to get the custom recovery to flash the rom. People are running JB, KK, and LP ROMs on firmware from 4.3 upwards. These ROM are TW mods, AOSP, CM, and CM derivatives.
Click to expand...
Click to collapse
That's pretty much how it was on the VZW S3, after the 4.1.2 update there was no going back
Sent from my Nexus 5
ShapesBlue said:
That's pretty much how it was on the VZW S3, after the 4.1.2 update there was no going back
Sent from my Nexus 5
Click to expand...
Click to collapse
I agree with you about the no going back.
The big difference is that the AT&T S3 can install the custom recovery or ROM of your choice even if you have taken all of the OTA updates. It is not limited to two or three "safe" ROMs.
Anyhow, all of this is off topic of the thread.
dawgdoc said:
I agree with you about the no going back.
The big difference is that the AT&T S3 can install the custom recovery or ROM of your choice even if you have taken all of the OTA updates. It is not limited to two or three "safe" ROMs.
Anyhow, all of this is off topic of the thread.
Click to expand...
Click to collapse
Ah no worries there. It is what it is. I'd rather just have an unlocked bootloader and not have to fiddle with specific things. I'm loving my Nexus and wouldn't go back to a Samsung right now if I was paid to do it
Sent from my Nexus 5
ShapesBlue said:
Ah no worries there. It is what it is. I'd rather just have an unlocked bootloader and not have to fiddle with specific things. I'm loving my Nexus and wouldn't go back to a Samsung right now if I was paid to do it
Sent from my Nexus 5
Click to expand...
Click to collapse
My wish is that a Nexus had a removable battery and an external sdcard >> the perfect device. ;-D
dawgdoc said:
My wish is that a Nexus had a removable battery and an external sdcard >> the perfect device. ;-D
Click to expand...
Click to collapse
Its not as bad as it sounds. I've gotten use to it not having either. Solid device overall
Sent from my Nexus 5
Hi!
Is there any way to use the international rom with galaxy s6 Verizon version??
Thanks!
alexcochifu said:
Hi!
Is there any way to use the international rom with galaxy s6 Verizon version??
Thanks!
Click to expand...
Click to collapse
Not without unlocking the device, which can't be done on the verizon s6.
Gizmoe said:
Not without unlocking the device, which can't be done on the verizon s6.
Click to expand...
Click to collapse
I already unlocked the device, i actually have the CLEAN ROM installed---
alexcochifu said:
I already unlocked the device, i actually have the CLEAN ROM installed---
Click to expand...
Click to collapse
I'm not talking about root. I'm talking about unlocking the bootloader so you can flash modified kernels and what not.
Gizmoe said:
I'm not talking about root. I'm talking about unlocking the bootloader so you can flash modified kernels and what not.
Click to expand...
Click to collapse
Ok. SO how do i know if it´s unlocked? Because i bought this s6 used....
The problem is the Verizon S6 family is currently unable to have modified bootloader files as no one has found a way to change them with or without tripping Knox, the security suite on our phones. Hell, everything updated past Firmware update OF1 isn't even rooted yet and no one is sure when or if we will even have one. Basically what I'm saying is, there is no way for you to get the international ROM onto your phone unless you just happened to either crack the system yourself or the person you got it from managed to find a way without telling the world about it.
Word of advice, you can have a phone that is rooted with a flashed ROM but still have a locked bootloader. In our case it was due to an exploit that was patched.
Sent from my Super Computer (1976) with Tap Tap Talkolution
I just got the AT&T version of the note 12.2 and got it rooted but I want to know if we have an unlocked bootloader for them. I got the "unrecognized software" message when I tried to install TWRP.
AT&T version bootloader is locked so you can't add a custom recovery. What is your pro running, kitkat or lollipop?
hnic32 said:
AT&T version bootloader is locked so you can't add a custom recovery. What is your pro running, kitkat or lollipop?
Click to expand...
Click to collapse
Kitkat.
shadow105720 said:
Kitkat.
Click to expand...
Click to collapse
You can update to Lollipop which finally makes the note pro run a whole lot better. Oh, just in case AT&T doesn't already know.....YOU SUCK AT&T!!! STOP LOCKING OUR DEVICES DOWN!!!!
It says it provides the latest Android Security Patch on the Verizon Galaxy S5 Update page.
Now that the Odin FW is out, I flashed an Odin tar of the FW without the aboot and still have a Dev Edition phone. Now we just need an updated aboot.
Original Post:
It says it provides the latest Android Security Patch but if you notice, there is a difference in the "middle" of the build number, which happens when they update the bootloader.
Verizon Galaxy S5 Update page
The first time they updated the bootloader, it prevented downgrading. The number went from G900VVRU1 to G900VVRU2. This time, it's going from G900VVRU2 to G900VVRS2. What does this mean? I have no clue. But I do know that nobody should update until someone like @muniz_ri or @jrkruse has a look at the bootloader to see what exactly this changes. Hopefully it doesn't remove the ability to have Dev Bootloaders anymore.
Dudash said:
It says it provides the latest Android Security Patch but if you notice, there is a difference in the "middle" of the build number, which happens when they update the bootloader.
Verizon Galaxy S5 Update page
The first time they updated the bootloader, it prevented downgrading. The number went from G900VVRU1 to G900VVRU2. This time, it's going from G900VVRU2 to G900VVRS2. What does this mean? I have no clue. But I do know that nobody should update until someone like @muniz_ri or @jrkruse has a look at the bootloader to see what exactly this changes. Hopefully it doesn't remove the ability to have Dev Bootloaders anymore.
Click to expand...
Click to collapse
The 2 in the version represents the bootloader version usually as long as that doesn't change you should still be able to downgrade
jrkruse said:
The 2 in the version represents the bootloader version usually as long as that doesn't change you should still be able to downgrade
Click to expand...
Click to collapse
But what does it mean when they change it from VRU2 to VRS2?
The VZW S5 bootloader has always been VRU1 or VRU2. Now all of the sudden they change it to VRS2? They had to have changed something.
Dudash said:
It says it provides the latest Android Security Patch but if you notice, there is a difference in the "middle" of the build number, which happens when they update the bootloader.
Verizon Galaxy S5 Update page
The first time they updated the bootloader, it prevented downgrading. The number went from G900VVRU1 to G900VVRU2. This time, it's going from G900VVRU2 to G900VVRS2. What does this mean? I have no clue. But I do know that nobody should update until someone like @muniz_ri or @jrkruse has a look at the bootloader to see what exactly this changes. Hopefully it doesn't remove the ability to have Dev Bootloaders anymore.
Click to expand...
Click to collapse
No matter what they change, I think it will be unlocked forever.
I have seen the update yesterday but still not tested as s5 is my daily driver.
mohammad.afaneh said:
No matter what they change, I think it will be unlocked forever.
I have seen the update yesterday but still not tested as s5 is my daily driver.
Click to expand...
Click to collapse
No if they make it so we can't downgrade then their will be no way to obtain root. Since my bootloader update isn't always successful you could get stuck without being able to root on a worse case scenario. Now you can always start over and reroot
jrkruse said:
No if they make it so we can't downgrade then their will be no way to obtain root. Since my bootloader update isn't always successful you could get stuck without being able to root on a worse case scenario. Now you can always start over and reroot
Click to expand...
Click to collapse
You are right, if no root there no unlock.
But If you noticed that all the unlocked devices, Note 3, Note 4 and S5 are downgradeable. S3 and S4 are not!
I think its all about eMMC not the bootloader.
mohammad.afaneh said:
You are right, if no root there no unlock.
But If you noticed that all the unlocked devices, Note 3, Note 4 and S5 are downgradeable. S3 and S4 are not!
I think its all about eMMC not the bootloader.
Click to expand...
Click to collapse
If i read your post correctly, I believe that you may be incorrect on the last sentence. To unlock the bootloader, the devices mentioned need to have the Samsung eMMC 15 chip to aquire unlocking the bootloader.
Also, pretty much the same as the S5, N4 & N3, the S3 & S4 are downgradeable IF you didn't take the update that locked the bootloaders. As i know because I still own my VZW S3 which is unlocked and running TWRP recovery
al50 said:
If i read your post correctly, I believe that you may be incorrect on the last sentence. To unlock the bootloader, the devices mentioned need to have the Samsung eMMC 15 chip to aquire unlocking the bootloader.
Also, pretty much the same as the S5, N4 & N3, the S3 & S4 are downgradeable IF you didn't take the update that locked the bootloaders. As i know because I still own my VZW S3 which is unlocked and running TWRP recovery
Click to expand...
Click to collapse
I own S3 locked on 4.4.2 and 15 CID and no downgrade caused by eMMC and the aboot together, I think there a fuse triggerd so we cant unlock and downgrade.
My S4 is 11 CID and no downgrade too.
The PL1 update is not up yet so we cant be sure it will lock the bootloader or not, but the S6 already has same bootloader versioning letters on the new update!
I also noticed that my Tab 4 (no carrier, wifi only) just got an update for the first time in like a year and it's bootloader version changed from UEU1 to UES1. Maybe it doesn't mean anything after all.
Well now that the odin firmware came out this morning, I created a .tar without the aboot, flashed it, and I still have a Dev edition with the PJ2 aboot. Hopefully @jrkruse will create a bootloader update zip for the PL1 aboot.
The VZW S4 just got it too.
https://forum.xda-developers.com/galaxy-s4-verizon/general/update-1545vrsgpl1-t3537781
I'm not the sharpest tool. If the S4 Bootloader was locked via EFuse, how did they update it?
Anyone got and update zip for pl1 ?
Sent from my SM-G900V using Tapatalk
I was able to obtain root access on my device running LRX22C.I545VRSGPL1, bootloader was indeed updated, could it hinder progress on finding an unlock?