[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop topic
If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for the Verizon Samsung Galaxy Note 4 (N910V):
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.
xda-developers
- [Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop topic
- Htc desire 816 official lollipop update video review topic
- [Q] LG G2 Lollipop 5.0.2 V30A - NO ART topic
- [Q] Lollipop Notifications Color messed up topic
- [Q] Lollipop by HTC ? topic
- Lollipop - Which Countries have the OTA and who is next? topic
- Dell Venue 8 7840 Android 5.0.1 Lollipop OTA topic
- [Q] Lollipop! topic
- G2 Lollipop usb cable issue topic
- Lollipop screen off animation and double tap missing!!! topic
- To disable heads-up notification in lollipop topic
- Is root required to roll back to KitKat? topic
- [REQ] Multi DPI Stock Camera topic
- May be this is it for Xperia J topic
- [Q] No IMEI and baseband anymore. So back to stock rom for repair! topic
- [Q] New to phone - on 24A rooted - where to go from here? topic
- [Q] Galaxy S6 Edge T-Mobile Unlock by SIM code topic
- How to roll back to KK topic
- What is this in Greenify settings topic
- [Q] How to update? topic
0 commentaires:
Enregistrer un commentaire