yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nightsbird:
RSI Repair (Samsung authorized service center) Couldnt repair it.

Samsung blamed AT&T and AT&T blamed Samsung. Turned them in as claims to mobile insurance. Galaxy S3 no longer stocked so Mobile insurance gave me 2 Galaxy Alpha's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
LOL...typical. Neither one takes responsibility. From my understanding of the way the process works with these updates, it would be AT&T at fault since they have to "test and approve" any updates given by Samsung. Of course they will never admit to being at fault.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrossBones3129:
How can I disable OTA Update? Also anyone else have play store download a ota security policy?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
I have used TiBu in the past to stop updates by freezing the software update function in stock based ROM.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
I used an app from the Play Store called "My Backup Root" to freeze the update. You can also freeze the security policy updates which is a part of KNOX and/or SELinux I gander.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrossBones3129:
Dang i had to use titanium backup pro. Wish I could have found a free one before paying $6 to stop the notification. Idk what Titanum Backup even does
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
My Backup Root is a free app on Google Play Store. Always good to have Titanium Backup Pro though, as it lets you backup all your apps and pretty much anything on the software side of your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sketch2k278:
what's so special about this update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattsternc:
Nothing really special about it. From what I've read and put together through the reading here, it gives you the following:

Removes root access

Updates the bootloader

Updates the modem firmware, which according to a couple of posts, makes things a little bit better in terms of call quality and signal strength

KNOX updates

Other than those things, I don't know that it really does much of anything else. I'm on the fence as to whether or not I will update, as it seems the only way to do it from the state I am in now is to use ODIN and a rooted ROM from another thread. I may tackle that this weekend if I have time, but I was going to wait and see what others were doing for a bit longer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
I'm staying on NE4 where towelroot still works and knox isn't updated. I could use the slightly better call quality and signal strength though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Your money was not wasted. Worse case scenario is that you supported a very talented group of devs. TiBu has been my go to app after flashing many ROMs to restore my apps successfully. Paid version includes scheduling backups as well so your backups are always up to date and ready to restore. Look into the app. Many will concur that it is a must have.

Sent from my SGH-I747M using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I second you 100% Tibu is life saver.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epiel:
I want this update, please share the link, to download
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YasharF:
See the posts in the forum for the ROM image and upgrade: xda-developers -> AT&T, Rogers, Bell, Telus Samsung Galaxy S III -> AT&T Galaxy S III General
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vbetts:
If you lose root, it's easy to get back.

It will trip your counter though, if that doesn't matter to you then just go on with this method of root.

Towelroot doesn't work on the new firmware, so I ended up flashing a custom recovery through odin and installing SuperSU in recovery.

I haven't flashed any roms yet, but I believe you can just change the build prop to target the new firmware instead of the old.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitjasen:
I747M Stock Firmware Question

I have Rogers i747m with stock 4.4.2 installed. I was thinking is it possible to install for example stock firmware from SaskTel or Koodoo? Does it matter? Ive noticed that on sammobile they released newer versions firmware but not for Rogers. So I make full format and put on firmware from a different company? Will this work?
[Nexus 7 (2013) Q&A] cabadam:
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.

I downloaded the OTA zip and have tried to install it in 2 different ways:

In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"

From TWRP on the device, going to Install, and selecting the downloaded zip.

In both cases, I get the same error:

I'm not real sure what that error means, or how to go about addressing it. Any suggestions?

Thanks
[Nexus 7 (2013) Q&A] SwoRNLeaDejZ:
You can't flash the OTA in TWRP, at least I don't think so, but I do know that 5.0 requires the latest version of TWRP, think it's 2.8.1.0

Sent from my 2013 Nexus 7

"Until death, I will remain a Dirty Unicorn.."
[Nexus 7 (2013) Q&A] cabadam:
Tried updating to TWRP 2.8.1.0, I couldn't even get adb to recognize the tablet when in sideload. Just gave me device not found.

But, based on your other comment, I grabbed Wug's Nexus Root Toolkit and reflashed the stock recovery. Sideload is now in progress, I think I'm good to go (I probably just jinxed it!)

Thanks a lot for the help. I had thought it would just replace the recovery - I didn't realize that actually prevented it from running.
[Nexus 7 (2013) Q&A] nhizzat:
Update TWRP in bootloader. Fasboot flash recovery recovery.img
[Nexus 7 (2013) Q&A] jj14:
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.

