There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
use any of the many md5 checking apps out there
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.
|Thread Tools||Search this Thread|