Full stock receiving an update today - AT&T Galaxy Note 3 General

I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.

Milkman00 said:
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Click to expand...
Click to collapse
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.

pre4speed said:
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
Click to expand...
Click to collapse
400 megs for Stagefright? That seems pretty big.

OC2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Milkman00 said:
400 megs for Stagefright? That seems pretty big.
Click to expand...
Click to collapse
Yeah it was 380 for the S5 too.

Thanks for the info. This was the only site that had ANY information about the update.

I'm on Lollipop, but Rooted. Will this update take away root by any chance?

My question exactly!

sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
Typically these updates do remove root. Best to wait until someone has a root method figured out for the new update.

sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
I just updated via the OTA method on AT&T. Rebooted twice. I still have root (verified by Root Checker). Here's my About page:
Here's the root checker pic:
I now have OC2. Update OTA with confidence!
I originally rooted OC1 (Lollipop) by following the Root/OC1 method.
EDIT: I just checked for stagefright vulnerability (via Stagefright detector). It reports that my device is NOT VULNERABLE. Nice.
I took the chance because this site has helped me in sooo many ways. It's the least I could do. Thanks everyone.

I'm rooted and my update failed at 26%
Sent from my SAMSUNG-SM-N900A using Tapatalk

Update failed for me at 25% too. I'm rooted OC1.

Does this update do more than just fix the stagefright exploit?
If not, then kmokhtar already posted a flashable update fix for stagefright which works great.

Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...

Why is this 'update' 5.0? I could have sworn it was just up to 5.1.1

KestrelX said:
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...stagefright-vulnerability-fix-note-3-t3175087

Can confirm that the update worked for me on rooted OC1, now shows OC2 and I retained full root on my phone.

ATT Ota file
https://mega.nz/#!TdE02KwJ!m4pkNivN9q2ZB7hGuXFiq872UoB8D-F-QpiPVX4sWI0

mine worked I am still rooted no problems no failure

peterson65 said:
mine worked I am still rooted no problems no failure
Click to expand...
Click to collapse
Those like me who have installed modded apps like S6 and have mixed in deodexed files, the OTA will fail. the OTA installer MD5 checks the system files and if any fail it will abort the Update. Any deodexed system files will also abort the Update
How to updated to OC2 if your OTA failed
1. Download and unzip and copy this Folder to OC1 stock root backup to your TWRP backup folder,
\TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Copy OC1 kernel recovery installer to your sdcard SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
*** You can also go ahead and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk and NC2 Flasher to your sdcard ***
3 Download the OC2 OTA 2400258.cfg
rename the 2400258.cfg OC2 to 2400258.zip and copy to your sdcard
4 Install the OC1 backup,
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip
5. Install OC1 Kernel
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
6. (I did a factory wipe , but Warning you will loose UserData settings and Apps you installed) You might try without but if you had a custom SystemUI and Touchwiz as I did it might FC because you have setting in Userdata pertaining to the Custom apps that you will over write with the OC1 backup.
7. Select Reboot and then select Recovery to boot to stock recovery and install as a update from external storage. mine installed with no issues.
8. To get safe strap back working Download and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk to sdcard (if you have not done yet)
9. Download and copy NC2 Flasher by benwaffle
10. Install Safestrap-HLTEATT-NC2-3.75-B03, run app and install recovery ( do not press reboot to recovery, it will only take you to stock recovery)
11. Install NC2 Flasher app and then use it to boot to recovery.
12. Do a backup of your new OC2
Now you can customized and do what you want

Related

[OTA] Stock XNPH25R OTA

Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
I'm getting binary update script error by flashing with TWRP
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.
iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.
housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO
Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app
truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.
fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.
ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?
Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk

OTA Update Thread - Discussion - CM11S [XNPH25R] -Updated on 4th July 2014