You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
[Nexus 7 (2013) Q&A] cabadam:
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
[Nexus 7 (2013) Q&A] jj14:
Weird - did you modify your build.prop for any reason?
[Nexus 7 (2013) Q&A] cabadam:
Nope. When I got the tablet, I rooted it, flashed TWRP, but didn't modify anything else. And basically the root was just so I could do full backups.
[Nexus 7 (2013) Q&A] ImjuzCY:
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
[Nexus 7 (2013) Q&A] edbogue:
Build fingerprint error when flashing 5.0 OTA via stock recovery

Hello!

Really want to flash the OTA without a total wipe.

First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136

Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.

I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys

Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!

Thanks for any and all help!

Edbogue
[Nexus 7 (2013) Q&A] yogurt eater:
Same problem

Hey guys!

I have the exact same problem as OP.

tried installing the zip using the latest version of TWRP and got the same error as OP.

I reverted back to stock recovery and tried to install the OTA update and I got a similar error (image attached).

I'm stuck, could someone help?

Rooted Nexus 7 2013 running 4.4.4 with TWRP 2.8.1.0
[Nexus 7 (2013) Q&A] bwat1009:
Same here. Build.prop has the desired release keys but cwm is giving me the exact same error. Anyone have any suggestions?
[Nexus 7 (2013) Q&A] ahmao:
open the zip file,

edit META-INF/com/google/android/updater-script

just comment the following three lines:

#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||

# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||

# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");

then the update will go through.

you will take this workaround at your own risk.

make sure the version is 4.4.4/KTU84P already.
[Nexus 7 (2013) Q&A] hokuto34:
You need to be in kk stock with all apps from Google. !

I used NRT with sideload and no problem to flash 5.0 !
[Nexus 7 (2013) Q&A] yogurt eater:
ahmao, when you say comment you mean this

/*comment goes here*/

as they do with CSS?
[Nexus 7 (2013) Q&A] bwat1009:
As suggested, I tried that. Commented out the lines. Now when trying to flash it just says "Installing Update" then "Installation Aborted" gives no further details. Thanks for the suggestion though.
[Nexus 7 (2013) Q&A] fruity101079:
I had same problems on n4.

I tried flashing stock recovery. Doesn't work. So, I flashed the whole stock 4.4.4 rom, and then apply the Ota. And it worked.

But I had to wipe my user data. (maybe not necessary)

Envoyé de ma Nexus 7.2 depuis tapatalk
[Nexus 7 (2013) Q&A] bwat1009:
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
[Nexus 7 (2013) Q&A] ahmao:
comment means add a hash "#" in front of the script line.

if further check fails, just find the line and comment out the app_check line.
[Nexus 7 (2013) Q&A] yogurt eater:
Thanks man!

That worked perfectly!

I lost all my data (which is fine) plus I really needed to start from scratch at some point.

I'm trying to install TWRP custom recovery, but it seems to be crashing all the time.

Does TWRP support Android 5.0 yet?
[Nexus 7 (2013) Q&A] SwoRNLeaDejZ:
Do you have TWRP 2.8.1.0? Required to work in lollipop.
[AT&T Samsung Galaxy Note II] tailgunner9:
Check for OTA Update in your settings. :o
[AT&T Samsung Galaxy Note II] nicoled985:
Is it Lollipop?
[AT&T Samsung Galaxy Note II] DroidTuner:
I don't think so. I think it is a security update.

I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
[AT&T Samsung Galaxy Note II] dicksteele:
Update the Software for the Samsung Galaxy Note II (i317)

Update summary

AT&T released a new software update for the Samsung Galaxy Note 2 (SGH-i317) via Firmware Over the Air (FOTA) over Wi-Fi on November 11, 2014.

Software Update Includes

Android OS Enhancements

User-Initiated Software Update

From the Home screen, press the Menu key.

Tap Settings.

Tap the More tab.

Tap About Device.

Tap Software update.

Tap Check for updates, and then follow the subsequent prompts.

Verifying the Update

From the Home screen, press the Menu key.

Tap Settings.

Tap the More tab.

Tap About Device.

The following information displays:

Android version: 4.4.2

Baseband version: I317UCUCNJ1

Kernel version: 3.0.31-1728680 dpi@SWDD5922 #1 Wed Oct 1 22:38:36 KST 2014

Build number: KOT49H.I317UCUCNJ1

File size: 93.2MB
[AT&T Samsung Galaxy Note II] keplenk:
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.

What do you think guys?
[AT&T Samsung Galaxy Note II] a042349:
I wouldn't. I just posted this in the other thread about the OTA:
[AT&T Samsung Galaxy Note II] kabinoff:
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.

