Bootloader on 4.3 - Verizon Samsung Galaxy S III

Hi when I rooted and tried to flash twrp I soft bricked my phone and when I Odin back to stock a flashed safestrap I rebooted and on the boot screen it showed an unlocked lock with the word custom below it. So doesn't that mean that my bootloader is unlocked?
Sent from my SCH-I535 using xda app-developers app

siouxhockey11 said:
Hi when I rooted and tried to flash twrp I soft bricked my phone and when I Odin back to stock a flashed safestrap I rebooted and on the boot screen it showed an unlocked lock with the word custom below it. So doesn't that mean that my bootloader is unlocked?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It doesn't, that custom padlock is known to show up on completely stock firmware. It's not really an indicator of much of anything.
Sent from my SCH-I535 using Tapatalk 2

Related

custom opened padlock

i rooted my s3, then i unlocked the bootloader. i still havent flashed anything but now when i reboot my phone i get the custom notification with the unlocked padlock. did i do something wrong or is this normal.
edit: i used a windows based program to root and i used twrp to flash the unlocked bootloader
I am waiting on a stable completely functioning rom before flashing.
krbernier said:
i rooted my s3, then i unlocked the bootloader. i still havent flashed anything but now when i reboot my phone i get the custom notification with the unlocked padlock. did i do something wrong or is this normal.
edit: i used a windows based program to root and i used twrp to flash the unlocked bootloader
I am waiting on a stable completely functioning rom before flashing.
Click to expand...
Click to collapse
Sounds like it's not unlocked if you still have the custom boot screen. What method did you use to unlock?
You are not unlocked. When your bootloader is unlocked that Samsung screen just flies by. No padlock no waiting.
Sent from my SCH-I535 using Tapatalk 2
Thanks! i used a windows batch file to do the unlock...guess ill give it another go.
worked thanks!
My SGiii now does this when booting. I have root. I used the devFS root method. I to my knowledge I have not flashed the boot loader. Is this what people were talking about by adding one to there flash counter? If so I might as well flash cwm.
Is my warranty void now?
Sent from my SCH-I535 using xda app-developers app
Xiuix said:
My SGiii now does this when booting. I have root. I used the devFS root method. I to my knowledge I have not flashed the boot loader. Is this what people were talking about by adding one to there flash counter? If so I might as well flash cwm.
Is my warranty void now?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Has nothing to do with flash counter. It shows that software is modified and is caused by root. Unlocking the bootloader will get rid of lock. Warranty is void only if you don't revert to stock before return.

[Q] How can I tell if my Bootloader is unlocked?

I am rooted and unlocked, using adam's EZ Unlock 1.2 tool and running AOKP 4. I am about to flash a rooted "stock" ROM and am not sure if my bootloader will be unlocked after that flash, is their a way to tell if your bootloader is locked or not?
Thx
When our phones boot up there's two splash screens before the boot animation. The first one just says 'Samsung' and the second one says 'Samsung Galaxy SIII' and the way to tell easily if your bootloader is unlocked is if that first one that just says samsung flashes by in .5/1 second. If it doesn't and stays on the screen for 2-4 seconds then it's not unlocked.
If you're flashing it through a custom recovery, then it shouldn't lock your bootloader as it should only be writing to the system partition.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
damastah said:
If you're flashing it through a custom recovery, then it shouldn't lock your bootloader as it should only be writing to the system partition.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
lol I didn't even catch that. I literally just saw the "how do you tell" part.

[Q] Rooted stock image and updates

Question, I've got the root66 rooted stock image. and now my phones poppin stuff up about updating, when it updates will it brick the phone and need reflashed or should I be fine?...
It won't brick your phone, it will remove root and lock your bootloader though. You would just need to root again.
Sent from my SCH-I535 using xda app-developers app
So it isn't going to yellow triangle me. It'l just re-lock the bootloader and un-root me?
Sent from my SCH-I535 using Tapatalk 2

unable to flash ANY rom with safestrap, Maxx hd

rooted, unlocked, using the latest safestrap (3.12 i think) and ive tried EVERYTHING to get this to work.
Flashed multiple roms and all that ever happens is the bootloader splash screen shows, then a permanent black screen until i hard reset back into recovery and info the unsafe rom. WTF is going on. i've followed all instructions thus far and i've been screwed time and time again. suggestions?
If your bootloader is unlocked you shouldn't be using safestrap. Remove it an flash cwm or twrp. Then flash away.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
If your bootloader is unlocked you shouldn't be using safestrap. Remove it an flash cwm or twrp. Then flash away.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
APPRECIATE THE RESPONSE. PROBLEM SOLVED :good::good::good:

How to Know before flashing custom recovery

Hello I have a chinese opo with cm11s installed.Whenever I run bootloader unlock it says time taken 0.00 sec
okay.Now Im not sure maybe the seller has unlocked the boot loader. Is there a way to know before flashing custom recovery?Thanks.Will flashing custom recovery on locked bootloader will brick my device?
Sent from my One using XDA Premium 4 mobile app
No it will not brick your phone. If your phone's bootloader is locked, it will simply not let you flash a custom recovery. If its unlocked, then it'll flash the custom recovery.
Ensure that update CM recovery in developer options is disabled (to enable the menu, tap build # 10 times in about phone and then go back into developer options)
Thanks it worked,I was right it was already unlocked
Sent from my One using XDA Premium 4 mobile app
Now can I update system officially with twrp.I have unchecked update cm recovery.I saw someone said that the update bricked his phone with twrp installed
Here
http://forum.xda-developers.com/showthread.php?t=2825514
Sent from my One using XDA Premium 4 mobile app
should i update?
Sent from my One using XDA Premium 4 mobile app
that guy used cwm... it seems that that recovery caused his brick.
i think you should use twrp or philz one...

Categories

Resources