Database Develop

[BOOTLOADER] Bootloader Update (sbl.bin) pulled from KA6

EDIT: As jellete stated in a post below this is ONLY for the Samsung Vibrant running Froyo! (JL5 or higher)
Hi. This is the bootloader (sbl.bin) update from KA6. I find it safer to flash a bootloader alone. This is untested. This *should* be compatible with JL5 and upwards. Be aware, if something goes wrong it won't be fixable with Odin nor Heimdall. I am NOT responsible for anything that happens, this is untested, as I mentioned earlier. There is always a small chance of bricks, especially when writing to/replacing the secondary bootloader.
How-To Flash:
You MUST use the stock Recovery! 2e or 3e! Nero users, I believe your recovery is by default, replaced with Clockworkmod, so you cannot flash this. Don't even attempt it.
1. Place it as "update.zip" on the root of your INTERNAL sd card.
2. Reboot into Recovery. (Via 3-button combo or other option, such as adb)
3. Scroll down to "Reinstall Packages", use the power button to select this.
4. Wait for it to flash and pray that it works.
5. If your device powers on, it succeeded, if it refuses to power on, your hardbricked and must get a new phone or a replacement.
I'll say it one more time: If this fails it will hardbrick your phone, beyond repair.
DOWNLOAD: http://db.tt/sNkeDiC

What is different about it?

Why would we want to flash this.. What would be the benefit.. Curious to know

Yeah, I fail to see what the benefit is...

This seems like a REALLY bad idea.

Talk about giving us just enough rope to hang ourselves with...

NikolaiT said:
Hi. This is the bootloader (sbl.bin) update from KA6. I find it safer to flash a bootloader alone. This is untested. This *should* be compatible with JL5 and upwards. Be aware, if something goes wrong it won't be fixable with Odin nor Heimdall. I am NOT responsible for anything that happens, this is untested, as I mentioned earlier. There is always a small chance of bricks, especially when writing to/replacing the secondary bootloader.
How-To Flash:
You MUST use the stock Recovery! 2e or 3e! Nero users, I believe your recovery is by default, replaced with Clockworkmod, so you cannot flash this. Don't even attempt it.
1. Place it as "update.zip" on the root of your INTERNAL sd card.
2. Reboot into Recovery. (Via 3-button combo or other option, such as adb)
3. Scroll down to "Reinstall Packages", use the power button to select this.
4. Wait for it to flash and pray that it works.
5. If your device powers on, it succeeded, if it refuses to power on, your hardbricked and must get a new phone or a replacement.
I'll say it one more time: If this fails it will hardbrick your phone, beyond repair.
DOWNLOAD: http://db.tt/sNkeDiC
Click to expand...
Click to collapse
Youch! This is really putting yourself out there!
If it were me, I would package it as a cwm flash WITH a check at the beginng of the script to ensure that it will only flash on 959's AND over Froyo builds.

jellette said:
Youch! This is really putting yourself out there!
If it were me, I would package it as a cwm flash WITH a check at the beginng of the script to ensure that it will only flash on 959's AND over Froyo builds.
Click to expand...
Click to collapse
Do work, son, go for the gold!

bobbbb said:
Do work, son, go for the gold!
Click to expand...
Click to collapse
When asked by the newest EDT Dev yesterday what restrictions we had about releases, I answered that there is only one of the rules that there is no exception to:
We will not allow the "Einherjar" moniker to be attached to any release that containes a boot.bin or an sbl.bin.
True story.

You are correct. There is no benefit that we have seen so far. All the warning are so moons do not flash this, it is meant for experimentation by revs, not by the average user.

@jellette
I would do this, but people should be smart enough to understand this is only for froyo and the vibrant, if someone flashes on say, a Captivate, then they're bricked and they learned a lesson. Just my point of view.
Sent from my SGH-T959 using XDA App

Will this give us *gasp* fastboot? /curious

smackdown85146 said:
Will this give us *gasp* fastboot? /curious
Click to expand...
Click to collapse
Chances of this are minimal, though "fastboot" is an example of an SBL (secondary bootloader) for HTC phones.

Ide rather take a Tyson punch to the jaw!! But thanks for sharing.
Sent from my SGH-T959 using XDA App

smackdown85146 said:
Will this give us *gasp* fastboot? /curious
Click to expand...
Click to collapse
no.............

Ok I just flashed and I can confirm that it successfully transformed my phone into vibrant 4g

Is there no way to revert yo the old sbl ?

BuLLeT_PrOOf_wAlleTz said:
Ok I just flashed and I can confirm that it successfully transformed my phone into vibrant 4g
Click to expand...
Click to collapse
Huh?
Sent from my SGH-T959 using XDA App