New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
[AT&T Samsung Galaxy Note II] melvinaury:
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
[AT&T Samsung Galaxy Note II] kabinoff:
actually flashed CF with Odin and it worked.
[AT&T Samsung Galaxy Note II] selw0nk:
Did it really work?
[AT&T Samsung Galaxy Note II] toshik1:
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?

I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).

If I stick working AT&T SIM card and check for updates it says the device is up to date.

Moreover if I'd connect it to Kies it would also say that firmware is up to date!

Same thing on both phones - what am I missing?

I purchased them used - maybe the previous owners rooted them and this prevents them from updating?

One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
[AT&T Samsung Galaxy Note II] Zen Arcade:
Is service activated on the AT&T SIM? That might be a factor.

Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
[AT&T Samsung Galaxy Note II] toshik1:
Yes the SIM card has normal active service on it.
[AT&T Samsung Galaxy Note II] Zen Arcade:
Other reasons OTA won't work:

1 - Location (if you are not in an area where OTA updates are provided, then...

)

2 - AT&T Update apk disabled on phones (seems unlikely that this would be the case on two phones but a factory reset might clear this as it is set on the data side)

3 - Identity issues (could be any number of things related to IMEI, efs partition scrambling, etc - just spitballing)

As far as suggestions go, I'd say try a factory reset and clear cache from recovery. If that doesn't work, maybe go back to AT&T and see if they can figure it out - the phones are stock and it's their OTA process. If that doesn't work, you can pursue the path I suggested previously - same firmware update, minus the script that pushes stock recovery every time you boot. You will trip the knox flag though...only an issue for warranty repair really. Others here have intentially or unitentionally received the NJ1 OTA with the knox flag tripped on their phones.
[AT&T Samsung Galaxy Note II] tacarat:
Which process did you freeze?
[AT&T Samsung Galaxy Note II] toshik1:
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for :)

Got 4.4.2 I317UCUCNE5
[AT&T Samsung Galaxy Note II] Zen Arcade:
Glad to hear it. Wait a day (or disable network time and the set the time on the phone forward at least a day) and try again - you should get NJ1. (If that's what you want). ;) Approx. 93MB security and minor enhancement update.
[AT&T Samsung Galaxy Note II] toshik1:
Just to follow-up - it took the second update with T-Mobile SIM card even without waiting for 24 hours.

I guess in order to take the updates the phone's IMEI MUST re-register on AT&T network with the valid AT&T SIM card first.

It's now I317UCUCNJ1
[JASJAR, XDA Exec, MDA Pro General] flummie:
Hi,

ActiveSync on my Universal is not working. When I connect to desktop (xp.s2) AS on desktop (4.5 b2) connects but under 'tools' everything is greyed out but 'add remove programs' and 'explore device'.

When I explore device I can see the files on it but can not copy files to or from it. 'Add remove programs' has same problem. I get message like: 'connect to device/is device writeprotected?/do you have the rights?'

AS on device says something like: connect to desktop to sync. But desktop says I'm connected!!

I can't install backup program to backup contacts. I can't copy backupprog to device to install.

Btw: have tried to disable firewall but same result.

Hope some1 has a cunning plan?? Idears are very welcome!!

Cheers. Flummie
[Verizon Samsung Galaxy S III] guy with phone:
HELP soft bricked my verizon galaxy s3, last i knew it was running 4.4.2, i can still get to download mode, ive been looking for the odin file for the past 2 hours, cant find it. if anyone can point me in the right direction that would be great.

:)
[Verizon Samsung Galaxy S III] ShapesBlue:
What were you trying to do? Being that your on a locked bootloader you can only flash safestrap and BL roms

From my CM11 S3
[Verizon Samsung Galaxy S III] cyberkeeper1:
I have it. I'll shoot one to dev-host later today when I am able. :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
VRUDNE1 4.4.2. And here's a separate link as well.
[Verizon Samsung Galaxy S III] 05JSamide27:
soft bricked my s3

I have a galaxy s3 i535 which was upgraded to kitkat 4.4.2. I was attempting to revert back to 4.1 when i bricked my phone. I can get into odin mode, but I cannot get any files to complete with odin. upon trying to flash the 4.1 rom i got a screen which had a picture of a phone....yellow triangle exclamation....computer and told me to use a repair something or other. I needed a phone so i pulled the main board out of another s3 and was able to get a working phone. I am able to boot into download mode.

any help would be great. I am a noob. and im pretty sure that I didnt have usb debugging enabled when i attempted to flash the rom.
[Verizon Samsung Galaxy S III] ShapesBlue:
You cannot downgrade once your on the locked bootloader. All you can do is flash TW bootloader locked roms at this point. You'll have to just Odin back to stock

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] j831:
I can't seem to restore anything using TiBu Test Version after I updated to Android L. It always get stuck at 0% when I try batch restore. And if I try to restore a single app it still gets stuck until I force close the app.