Hello guys,
New CM11S OTA Released ...
XNPH25R Incremental, -- FIX : NFC & Gyroscope.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I've unlocked the bootloader, instaled TWRP as recovery and rooted it, now, when the OTA message appears and I click on it, it reboot into recovery, but the updated is not performed... any idea how should I apply the update with the custom recovery?
Thanks
ICEM4N99 said:
Hi,
I've unlocked the bootloader, instaled TWRP as recovery and rooted it, now, when the OTA message appears and I click on it, it reboot into recovery, but the updated is not performed... any idea how should I apply the update with the custom recovery?
Thanks
Click to expand...
Click to collapse
Hi,
I've red in the Opo Forum that OTA currently only works with Stock Recovery or Clockworkmod Recovery, but not TWRP.
Greetz
Uludag
Uludag said:
Hi,
I've red in the Opo Forum that OTA currently only works with Stock Recovery or Clockworkmod Recovery, but not TWRP.
Greetz
Uludag
Click to expand...
Click to collapse
Take backup
1) do a full-wipe and try again..
2) do a full-wipe and install CM11S -- 22R freshly from fastboot and try... (install TWRP & root )
3) Try ota zip and flash... from
http://forum.xda-developers.com/oneplus-one/development/ota-stock-xnph25r-ota-t2804155
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
Uludag said:
Hi,
I've red in the Opo Forum that OTA currently only works with Stock Recovery or Clockworkmod Recovery, but not TWRP.
Greetz
Uludag
Click to expand...
Click to collapse
Not really , my opo is rooted and has TWRP , OTA was successfully installed through TWRP and the phone is still rooted
Make sure that "Update CM recovery" in developer options is unchecked and try again
king1990 said:
Not really , my opo is rooted and has TWRP , OTA was successfully installed through TWRP and the phone is still rooted
Make sure that "Update CM recovery" in developer options is unchecked and try again
Click to expand...
Click to collapse
I didn't even received my Opo, will hopefully arrive today :laugh:fingers-crossed: I just wanted to tell what I heard.
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I'm rooted unlocked and using TWRP and it worked fine for me...
Mnt-XDA said:
Hello guys,
New CM11S OTA Released ...
XNPH25R Incremental, -- FIX : NFC & Gyroscope.
Click to expand...
Click to collapse
Apparently, that's not all:
People who have received a OnePlus One through one means or another are now receiving an over-the-air software update that addresses a charging issue affecting the device. Sometimes the phone would think it's plugged into USB when it's actually plugged into AC power and, as a result, charge only half as fast, if not slower. The handset would display Charging (USB) instead of Charging (AC).
Click to expand...
Click to collapse
Source: Android Police
Seems to TWRP has been removed after OTA update. First time it run update with TWRP but update notification still stay in tray. And after second try it disappear but together with TWRP
Works for me too. Using TWRP as Recovery. Press the OTA update then reboot into Recovery Mode automatically and process the rest upgrade command
hi guys, i have a problem istalling this ota update... in the previous version i cancelled cclock app and now when i try to update it fails do to system cant find the app. i tried also to manually istall the app without result... so i cant update!!! anyone know hot to solve without flash the firmware?
thank you!
CafeKampuchia said:
Apparently, that's not all:
Source: Android Police
Click to expand...
Click to collapse
You are right .... Charger AC/USB bug is also fixed ... I have mentioned the same on my OnePlusOne Forum Thread.. yesterday
Mnt-XDA said:
You are right .... Charger AC/USB bug is also fixed ... I have mentioned the same on my OnePlusOne Forum Thread.. yesterday
Click to expand...
Click to collapse
I haven't received the update yet
Wish I hadn't taken the "update". My phone came rooted so I thought that was the default setting. This update killed root so I had the hassle of re-rooting my new phone. Also missing a few features now.

OnePlus One July OTA Update Android 4.4.4

Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689

[OTA][LXB22.99-16] [India] stagefright patch update

