[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
- How to roll back to KK topic
- What is this in Greenify settings topic
- [Q] How to update? topic
- [ROM] ViperOneM9 1.1.0 Tweaks | HUB | Themeing | OTAs TMoUS, AT&T, Sprint topic
- A statement of fact about non AT&T service and OTAs topic
- [Q] Is it possible to take pictures on a Lollipop 5.1 Rom?? topic
- "Can I have your IMEI?" Mod please take action. topic
- OTA Lollipop from NK1 - To take or not to take? topic
- can't take screenshot topic
- Long press back to take a screenshot topic
- Tap anywhere on screen to take photos?? topic
- OTA won't take topic
- [Q&A] [10.03][XPOSED FIX] Samsung DVFS Disabler! - Take the full power of gs4 topic
- How to take screenie shot? topic
- [Q] upgrading to lollipop?? topic
- Trouble upgrading hboot - S-Off topic
- Is Lollipop really worth upgrading to? topic
- Android is Upgrading... Starting apps on EVERY BOOT. (CM12 Lollipop) topic
- [Q] Upgrading to lollipop / unlocked / rooted /xposed working /deodexed topic
- Service issues after upgrading to 5.0 topic
0 commentaires:
Enregistrer un commentaire