After flashing this everything online was free. All flights on all sites. 15 asian women showed up at my door wanting an orgy. Best bootloader ever!
Seriously though, don't flash this, wait for the genius devs on here to figure out what the possible benefits are and it to be implemented into voodoo or some custom rom. You never know if samsung released us something vicious on purpose to shut us up about the new vibrant, or make us buy the new one???
Sent from my SGH-T959 using XDA App

traicer said:
Is there no way to revert yo the old sbl ?
Click to expand...
Click to collapse
If someone posts the original Sbl, then yes, you should be able to flash back...

[DUMP] Bootloader (from devkit atrix)

So I haven't tried to use this yet, but it was dumped from a devkit atrix that supposedly has a bootloader that doesn't blow
http://www.mediafire.com/?d13i7uxrhw38y7o
SHA: FDA1FDBFD70628CBF1C79361525168847A00830B (motoboot.bin)
DO NOT FLASH THIS!
jimmydafish said:
this is P3Droid again,
I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.
This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.
either way good luck, but do not return the device to ATT if you break it.
Click to expand...
Click to collapse

designgears said:
So I haven't tried to use this yet, but it was dumped from a devkit atrix that supposedly has a bootloader that doesn't blow
http://www.mediafire.com/?q053u356h5u52zd
It can be flashed with Qualcomm QPST
http://www.filecrop.com/QPST.html
Click to expand...
Click to collapse
the link is dead

Does "doesn't blow" mean unlocked/non-encrypted?

t0dbld said:
the link is dead
Click to expand...
Click to collapse
Which? I was able to get a copy of motoboot.bin (I think, anyway. designgears, could you post a md5/sha hash of the bin file for us?)
FYI, here's what I have for the file I was able to download:
Code:
$ shasum motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b motoboot.bin

really i cant tells me file has been removed can you mirror or send ?

"Doesn't blow" should mean "lets us load our own kernels" in this context I think
now to figure out how to get the dev bootloader onto our phones..

sorry, was uploading a compressed version

designgears said:
sorry, was uploading a compressed version
Click to expand...
Click to collapse
ok now to test... this would be great esp considering they jsut anounced on twitter that zoom comes with locked/unlockable bootloader

t0dbld said:
ok now to test... this would be great esp considering they jsut anounced on twitter that zoom comes with locked/unlockable bootloader
Click to expand...
Click to collapse
damn, wish we would have gotten that.

designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.

perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
already did

perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type

Slow Down Everyone...
this is P3Droid again,
I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.
This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.
either way good luck, but do not return the device to ATT if you break it.

Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
Sent from my MB860 using XDA App

t0dbld said:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Click to expand...
Click to collapse
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.

perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
smiths-MacBook-Pro:~ smith$ shasum /Users/smith/Downloads/motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b
smiths-MacBook-Pro:~ smith$ md5 /Users/smith/Downloads/motoboot.bin
MD5 (/Users/smith/Downloads/motoboot.bin) = f3cb372a7498f175b53dc7881e4bd3c2
​
P3Droid, you have past experience with Dev phones and retail phones, what does this mean to the hacking efforts? Does an unsigned bootloader move us past any of the previous obstacles or is this just something to study?

t0dbld said:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Click to expand...
Click to collapse
humancyborg said:
Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you would like to brick your device I can teach you how to get it on, but it will require you to be rooted and running a custom recovery, the other method requires a fully released sbf file.

jimmydafish said:
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.
Click to expand...
Click to collapse
i am listening and i am not flashing anything yet .. .i heard ya before and i hear ya now

Could this bootloader work on Defy also?

I do have to say though with this Xoom news... gives us hope that maybe with GB release for atrix that was promised soon and to include 1080p it might also come with unlock/lock

[PRERLS-REF] Root, BL, Kernel, Recovery

