Related
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
you can always use fastboot to go back to 5.0.1
stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.
EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.
Sweet, successful downgrade!
I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!
Disregard! Got it handled. Thanks guys!
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1
EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??
Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?
Hey, I have a att s5 active rooted, what I am wondering is if I can put a s5 active Bell or telus rom on it, and if I can, does anyone have the rom that can send it to me.
Thanks
joemm210 said:
Hey, I have a att s5 active rooted, what I am wondering is if I can put a s5 active Bell or telus rom on it, and if I can, does anyone have the rom that can send it to me.
Thanks
Click to expand...
Click to collapse
I believe the answer is no....reason being is the 870a is bootloader locked...can't flash the kernel or modem of the other rom.
nutt_case said:
I believe the answer is no....reason being is the 870a is bootloader locked...can't flash the kernel or modem of the other rom.
Click to expand...
Click to collapse
I think it is already unlocked I can't remember the exact steps I took but It took forever.
On boot it says custom and shows a unlocked pad so I think that means it's unlocked
I would like to find a bell lollipop rom for it, I don't want to put any att rom on it because it locks tethering and it took lots of ****ing around to get it turned back on.
joemm210 said:
I think it is already unlocked I can't remember the exact steps I took but It took forever.
On boot it says custom and shows a unlocked pad so I think that means it's unlocked
I would like to find a bell lollipop rom for it, I don't want to put any att rom on it because it locks tethering and it took lots of ****ing around to get it turned back on.
Click to expand...
Click to collapse
The custom symbol just means that it has detected you modified your system, it means norhing, your bootloader is still locked.
Sent from my SM-G900A using Tapatalk
Hello community, recently I did the procedure to get the lollipop version in my S4 active i537 keeping root, but after many searches I can't find how to upgrade to marshmallow or nougat version and I wondering why.
I think it have to be because at this moment doesn't exist any way to intall a custom recovery as TWRP or CWM, if this is true, why nobody found the way to unlock the bootloader yet? in order to manage the custom recovery.
And why is so difficult to unlock it?
Which are the differences between this s4 version with the others? And how can I help to unlock the bootloader, thanks in advance.
I'm going to try to answer your questions one at a time:
m44nu33l said:
Hello community, recently I did the procedure to get the lollipop version in my S4 active i537 keeping root, but after many searches I can't find how to upgrade to marshmallow or nougat version and I wondering why.
Click to expand...
Click to collapse
There is not and never will be marshmallow or nougat for the i537. This is because it is outside the "2-year" update cycle of Samsung/AT&T. If you look at other phones from Samsung and AT&T, there are very rarely updates to phones 2 years after the initial release of the phone. There's not really a good reason for this other than Samsung and AT&T want you to buy a new phone to get the latest updates. In the past you would need to get a new phone in order to have new hardware that is able to run the latest version of Android. But we're now at a point that nearly any phone released in the last 2-3 years can run nougat with minor lag. Manufacturers and carriers are holding on to the 2-year upgrade cycle and forcing you to buy new phones in order to get updates.
m44nu33l said:
I think it have to be because at this moment doesn't exist any way to intall a custom recovery as TWRP or CWM, if this is true, why nobody found the way to unlock the bootloader yet? in order to manage the custom recovery.
Click to expand...
Click to collapse
The i537 has a locked bootloader while the i9295 does not have a locked bootloader. Nobody has figured out how to unlock the bootloader on any variant of the S4.
m44nu33l said:
And why is so difficult to unlock it?
Click to expand...
Click to collapse
It's a very long read, but this thread explains exactly why it is so hard to unlock the bootloader. (http://forum.xda-developers.com/showthread.php?t=2500826)
m44nu33l said:
Which are the differences between this s4 version with the others?
Click to expand...
Click to collapse
As I stated above the only difference between the two versions of the Samsung Galaxy S4 Active (i537 vs i9295) is that the i537 has a locked bootloader and the i9295 does not. The i537 was sold exclusively through AT&T (US), Telcel (Mexico), and Claro (Uruguay), while the i9295 was sold internationally. Neither device will get official versions of marshmallow or nougat, but since the i9295 has an unlocked bootloader you can flash marshmallow and soon nougat custom ROMs. Other than the bootloader, the i537 and i9295 have identical hardware.
m44nu33l said:
And how can I help to unlock the bootloader, thanks in advance.
Click to expand...
Click to collapse
Honestly, unless you have a deep understanding of kernels, Linux, and cryptology, I'm not sure there's much help you can provide. The link I provided above explains all the effort that has been put into unlocking the bootloader. If you truly want to help I would read through that thread and see if there's anything meaningful you can provide.
Finally, if you don't ever want to have this problem again, always do your research and but a phone that has an unlockable bootloader. I purchased the i537 when it first came out only to find that the bootloader was locked and because of that I will never buy another phone with a locked bootloader again. Good luck.
Devo7v said:
I'm going to try to answer your questions one at a time:
There is not and never will be marshmallow or nougat for the i537. This is because it is outside the "2-year" update cycle of Samsung/AT&T. If you look at other phones from Samsung and AT&T, there are very rarely updates to phones 2 years after the initial release of the phone. There's not really a good reason for this other than Samsung and AT&T want you to buy a new phone to get the latest updates. In the past you would need to get a new phone in order to have new hardware that is able to run the latest version of Android. But we're now at a point that nearly any phone released in the last 2-3 years can run nougat with minor lag. Manufacturers and carriers are holding on to the 2-year upgrade cycle and forcing you to buy new phones in order to get updates.
The i537 has a locked bootloader while the i9295 does not have a locked bootloader. Nobody has figured out how to unlock the bootloader on any variant of the S4.
It's a very long read, but this thread explains exactly why it is so hard to unlock the bootloader. (http://forum.xda-developers.com/showthread.php?t=2500826)
As I stated above the only difference between the two versions of the Samsung Galaxy S4 Active (i537 vs i9295) is that the i537 has a locked bootloader and the i9295 does not. The i537 was sold exclusively through AT&T (US), Telcel (Mexico), and Claro (Uruguay), while the i9295 was sold internationally. Neither device will get official versions of marshmallow or nougat, but since the i9295 has an unlocked bootloader you can flash marshmallow and soon nougat custom ROMs. Other than the bootloader, the i537 and i9295 have identical hardware.
Honestly, unless you have a deep understanding of kernels, Linux, and cryptology, I'm not sure there's much help you can provide. The link I provided above explains all the effort that has been put into unlocking the bootloader. If you truly want to help I would read through that thread and see if there's anything meaningful you can provide.
Finally, if you don't ever want to have this problem again, always do your research and but a phone that has an unlockable bootloader. I purchased the i537 when it first came out only to find that the bootloader was locked and because of that I will never buy another phone with a locked bootloader again. Good luck.
Click to expand...
Click to collapse
Thanks for the explanation, what I will do is change my S4 for the international version in order to get the nougat custom rom.
m44nu33l said:
Thanks for the explanation, what I will do is change my S4 for the international version in order to get the nougat custom rom.
Click to expand...
Click to collapse
well my questions has really been answered , i guess we are never going to get an update , best option is to get a new phone
I have an SM-N910T running N910TUVU1COG2. I've kept it at this because I didn't what to lose the unlocked bootloader.
Is it possible to update my N910T with stock firmware without updating the bootloader? I've done it on other Android phones without any problems, but am clueless about the Note 4's ability to do so. What say you all?
Fat Rat Bastard said:
I have an SM-N910T running N910TUVU1COG2. I've kept it at this because I didn't what to lose the unlocked bootloader.
Is it possible to update my N910T with stock firmware without updating the bootloader? I've done it on other Android phones without any problems, but am clueless about the Note 4's ability to do so. What say you all?
Click to expand...
Click to collapse
No you cannot run 5.1 or 6.0 firmware/rom with 5.0 bootloader.
Trex888 said:
No you cannot run 5.1 or 6.0 firmware/rom with 5.0 bootloader.
Click to expand...
Click to collapse
Well, that totally sucks. Damn Samsung/T-Mobile. One of the main reasons I bought the phone was because it had an unlocked bootloader so that I could do as I will with it. It was bought out-right, unsubsidized, and I should be able to install what I want without worrying about the bootloader getting locked. So I guess I'm stuck at COG2 for a while longer, at least until my desire to keep the bootloader unlocked is overcome by my desire for new hotness.
Fat Rat Bastard said:
Well, that totally sucks. Damn Samsung/T-Mobile. One of the main reasons I bought the phone was because it had an unlocked bootloader so that I could do as I will with it. It was bought out-right, unsubsidized, and I should be able to install what I want without worrying about the bootloader getting locked. So I guess I'm stuck at COG2 for a while longer, at least until my desire to keep the bootloader unlocked is overcome by my desire for new hotness.
Click to expand...
Click to collapse
The Bootloader is still unlock on MM too...
KennyLG123 said:
The Bootloader is still unlock on MM too...
Click to expand...
Click to collapse
Are you certain? I thought that past COG2 T-Mobile locked the bootloader.
Fat Rat Bastard said:
Are you certain? I thought that past COG2 T-Mobile locked the bootloader.
Click to expand...
Click to collapse
If once you upgraded to marshmallow you can only downgrade to 5.1.1 OK1 but no 5.0 or 4.4.4.
But with 5.1.1 OK1 bootloader you can still flash 4.4.4 and 5.0 roms with custom kernels and they work flawless.
Fat Rat Bastard said:
Are you certain? I thought that past COG2 T-Mobile locked the bootloader.
Click to expand...
Click to collapse
Only revert lock. But if you are looking at rooting, recovery and flashing roms its not locked. I took mine to PE3 MM and left it there.....
OK, I'm confused.
Sorry to belabor the point, but I'm confused. If the bootloader is unlocked, then should I not be able to flash any ROM, Samsung's or not? i.e. I don't understand how the OK1 bootloader, if it's unlocked, will prevent me from flashing COD2. Or is it that the bootloader itself will not properly boot anything prior to OK1?
Can I install TWRP for the AT&T version with Nougat? I have heard that if I try it will brick. I'd really like to install a new ROM so I can get rid of all the crapware that comes with the phone.
Micah_Droid said:
Can I install TWRP for the AT&T version with Nougat? I have heard that if I try it will brick. I'd really like to install a new ROM so I can get rid of all the crapware that comes with the phone.
Click to expand...
Click to collapse
The 920A At&t cant be rooted as of yet and no twrp because the bootloader is locked...
Bootloader
I recently talked to at&t about getting my bootloader unlocked and a supervisor told me the only way to do so without bricking would be to being it in to an at&t store and they will unlock the bootloader.. anybody else have this told to them?
They're most likely taking about a Sim unlock not bootloader. Also there is a method for rooting it but you have to be on a specific bootloader and you can only use it on lolipop.
asislife20 said:
They're most likely taking about a Sim unlock not bootloader. Also there is a method for rooting it but you have to be on a specific bootloader and you can only use it on lolipop.
Click to expand...
Click to collapse
Ya, I know about that root method. Unfortunately, my phone decided to update itself a few weeks ago and now its on BL 5. So that's pretty much a no go.
In relation to bringing in the store for a BL unlock, I did specifically ask and made sure the tech I was speaking with knew the difference between BL and sim unlock. In fact, i made it very known that my radio was already unlocked, I done that weeks before i talked to her.