Hello guys this ota update for our motor g 2014.
This include only stagefright security patch and other bug fix.
This is not android 5.1 OTA update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/0ByxugVLkdzFgOElCbWxDeTJidkk/view?usp=docslist_api
This is cool, thanks! Can this be installed on xt1068 btw?
If it is for XT1068, shouldn't it be named "Blur_Version.22.21.28.titan_retaildsds.retaildsdsall.en.03.zip"?
Because, the zip files are normally named by the Version Number they are for. In this case, was your Build 22.41.16? Mine is 22.21.28
demothon said:
This is cool, thanks! Can this be installed on xt1068 btw?
Click to expand...
Click to collapse
Yes this is for xt1088
Didn't work for me. Guess it is because I am on 22.21.28 I downloaded, placed it in Internal Storage, checked for updates, didn't get it. Rebooted, still didn't.
I tried it also via recovery, it says It's for an other build (99.16)
Yep, so won't work for 22.21.28, as it is mentioned in the zip file "22.41.16". (The Zip files are named after the version that they are for, NOT the version the update contains).
me too at 22.21.28 waiting for this stage fright patch .....?
Sri2702 said:
If it is for XT1068, shouldn't it be named "Blur_Version.22.21.28.titan_retaildsds.retaildsdsall.en.03.zip"?
Because, the zip files are normally named by the Version Number they are for. In this case, was your Build 22.41.16? Mine is 22.21.28
Click to expand...
Click to collapse
Yes mine is 22.41.16
Guys try to put zip file in root of SD card if internal storage not working.
vikasb32 said:
Guys try to put zip file in root of SD card if internal storage not working.
Click to expand...
Click to collapse
it will fingerprint check that you have right version of 5.0.2 installed if not it wont install
vikasb32 said:
Guys try to put zip file in root of SD card if internal storage not working.
Click to expand...
Click to collapse
Well, it won't work for 22.21.28 users regardless.
Manual INSTALLATION of STAGE FRIGHT patch
Right this is how to install for ANY GLOBAL XT1068 running LXB22.99-16 Retail / Now working with Brazil LXB22.99-16
LXB22.99-16 is build number for the rom with system version 22.41.16 - THEY ARE ONE AND THE SAME.
You need to update to 5.0.2 LXB22.99-16 STOCK ROM to have the correct RECOVERY or this patch will NOT even start to install - it will also check system version when installing
I have been told you must be UNROOTED or phone hangs on boot logo once patch applied.
These 2 things are therefore are a must, STOCK OEM motorola Recovery (LXB22.99-16) and UNROOTED phone.
1) you must be on LXB22.99-16 this was the latest FULL version of 5.0.2 feb 25th - ALL xt1068's can run this - as it has drivers for BOTH types of front cams. ( Brazil has it own version of LXB22.99-16 )
2) copy the blur_version.zip to internal storage on XT1068 - pick correct one from attached files below
3) forget going to settings and checking for software - it wont show
4) reboot into AP fastboot mode then use vol down to select recovery and volume up to select you should see after a small wait with black screen a fallen android with red triangle - then hold power and quickly tap vol up - you should now be in recovery
5) choose apply update from sd card then choose blur_version xxx.zip
6) it will install if you are on correct lXB22.99-16
the new version is LXB22.99-16.3 system version 22.56.3.titan_xxxx released wed august 26th and yes still 5.0.2
Mine also 22.21.28
amritmalviya said:
Mine also 22.21.28
Click to expand...
Click to collapse
update to full oem rom LXB22.99-16 then apply patch or wait for ota for your version
Stagefright patch by Motorola means disabling MMS, can someone confirm that?
zman01 said:
Stagefright patch by Motorola means disabling MMS, can someone confirm that?
Click to expand...
Click to collapse
no idea not sent a MMS message for years - outdated - I use whats app / snap chat etc
what about rooted device? 1068 (bootloader unlocked)
is there any manual way to install?
as you said "I have been told you must be UNROOTED or phone hangs on boot logo once patch applied." (BOOTLOOP?)
hacker1911 said:
what about rooted device? 1068
is there any manual way to install?
as you said "I have been told you must be UNROOTED or phone hangs on boot logo once patch applied." (BOOTLOOP?)
Click to expand...
Click to collapse
yes flash LXB22.99-16 to restore to stock OR unroot your phone manually and then apply patch - you can root again after
reefuge said:
yes flash LXB22.99-16 to restore to stock OR unroot your phone manually and then apply patch - you can root again after
Click to expand...
Click to collapse
if i flash this now directly on the rooted device will there be any problems?
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
btw bootloader unlocked and then rooted