I tried changing the backup directory to emulated/legacy/TitaniumBackup instead of emulated/0/TitaniumBackup and still not working. Any ideas?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Did you follow the pop up and enable USB debugging? I didn't have to do this on the Dev Preview, but this was driving me mad today. Just sat at 0% forever until I set the USB debugging on and rebooted. It was ok after that
[Nexus 5 Q&A, Help & Troubleshooting] j831:
I did set USB debugging on, and still didn't work.

I don't know, TiBu has just been wonky for me. I also lost all my labels for some reason.
[Nexus 5 Q&A, Help & Troubleshooting] Utacka:
Dont know if this will help but which test version do you have? Ive had identical issue with test5 which was fixed by using test6 on the preview. Test6 also worked flawless for me on the latest L release.

TitaniumBackup_6.2.0-test6_r343_Market.apk is the apk I used.

Skickat från min Nexus 5 via Tapatalk
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
You may also need the permissive kernel / pie patch. I can't say for sure as I already have that and it works
[Verizon HTC One (M8)] jbaroz:
Ever since the OTA upgrade to 4.4.4 and the new camera, I've been experiencing an issue where shortly after taking a picture with the stock, it will become corrupted and replaced in the gallery by a grey triangle icon with an exclamation point. This only seems to affect pictures on the SD card. I switched it to save pics to the phone and they don't seem to be corrupted like the pics saved to the SD card are.

Has anyone else experienced this, or have any ideas what could be causing this or how to fix? Thanks!
[Verizon HTC One (M8)] dottat:
Do you have kitkat SD card permissions set right? By default they don't really work right.
[Verizon HTC One (M8)] jbaroz:
Complete stock so I haven't touched the permissions. Unrooted as well so not sure if it's possible for me to do this either.

Thanks for the response!
[T-Mobile Samsung Galaxy S 4] vipercoyote:
So basically with my backup phone S4 it dropped on its side with the case on it. Now the screen is not responsive to my touches at all.

Glass is not cracked. Up under glass in top left hand corner i can see small spider web. Along left side of the phone there is a grey,green and red thin lines.

I know my option is to replace the lcd, digitizer and screen all in one piece but for the price and repair trouble Im thinking of just buying a BAD ESN S4 off ebay that have a perfect display and just swap the motherboard from my phone to the phone I buy on Ebay and put the Ebay phone motherboard into my backup S4 and then sell that phone on ebay to get some of my cash back

My question is, can I use any S4 to do this? Will the tmobile motherboard work with any S4 meaning will it fit? is there any differences in the build?
[Nexus 7 Q&A, Help & Troubleshooting] .TanTien:
Hey guys,

a few hours ago I tried flashing the new Ldroid Rom onto my Nexus 7. After flashing the rom my tablet took ages to boot up and after the bootup it said i had to enter a password to encrypt the data (i never set encryption). after entering a random password android reported that the password was right but the data corrupt and i'd have to do a factory reset. after entering twrp i realized that the device couldn't mount anything except system. i wiped/formated everything except system and tried booting into android. this time i was stuck at the google logo. after entering recovery mode again now twrp couldn't mount system and sdcard. so i formated both and now i'm here with an absolutely empty nexus 7. i tried to use adb sideload to flash a new rom but my pc doesn't recognize the device and neither does fastboot. i tried reinstalling adb and fastboot drivers, i used universal drivers, i used drivers from toolkits, i did many many pc and tablet restarts, i reinstalled android sdk several times, i used different adb/fastboot locations, i even tried using a different pc trying the same steps. no change, only thing i get is that the tablet gets recognized by the device manager as an adb/fastboot device, nothing more.

Does anyone of you know a possible sollution for my issue?

Thanks in advance :)

P.S.: i've been researching the internet for this issue for the past hours and couldn't find any sollutions, so please don't say stuff like "use search function"

P.P.S.: My other devices get recognized without any issues with the same cable.
[Nexus 7 Q&A, Help & Troubleshooting] Masterloki666:
I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking :rolleyes: hope this helps let me know if ya need more
[Nexus 7 Q&A, Help & Troubleshooting] .TanTien:
Thanks for the reply.

The thing is that the device doesn't get recognized in fastboot mode by the fastboot interface. But I'll try anyways as soon as I'm at home again...
[Nexus 7 Q&A, Help & Troubleshooting] Masterloki666:
Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails