When I first got the N6 in June I immediately unlocked the bootloader and flashed CyanogenMod 12. Now I remember reading beforehand that if you updated your device to 5.1 via the factory images or OTA, that the bootloader cannot be downgraded anymore. I made sure to not do this so my N6 is on the very first bootloader still and I haven't had any issues.
Now, I feel like I read that there was a reason to want to downgrade and a reason for not wanting this new bootloader but I can no longer find any information on this whole topic, other than people saying yo ucannot downgrade.
I'm asking if there are potentially issues if I do update or if it's ok to stay on my current old bootloader when I update to 6.0 soon?
admiralspeedy said:
When I first got the N6 in June I immediately unlocked the bootloader and flashed CyanogenMod 12. Now I remember reading beforehand that if you updated your device to 5.1 via the factory images or OTA, that the bootloader cannot be downgraded anymore. I made sure to not do this so my N6 is on the very first bootloader still and I haven't had any issues.
Now, I feel like I read that there was a reason to want to downgrade and a reason for not wanting this new bootloader but I can no longer find any information on this whole topic, other than people saying yo ucannot downgrade.
I'm asking if there are potentially issues if I do update or if it's ok to stay on my current old bootloader when I update to 6.0 soon?
Click to expand...
Click to collapse
You couldn't downgrade from a 5.1 bootloader to a 5.0 bootloader, because the 5.1 bootloader brought some new security features in. I don't know of any reason why you would want to downgrade the bootloader.
There is no reason to not upgrade it either, though as far as I am aware, 6.0 will work with a 5.1 BL, just don't think it will work with a 5.0 one.
I see, thank you!
Related
Okay, I have to ask. Has anyone successfully downgraded a 4.4.4 KitKat Moto X (2013) to a previous firmware version?
I have the XT1058 "ghost" if that matters.
Seriously? This has only been covered nearly everyday since 4.4.2 became available. In other words, the answers are out there if you simply open your eyes or search.
No not possible to downgrade from 4.4.4
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Darth said:
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Click to expand...
Click to collapse
This is the info I wanted. Thanks.
Hi, my phone is xt1056, BL unlocked, I was fully flashed (enabled all the options in the xml file) the ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4 once.
Then I fully flashed my xt1056 with the xt1060 rom (VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml) in rsd. Now the phone is 4.4.2 and no signal, but it is 4.4.2, I can get my SPC with the app SPCUtility.apk.
After get my SPC, I was fully flashed the xt1056 (ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4) again and works well (need to unlock the network again).
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Downgrading with an unlocked bootloader is no different than locked... Extremely dangerous.
And the poster above who downgraded, then upgraded again... I would not take any OTA's going forward. Or you might get an unfortunate surprise.
DarkWolffe said:
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Click to expand...
Click to collapse
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
KidJoe said:
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
Click to expand...
Click to collapse
Perfect answer. Thank you for the clarity.
Long story short, I received the Lollipop update today only for it to say "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone....etc."
When I first got the phone it was from AT&T and thus had all the standard bloatware, etc. After tinkering around with rooting/unlocking I decided to convert it to the unlocked edition. I believe it is S-Off, and the Boot loader is unlocked, HBOOT-1.57.0000 with everything else pretty much unchanged. I'm still on AT&T currently if it helps. I've read that the bootloader needs to be locked in order for OTA updates to work properly?
I haven't rooted or tinkered with anything for months and so I've pretty much forgotten everything about it although I can catch up again pretty quickly. Apologies if the fix is something simple. I'd basically just like to be able to update to official stock Lollipop and stick with it.
mch277 said:
Long story short, I received the Lollipop update today only for it to say "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone....etc."
When I first got the phone it was from AT&T and thus had all the standard bloatware, etc. After tinkering around with rooting/unlocking I decided to convert it to the unlocked edition. I believe it is S-Off, and the Boot loader is unlocked, HBOOT-1.57.0000 with everything else pretty much unchanged. I'm still on AT&T currently if it helps. I've read that the bootloader needs to be locked in order for OTA updates to work properly?
I haven't rooted or tinkered with anything for months and so I've pretty much forgotten everything about it although I can catch up again pretty quickly. Apologies if the fix is something simple. I'd basically just like to be able to update to official stock Lollipop and stick with it.
Click to expand...
Click to collapse
Read this, I did this last night and got lollipop, as your s-off and on "unlocked" edition anyway, this will be4 easy for you: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311
Ah, thank you! That worked flawlessly.
Hi Noob question here, I don't want to root or flash my Nexus 6, I bought it from a guy 2nd hand and he had flashed various roms. He restored it to stock android before selling it to me - It has the unlocked padlock on boot - Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1? Will there be any danger of bootloop?
What should I do?
@Darius,
Unlocked bootloader has no effect on installing OTA.
Yes, there's always a risk of bricking if you don't follow the directions precisely. There are several "how to" threads. Read, understand, and ask questions.
Whatever you do, relocking the bootloader is probably not the answer ?
Sent from my Google N6 on VZ
Darius said:
Hi Noob question here, I don't want to root or flash my Nexus 6, I bought it from a guy 2nd hand and he had flashed various roms. He restored it to stock android before selling it to me - It has the unlocked padlock on boot - Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1? Will there be any danger of bootloop?
What should I do?
Click to expand...
Click to collapse
If the device is completely stock (including recovery), you should be able to take the OTA. Unless there is something wrong with your device hardware, I don't see any risk. It is just a regular OTA you get from google, direct to device, and you just apply it. Just make sure your phone has a full charge, and don't interrupt the update process.
As a precaution, you should back everything up - never say never
Oh, and to second what DebianDog wrote, don't lock your bootloader
Thanks for all the tips guys, applying update right now...
I have been trying to upgrade my Sprint Nexus6 for the last 3 days. the download goes well the install gets halfway through the blue line under the Android and then he lays down with an "Red Error"
boot loader unlocked and rooted running Stock 5.01. suggestions of the log files i should pull to help narrow this down?
myopic said:
I have been trying to upgrade my Sprint Nexus6 for the last 3 days. the download goes well the install gets halfway through the blue line under the Android and then he lays down with an "Red Error"
boot loader unlocked and rooted running Stock 5.01. suggestions of the log files i should pull to help narrow this down?
Click to expand...
Click to collapse
Nothing needed to narrow it down - you cant take the OTA if you rooted -> because rooting installs SU -> which changed your /system partition -> it no longer matches what the OTA looks at -> and it will fail, sorry.
Unroot it and you might try it again, or you would have to re-flash a stock image to be clean and then take it. The bootloader being unlocked is not the cause.
I have an xt1058 which is running Android 4.4.0 build 140.44.5.ghost_att.ATT.en.US. I've downloaded and installed Sunshine and am planning to unlock the bootloader as all tests passed without issue. What I am wondering is, after I do this can I take any OTA updates or will this cause me to lose the bootloader unlock?
Of particular concern is incompatibility between older versions of the bootloader and ROMs based on newer Android versions. I ran into this with my Atrix HD which also had an unlocked bootloader. The bootloader on that device was based on Android 4.3 Jellybean. I could not flash any ROMs for MSM8960 devices which used newer bootloaders, for example I always needed to use CM versions with Jellybean bootloader.
Will I have similar issues with my Moto X once the bootloader is unlocked?
Thanks!
No issues, flash latest XT1058 AT&T ROM, and you are in safety. Once unlocked, bootloader can't be locked by any app, but your hands. And there will be no more OTA for this phone.
Btw, you can use Safestrap (for free) on Android 4.4, it will give you possibility to use any stock ROM up to 4.4.4. If you need CM, or 5.1 stock, then yes, Sunshine only.
Just to be clear, I have now successfully unlocked my bootloader using Sunshine (I see the "warning bootloader unlocked" splash at boot up, and have also booted into bootloader and I see "device is UNLOCKED".
I am currently on build 140.44.5.ghost_att.ATT.en.US which is Android 4.4.
Ultimately what I want to do is get rooted but be running stock 5.1. I don't want to go to a custom ROM right now, but don't want to do anything that would prevent me from doing that later. That's why I unlocked the bootloader now.
I am planning to use this process to root the phone:
https://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Once this is done, what is the easiest way to move to stock Android 5.1 but not lose root and bootloader unlock/s-off ?
My advice would be - don't update to 5.1 official, it's very very buggy and you'll want to get rid of it very fast.
The best you can do for this phone atm, if you want anything above 4.4 is to go for Mokee 6. It's nearly perfect MM.
Hi, I am currently using CM13 on Android M because I wanted Xposed. Recently, I have planned to switch to The Pure Nexus ROM for Android N, but I have been told something disheartening. I was told if I update my bootloader to Android N latest from Google, I will not be able to downgrade the bootloader because it can cause it to brick. Since my backups are for CM13, would I not be able to restore them through TWRP with the new Android N bootloader?
Bootloaders are backwards compatible. The 7 bootloader should work as far back as 5.1.1. You're right though, don't downgrade the bootloader.