yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkong:
I thought being rooted did not affect OTA updates, you just lose root after. I know in an S4 active kitkat update thread someone somehow extracted the updater-script from their ota update that listed the apps/files that are needed for the OTA to pass. I already have stock recovery, defrosted all my apps, unchecked all xposed modules and I replaced the missing system apps like knox with the stock /system/apps folder. The OTA is redownloading now, I guess I can unroot and resume the update and hopefully it works. The only other option is to either use stock recovery to flash the ota from external (which wipes data) or flash enewman's 4.3 stock which also does a factory reset, so I'm guessing there's no way to update without a reset.

I think sideloading doesn't work because adb sideload is only available as an option on TWRP not stock recovery, and the OTA always fails if you have a custom recovery..

On a side note, is there anyway to backup and restore the touchwiz launcher, like preserving your folders, apps, and widgets on your homescreen and appdrawer? I know you can use TiBu to backup all user apps and data but I don't think it preservers folders and the layout.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
That means you are still on 4.1 firmware. It may not flash the ota unless you fully update to 4.3 via odin.

you can try your way of course. Looking at the script it appears to only check the kernel and modem so it might just work that way.

You are right about root. Sorry for the misinformation. Been a while since ive dealt with OTA's. Im uploading a modded version now. It SHOULD allow flashing from cwm and twrp while also preserving root. (I hope!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ok, here is the modded OTA!

It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!

You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.

THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.

Please post back ASAP after trying this out so we know if it is working or not.

Modded_OTA_UCUEMJB-UCUFNE4.zip

Hope this proves helpful for some of you!

Doc :cowboy:

---------- Post added at 02:56 AM ---------- Previous post was at 02:54 AM ----------

Me too! Though since youve already updated your firmware, im not sure if the ota will work or not. It probably will, but cant guarantee it of course!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkong:
I'm getting an error, "Error executing updater binary in zip '/sdcard/Modded_OTa_UCUEMJB-UCUFNE$.zip" when using twrp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] makona:
Hi is there an OTA file like this one it would help a lot since i am not in AT&T network? http://xdaforums.com/showthread.php?t=2387423
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ok thanks! I will try a different binary and reupload soon.

What version of TWRP are you using?

Umm, do you mean like the one in the OP of this thread? Just flash stock 4.3 via Odin, then flash the posted ota from recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkong:
I'm using 2.7.1.0, I tried using twrp to install both the modded and unmodded zips and they end up with the same error. I think its worth mentioning that I tried it using this rom [http://xdaforums.com/showthread.php?t=2498233] nonrooted, and it said something like "package expected 4.3 or 4.4.2 but found 4.1.2," which is strange because it is a 4.3 rom. I am again twrp-ing back to my rooted/modified 4.3 original rom and try that but it will probably fail since I'm missing some system apps.

I think I will wait for a flashable tar of the entire kitkat rom instead of trying to mess with the OTA because I either have to delete all my data for it to work. Hopefully somone can hack something like that together like they did with the 4.3 update; its not like I'm expecting samsung to release anymore updates after this one anyway.

edit: tried it on my original rooted restore, "/system/app/containerAgent.apk" has unexpected contents" and also "Error executing updater binary in zip" again. I am going to try to replace my entire /system/app/ folder and try the modded zip again using twrp. I might not get the unexpected contents error but I think the binary still won't work so I''ll wait for an update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] makona:
Yes, im on stock 4.3 so i will try that. its asking for a decryption key can anyone provide?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkong:
Are you sure? The link the op is working for me, but can someone make a mirror?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] makona:
weird i tried it again and link now working. thanks bro! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xCAVEMANx:
OTA

I couldn't get mine to side load...Odin back to stock, grabbed OTA over WiFi (with Knox Tripped at Warranty bit 1)...waited, went and got a margarita, came back installed OTA, TowelRoot, Installed SU from Play Store, TiBu apps...debloat, Xposed...running like a champ. Seems rock solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoobie-doo:
Being on 4.1 is a surprise to me.. My baseband is MJB, and about devices shows me with Android 4.3 and the kernel fromOct 31. Hmmm... Would your recommend flashing the 4.3 package posted by ashamsu at http://xdaforums.com/showthread.php?t=2722660 or a different package?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lifetimes:
Unzipping the file and then converting the cfg file to zip and installing through stock recovery updates the phone to 4.4.2 but remember, it wipes the devices clean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tailgunner9:
4.4.2

I have 4.3 rooted but the Update to 4.4 will download but not install. Is it that I have CWM or that it is rooted? Do I have to install pure stock 4.3 then Update to 4.4????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
which odin file you used for the stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoobie-doo:
I am interested in knowing as well; there are at least two out there - the one from ashamsu and the one enewman17, both in http://xdaforums.com/showthread.php?t=2722660. Did you use one of them or a different one?

As far as I am concerned; the fewer flashes, the less chances of bricking, so would rather follow in someone else's path, especially since I am interested in staying as close to stock as possible and then rooting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xCAVEMANx:
I used the one from ashamu http://xdaforums.com/showthread.php?t=2722660

---------- Post added at 10:11 AM ---------- Previous post was at 10:08 AM ----------

Have to use Odin 3.09 and put all the separate file in each slot. Follow the instructions from ashamu...I haven't used enewman17's version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Unless you updated via

Odin or OTA, the base firmware would not have been updated. Mobile Odin, while a fantastic app, cannot flash the full firmware. (This is by design). It can only flash system, kernel, modem, recovery and cache.

If you want to know for sure, enter this in terminal emulator:

getprop ro.bootloader

It will tell you your base fw build

Going to now. Sorry bout the wait. Was exhausted and couldn't concentrate any more and fell asleep!

Until I get the modded ota working, yes you have to be full stock to use the ota.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoobie-doo:
I didn't know that about Mobile Odin. But interestingly enough - bootloader is I747UCUEMJB

Thanks for the info. Despite being stock everything except for root, the OTA isn't working for me either from the phone's interface or as a push from ABD or from the SD. Looks like I'll need to Odin to stock and then apply the OTA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrPandroid:
yeah, you can't even be rooted to flash the OTA with stock recovery. I used the odin file from enewman and sideloaded the update. Then wiped all data anyway, just to be safe.

i guess its just personal preference to wipe data when I take an update, better safe than sorry. Not like I have too many apps installed anyway xD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoobie-doo:
Hmm..if I am going to have to ODIN it; I wonder if I should just try to unroot first with SuperSU before going through all of the flashing. Would save time and mean one less flash, if it works

Curious, any reason you chose enewman's tar vs ashamsu's individual files?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I am uploading two new versions of the modded OTA now. Will post links as soon as they are ready. Both have replaced the upater-binary. One has nearly all checks removed, so it should flash even if you have removed or changed anything. I will post more when it is ready, but needless to say, be careful with this one!

Didn't realize someone already did this.....do I need to continue working on it? Provided mine works btw, it should preserve root as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrPandroid:
Im a fan of everything being all in one if possible. One download, one flash, clean slate. Just personal preference I suppose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
So we'll still need to be on stock (everything) to flash them??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes, please that will be awesome

---------- Post added at 07:59 PM ---------- Previous post was at 07:42 PM ----------

Did these steps updated your S3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
READ THIS WHOLE POST BEFORE FLASHING!!!!!!!!!!!!!

READ THIS WHOLE POST BEFORE FLASHING!!!!!!!!!!!!!

READ THIS WHOLE POST BEFORE FLASHING!!!!!!!!!!!!!

READ THIS WHOLE POST BEFORE FLASHING!!!!!!!!!!!!!

Ok, here they are. Please try the OTA2 first! It still performs all of the original file checks before flashing. The OTA3 version has most of the checks removed. (It will still check your kernel and modem, as well as free space to ensure there is enough room for the process to work.) Make sure you have a backup and a known good rom handy, just in case.

Modded_OTA2_UCUEMJB-UCUFNE4.zip

Modded_OTA3_UCUEMJB-UCUFNE4.zip

Both now use an update-binary I know to work for flashing KK in TWRP. Hopefully they will be able to handle the OTA's updater-scripts syntax. (If it fails, please Copy Log to SD and post it here so I can determine if I can make changes to the scripts, or if I need to try yet another binary.)

For OTA2 to flash, just like the original one, you must be full stock 4.3. Any debloating, or modded files may cause the flash to immediately fail. This is the preferred method because it is safer!

For OTA2 to flash, you must have the 4.3 stock kernel and modem. I believe it will update the rest of the firmware regardless of its build, but I cannot say for certain. This one has all other file checks removed, so if a file is missing or changed, it should still flash. BE CAREFUL!!!!!!!! I make no guarantee of this method working! MAKE A BACKUP FIRST!!!! If this does cause problems I do believe you will still be able to restore a backup and/or reflash another rom. I do believe the worst that may happen would be a soft-brick, but understand I cannot guarantee this! I have never tried this method myself, but theoretically it should work. When it flashes, it will patch many of the files you currently have on your device, and will replace some others completely. This is why it is best to be completely stock. If you have any mods applied, the patches may or may not work as expected. DO NOT ATTEMPT TO USE EITHER OF THESE IF YOU ARE USING A CUSTOM ROM OR ANYTHING OTHER THAN OFFICIAL 4.3!!!!! Custom roms are most likely going to be too heavily modified and will probably cause problems! If you try, it will probably soft brick.

I think I have covered everything I can think of. If you have any questions, please ask! I do want to avoid any problems if possible! I do not believe these will hard brick the device as it does not patch the underlying firmware partitions, it replaces them with 4.4.2 versions. So any issues should (in theory) be centered in the system, kernel and/or modem. But again, I am not guaranteeing ANYTHING. As with everything else on XDA, you use this at your own risk! But also understand that I would not even release these if I felt there was a good chance of hard bricking!

:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
Won't be able to try this until I get home from work in a couple of hours. If there's anyone else willing to try please post here your results. Happy flashing guys ???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Hopefully I didnt scare everyone from trying it! Lol!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoobie-doo:
A big public thanks to DocHolliday77, MrPandroid for the direct help in getting me to 4.4.2. I've thanked your posts, but do appreciate the responses to my questions.

Flashing stock and then sideloading worked for me. Now I need to see if I can encrypt my device again, and then finally perform towelroot to get TiBu up again.

Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
Lol I'm not. Just waiting until I get home. Downloading both packages now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lifetimes:
yeah. It's on 4.4.2 now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bronsonelliott:
I want to try but I'm still gunshy and waiting for more reports before I proceed.

I have 4.3 but installed twrp and then rooted. I'm just still trying to figure out the right process for unrooting and going back to stock since that seems to be a requirement. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lifetimes:
yes, pure stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If my modded ota works, you can be rooted and won't lose root either. You will also be able to flash from TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
Flashing now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jammn:
Hey Doc... After returning to stock do you flash from stock recovery?

Thanks and great work!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
I tried to flash both files on stock recovery and got multiple errors..didn't get a chance to record any of em either
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
so any of the doc ota file worked for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
switch to google emoji

anyone who has root can get back to stock google emoji with emoji switcher https://play.google.com/store/apps/details?id=com.stevenschoen.emojiswitcher , I just learnt about this and posting it here; the system wide samsung emoji are awful
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jammn:
I'm on stock 4.3 rooted with twrp recovery. I tried option 2 but got "Error executing updater binary"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
The included binary is for custom recoveries, so I don't know if it'd work with stock recovery. Probably not. Can you try using twrp? If it fails don't reboot, go to the advanced menu and copy log to sd. Then post here so I can see what went wrong. Hopefully it'll just work with twrp though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
can I get back to 4.3 without bricking the device? via odin flashable file or some other method?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Only if using the ota in the OP. If using mine try from cwm or twrp.

---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------

Or if you want to try with stock recovery, try using the first one I posted last night. It still has the binary intended for the stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
There you go Doc..failed again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Thanks! Hopefully this will show me where im going wrong! Sorry this is taking so long to hammer out!

---------- Post added at 01:08 AM ---------- Previous post was at 12:55 AM ----------

Lol! Looks like I was too slow again!

Don't know if it preserves root or not, but here you go!

http://xdaforums.com/showthread.php?t=2789917

I did note that he is using TWRP 2.6.1.0 I think it was. If someone wants to still try it, try flashing my modded ota using that version. Try the first one I posted first if you do want to test this. Its in post #47.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crazymonkey05:
OK guys let me get this straight, which .zip do I use with stock recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
If you want to try mine, try the first one I posted in post 47. Otherwise use the one in the OP, or the one posted by enewman17 at the link I posted just above your post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
how to fix the external sd card issue on the kit Kat issue. I never faced this issue with nd8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ill post the fix in a few min. Its a simple edit in the platform.xml, but want to make sure I tell you exactly right.

---------- Post added at 12:40 PM ---------- Previous post was at 12:00 PM ----------

To fix writing to the External sdcard, you need to open /system/etc/permissions/platform.xml and look for this:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_r" />

<group gid="sdcard_rw" />

</permission>

add another group gid, so it should now look like this:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_r" />

<group gid="sdcard_rw" />

<group gid="media_rw" />

</permission>

Reboot, and Done! :victory:

---------- Post added at 12:43 PM ---------- Previous post was at 12:40 PM ----------

If you are running stock, rooted, and are not planning to flash a custom rom, you may also have problems with writing to Internal SdCard. To get around this, you need to be using an insecure kernel with selinux disabled. You can use this one if you so choose:

ATT_NE4_Insecure_Kernel.zip

If you flash this and wifi stops working, you can use the KT747 kernel from ktoonsez instead.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
I used the post by enewman to flash the ROM in his post following his instructions and using TWRP. I have no problem with copying files back and forth between a 64gb SD card and the internal SD. No wifi problems either. This phone has basically just been setting around the house connected to wifi and doing nothing for like 26 hours and the battery is at 66%. This is a 3300 mAh battery. This is my backup phone. I just added my work email to it. Going to recharge it and see how it does with email and weather alerts running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harishbabu77:
Can you please let me know which file you downloaded for 4.4.2 update and what steps you followed to do the same

I am on stock 4.3 firmware and do not what to root my phone. Thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harishbabu77:
Hi, I am in stock 4.3 and used OTA provided by OP to update to 4.4.2 using stock recovery from External SD

I am getting the error message E: Signature Verification Failed

Cache got cleared and phone got reset back to factory and I am still in 4.3

Please help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Try this one.

http://xdaforums.com/showthread.php?t=2808654
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harishbabu77:
I tried this update with stock recovery - update from SD card, but still I get E: signature verification failed message and phone is getting factory reset.

Do I need to install using TWRP only and is this going to root my phone as I do not want to root my phone

please help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
No it wont root the device. Your current rom and kernel will remain as they are and it will update only the base firmware/bootloaders to 4.3. And yes, it must be flashed from custom recovery, TWRP recommended. If you don't want root or custom recovery, this or using the Software Update option are your only choices.

I've tried making an Odin flashable package, but it hasn't worked. If I have time I might try again this weekend. Can't promise it though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harishbabu77:
I successfully updated to 4.4.2 using the OTA file by OP

Note: this will wipe the phone so take backup

here are the steps I followed

* I had a stock 4.3

* took back up of existing data

* Download the OTA file and unzip it

* find a file 2400258.cfg - rename this file to 2400258.zip

* copied the zip file to SD card

* used stock recovery - update from SD card option

got updated to 4.4.2 and restored the data from the backup
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] donuthole:
Anyone have a mirror of the OP's fota.zip? Mega has just been showing "Temporary error" trying to download it for the last 2 days now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
have you tried a different browser?
[Android Q&A, Help & Troubleshooting] :
:cowboy:

HELP !​

Im using GT S5302 a.k.a Galaxy Y Duos Lite OR Galaxy Pocket [ DARK JB ROM ]

I face this problem frequently...

Im Flashoholic and interstingly this problem occures after frequent flashes...

And dissapears automatically after 1/2 weeks !!

Now, Finally The Problem is ... ​

Whenever I turn on / toggle WiFi on my phone , Phone Activity (i.e radio part not dialertabactivity) FCs and I have no network connection for about 5 min. Same occures when I turn off WiFi.

Whats causing this FCs ?

Has Xposed Framework ( ported ) caused this ? Coz I had installed it last weak and its really buggy ...

Or any else ??

Has anyone among you faced this problem earlier ?

Any solution ??

Feel Free to post whatever you think...!

:cool:
[One (M7) Q&A, Help & Troubleshooting] narmerpolo:
good day everyone, i'm facing a problem in my HTC one on the phase of verifying the whatsapp on it.

i had Iphone 5s and my whatsapp was installed on it, i was using it without any problem. then i bought the HTC one and i factory reset the Iphone 5s.

after installing the whatsapp on the HTC one and inserting my phone number i waited for the verification sms which in a minute gives me a message stating " SMS verification failed please try voice verification", and then when i press on call me it gives me a message stating " we couldn`t call your number, please check your number and try again in 1 hour" and i did many times, and it did not work.

i have Google and searched the web for solution even XDA and i did not find any. i followed the troubleshooting step by step with no success. i even sent an e-mail to whatsapp support and they replied with the troubleshooting steps which i did again with no success; then i sent them that it did not work but no reply.

so far for my conclusion i think that the iphone whatsapp is blocking my phone number from being installed on another phone even after uninstalling it.

can anyone help or support in solving this issue?

thx in advance.
[One (M7) Q&A, Help & Troubleshooting] narmerpolo:
any support will be appreciated, this problem is driving me to the wall
[One (M7) Q&A, Help & Troubleshooting] akshayy29:
Does your network has range!? Check date and time setting on phone! Change it to automatic !
[One (M7) Q&A, Help & Troubleshooting] narmerpolo:
thx akshayy for the reply, the date and time setting is set to automatic and same problem.