[n910t] n910tuvu2epj2 - october security patch

I just got a 250 MBs update on my galaxy note 4 N910t.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910T using Tapatalk
http://www.sammobile.com/2016/10/23...nance-update-for-the-galaxy-note-4-in-europe/
I took the plunge. It's a lot less buggy and battery drain is not near as bad. I almost sold this thing.
Rootable?
Cf auto root?
Sent from my SM-N910T using Tapatalk
ubigred said:
Rootable?
Cf auto root?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Systemless root works fine for me.
Uploading the tar to AFH will update the other thread.
DeeXii said:
Uploading the tar to AFH will update the other thread.
Click to expand...
Click to collapse
did u upload Oct MM security patch firmware upfate I wanna flash it on my t910w8 Canadian.....waiting for it thanks
MDHACK said:
Systemless root works fine for me.
Click to expand...
Click to collapse
Would you please give a quick description of the process/tools you used to accomplish this so that others may duplicate your success?
Also, what recovery are you using?
Thank you.
Fat Rat Bastard said:
Would you please give a quick description of the process/tools you used to accomplish this so that others may duplicate your success?
Also, what recovery are you using?
Thank you.
Click to expand...
Click to collapse
1. Update through OTA or flash Odin files.
2. Flash TWRP through Odin.
3. Flash latest Chainfire's SuperSu Systemless root on TWRP.
4. Enjoy!
https://www.androidfilehost.com/?fid=385035244224387215
Has anyone ever updated while they had an app like EZ Package Disabler installed with the apps disabled? I updated this morning and forgot to enable the apps before the update. It's working fine right now, just wondering if there would be a problem since the app says to enable apps before doing an update.
I just tried to flash TWRP using Odin. After restarting the phone, I went to android recovery mode instead of TWRP. What did I do wrong there? Please help!
buidoitieutu said:
I just tried to flash TWRP using Odin. After restarting the phone, I went to android recovery mode instead of TWRP. What did I do wrong there? Please help!
Click to expand...
Click to collapse
After flashing twrp dont let the device reboot. The stock recover overwrites twrp. In odin uncheck reboot then after the twrp install you have to boot to recovery Vol+ home and power..
buidoitieutu said:
I just tried to flash TWRP using Odin. After restarting the phone, I went to android recovery mode instead of TWRP. What did I do wrong there? Please help!
Click to expand...
Click to collapse
In Odin, visit Options tab, and uncheck Auto Reboot before Starting.
j21098 said:
Has anyone ever updated while they had an app like EZ Package Disabler installed with the apps disabled? I updated this morning and forgot to enable the apps before the update. It's working fine right now, just wondering if there would be a problem since the app says to enable apps before doing an update.
Click to expand...
Click to collapse
I freeze my apps using Titanium Backup, and I have never activated them before an update
Hi everyone, I installed this and issue arised, my system settings went to default rather than my customized settings.
But started to realize that my quick charge isn't working anymore (at least doesn't show a notification saying the fast charge is connected) and also no more vibrations for my touch light keys (back and switching apps buttons) when I touch them.
Pretty annoying, anyone has these issues and know how to fix these? Thanks
MDHACK said:
1. Update through OTA or flash Odin files.
2. Flash TWRP through Odin.
3. Flash latest Chainfire's SuperSu Systemless root on TWRP.
4. Enjoy!
Click to expand...
Click to collapse
I am using same firmware, but can't seems to root it using Systemless root on TWRP and Auto CF root... Any step by step guide on how you did it?
Anyone who has Android 6 on the N910T, could you please see if they have the language PORTUGUESE BRAZIL?
I cant get an 'adb shell' on the device. It says "error: device unauthorized. Please check the confirmation dialog on your device"

Categories

Resources