This thread is left here only for historical purposes ! Now that the device has been released, easier and better methods have been developed to gain root, like CF-Root.
.
.
.
.
.
Check your device model ! Settings -> About device -> Model number. This stuff is made for the GT-I9300, if your model number has a suffix, it may not work, or if it is a totally different model, it will not work (may even brick) !
Ladies and gentlemen, we have root on the SGS3 (!)
This will all be common knowledge in the near future, but here's some info I though various devs, chefs, and users will be dying to know!
Unfortunately, I am not able to share the "insecure" kernel with you at the moment, because of fears it is traceable to the leaker (this is said to be the last traceable firmware revision).
Update: The kernel is linked at the bottom of the post.
Update: The easiest way for rooting is now CF-Root
This root is, as expected, trivial. It was a simple matter of repacking the stock kernel, with a modified adbd binary that thinks ro.secure=0 (even if ro.secure=1). This gives access to all adb root commands (see screenshots). Then SuperSU was installed manually.
Kernel
The modification was trivial, because this time around, Samsung is using the standard boot.img format, instead of the zImage format used for SGS1, SGS2, SGNote, etc, that is much harder to repackage.
This is also why I don't feel particularly bad about not giving you the insecure kernel - any serious dev on this board can do the same thing in 10 minutes.
Recovery
The recovery partition is also being used this time around. And thus we can flash recoveries separately from the kernel.
Bootloaders
There was no warning triangle at boot-up after flashing the modified kernel, but download mode did show a custom kernel flash counter which increased. Whether or not flashing a custom recovery also triggers this counter is as of yet unknown. Both flashing kernel and/or flashing recovery will trigger the flash counter!
Final note
This was all tested on a current (release candidate) SGS3 firmware. There may be a newer firmware on true retail/production devices. Though some things may change, it is unlikely to change much. Let's hope nothing
Also, Triangle Away did not work. They have hidden the boot partitions again as on the latest SGNote firmwares.
(No, I don't have an SGS3 yet, everything was done remotely)
Now, everybody say thanks to Samsung! I don't always agree with them, but so far they have been the first and IMHO still are the only high-end Android OEM who aren't complete douchebags in the unlock department!
Download
The instructions below assume some basic knowledge about Samsung devices. This is not a noob-proof guide.
Here's the "insecure" kernel, based on XX NEE ALE8 firmware:
CF-Insecure-SGS3_XX_NEE_ALE8-v1.2.zip
- Extract the linked file (you will get a .tar file)
- Use the ODIN version attached below to that .tar file to your SGS3 as "PDA"
Going from insecure to full root
After having flashed the insecure kernel, boot your phone, and make sure USB debugging is enabled.
Your device is now insecure, so you can use the adb root commands. This does not allow your on-device apps to get superuser access, though. For that, you need to install SuperSU:
Download and extract the sgs3-root-install.zip file, containing SuperSU v0.89. Make sure adb is running correctly, then just double click install.bat (this will reboot your phone).

Wow, that was fast!

Chainfire said:
Ladies and gentlemen, we have root on the SGS3 (!)
(No, I don't have an SGS3 yet, everything was done remotely)
Click to expand...
Click to collapse
bravo my friend i hope the candle wasnt the inspiration or errr turpitude dayyyyymn.....nough said....thanks for leading the way

Appreciate

Finally boot.img/recovery.img about time samsung(on their flasg ship that is)

Remotely! Good work, i can't wait to get the device .
Sent from my GT-I9100 using Tapatalk 2

thats great. i hope they don't 180 on the boot.img format.

So is the GSIII bootloader unlocked from factory or did it require a bootloader unlock?

Phistachio said:
So is the GSIII bootloader unlocked from factory or did it require a bootloader unlock?
Click to expand...
Click to collapse
As with the SGS1, SGS2, and SGNote, it was never locked to begin with.

Awesome!

Awesome work man. Maybe triangle issue can be solved with usb jig

There u go
Sent from my GT-I9100 using Tapatalk 2

Great news!
Can you work any magic with Asus TF300T

Quick work, well done.

Chainfire said:
As with the SGS1, SGS2, and SGNote, it was never locked to begin with.
Click to expand...
Click to collapse
Props to Samsung!

That was fast!
That's 11 days before the device is available commercially! WHoa! That was fast!

W0W. There we meet again. Nice one dude !

I'd be very reserved with yelling "Tjohoo" at this point. Things can change a lot between a developer version (which I assume is the one on Chainfire's hands) and a fully commercial shipper version. Let's just hope Samsung stay cool, and don't cause us more trouble than necessary, like has happened with the HTC One X...

Grats on the fast work man, and even more impressive is that it was done remotely on Windows 8! I've heard a lot of people having issues just getting ADB to work on Windows 8, and yet you managed to root a device for the first time ever using it without even physically having the device!
You truly are an inspiration to this community.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
E:V:A said:
I'd be very reserved with yelling "Tjohoo" at this point. Things can change a lot between a developer version (which I assume is the one on Chainfire's hands) and a fully commercial shipper version. Let's just hope Samsung stay cool, and don't cause us more trouble than necessary, like has happened with the HTC One X...
Click to expand...
Click to collapse
He doesn't have any device in his hands, that's what makes this even more impressive!

Very nice work, thank you and congratulations!

FireTV Partial Bootloader Unlock

Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.

WOW, just WOW, awesome work rbox!
I was definitely not expecting this.

rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)

..

JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm

Rbox do you know if the bootloader can boot from usb?

Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "

Truly amazing. Can't wait for full fledged android on this.

Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.

jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.

I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.

KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.

Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.

KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.

rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again

Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance

Hi, I unlocked the bootloader and it was successfully. Thank you rbox

barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.

Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.

nice, thanks rbox, you rock.

How many people took the 5.1.1 and are stuck with the "locked" bootloader

If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.

The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops

Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1

mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.

se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade

ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"

ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.

se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me

mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.

ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.

se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.

ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.

From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........