yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] JoNex:
ZIP File Does Not Work

Hey, I have a Nexus S i9020 soju and flashed a fresh stock 2.3.6 GRK39F image... I want to keep my device on 2.3.6 for reasons I don't want to get into, but I tried flashing the "Disable.OTA.Updates.zip" zip file from CWMOD and it didn't take...

What could I be doing wrong? Does the phone have to be rooted even to flash a zip from a custom recovery? I don't want to have the phone rooted in the end... I did try rooting and installing the FOTAKILL.APK in /system/apps and THAT worked successfully, but I tried installing the zip from SD in CWMOD multiple times (without errors) before rooting and it didn't take :(

I just need help with getting FOTAKILL to install properly as a ZIP file so I don't have to have the phone rooted in the end... Is this even possible?

Please help as I am a bit of a noob (but not THAT much) :P

Thanks guys!

Jon
[Samsung Epic 4G Touch] Sloth:
Could be that you are trying to use it on the wrong device?
[Samsung Epic 4G Touch] JoNex:
Root needed for ZIP method?

How could I be using it on the wrong device? I did try the APK method however and that worked, but my question is if I try the ZIP method mentioned in the first post of this thread, do I need to be rooted for the ZIP method to work as well? I think when I tried the ZIP method, I was not rooted at the time and it did not work even though is said it completed successfully. So, I rooted and tried the APK method and that worked fine, but I want to try flashing everything again starting from scratch and try the ZIP method instead... Would I need root for the ZIP method?
[Samsung Epic 4G Touch] tdunham:
I'm pretty sure you have to be rooted so you can use a custom recovery to flash that zip I posted. In other words, you cannot flash it with stock recovery no matter what and to get custom recovery on the phone I believe also requires root access.
[Samsung Epic 4G Touch] rocket321:
The flashable zip was written for the Epic Touch...I would recommend using the APK method, or you need to learn the recovery script language and update your own script to work for your device.
[Samsung Epic 4G Touch] Ci2e:
Is it not possible to update to the latest verison? Why kill OTA?
[Samsung Epic 4G Touch] tdunham:
You cannot update to OTA from a custom rom. So the nag gets very annoying.
[Samsung Epic 4G Touch] H4rryTipp3r:
damn you went thread digging.... a day what he^^ said

Sent from my SPH-D710
[Samsung Epic 4G Touch] tdunham:
The flashable zip on the OP is mine. So I've been here before. :)
[Samsung Epic 4G Touch] makelite:
I have a Rooted Sprint Galaxy Note 2 flashed for MetroPCS with SynergyROm. Started getting this Update notification a week back and found this thread. I installed the .zip via Clockwork mod but upon reboot the update message displays again. I found the update in the cache folder- deleted it. Also using ES Explorer I copied the FOTAKIll.apk. Upon reboot I still get the Update Notification! I also went into the System Update under App Manager where I could "force Stop" which I did. It will not allow me to uncheck "show notifications" which is strange. I was also able to clear data from this screen - but still- Update appears on reboot. Hmmmm- Must be missing something. THanks for any advice.

---------- Post added at 05:34 PM ---------- Previous post was at 05:10 PM ----------

Ok, after some inspection of some folders using ES Explorer i have found one that is titled wdh_update. Within it is a file called EAD-T10_lJ02.sbin. I think this must be where the issue lies. I can delete this file no problem using ES EXPLORER but upon reboot it appears again. I tried deleting it, then reinstalling the ZIP through clockwork mod in hopes that it would "clear it away" but to no avail- still there on bootup and still giving me the message to update. i attempted to delete the entire folder - and sure enough- upon reboot the WDH_Update folder is there again. Seems like I am getting closer- just dont know how to stop this Train!
[Samsung Epic 4G Touch] rocket321:
You could contact the synergyrom dev and ask him to disable updates. I see no reason why the fotakill app wouldn't disable it because it is known to be working on multiple devices, but maybe samsung is using a non standard update process.
[Samsung Epic 4G Touch] tdunham:
Also, this update was designed for Gingerbread but it also works with ICS.

Since you are probably on neither of those builds, it will probably not work.

Since we do not have any OTA in this forum beyond ICS (for the Sprint Epic 4G Touch), we do not have any point of reference for any newer builds and OTA issues.

Edit: Have your tried finding a solution through the Note 2 forums?
[Samsung Epic 4G Touch] makelite:
Good idea, I'll see what the Synergy Peepz have to say about this. As a semi-fix it seems that if I go in and manually remove the update folder than it at least doesnt keep attempting to update- or at least its been a few hours without one compared to receiving the request every 5 minutes. I'll keep the thread posted if I find out anything more.
[Samsung Epic 4G Touch] EVObastard:
Well I can't say this is not working for JB because after I flash it and reboot it goes to download page and no matter how I reboot it ends up on download page. I have a feeling it is because this does not work for JB I am currently running DaRKSTAULKER S3 vX, 4.1.1/MB1

Any thoughts?
[Samsung Epic 4G Touch] MoHoGalore:
My first thought is that this was made for the E4GT and you're running a S3..
[Samsung Epic 4G Touch] roscoeh:
nice Thanks!!!
[Samsung Epic 4G Touch] rocket321:
I have tested the FOTAKill app successfully on the Sprint S3. It disabled update prompts as expected on an older 4.1.1 JB build (lj7)
[Samsung Epic 4G Touch] mattchoo:
OH NO!!

OH NO!! I found this thread by clicking a link in another thread... I proceeded to flash the Disable OTA Updates zip file in TWRP thinking it would solve my problem... But now I'm stuck at the boot screen with the picture of the Android! All I can do is "Start, Restart Bootloader, Recovery Mode, Power Off". But when I try to start, it brings me back to the same screen.

I then realized that this flashable zip was for the Epic 4G... and I have a Galaxy Nexus.

On the screen, it says Fastboot Mode - No boot or recovery img.

HELP!!
[Samsung Epic 4G Touch] rocket321:
I assume you could download and flash a factory image to restore, but unfortunately I know nothing about gnex. You might want to ask for help in your device Q&A forum if you are stuck.
[Samsung Epic 4G Touch] Goflex:
I just did the same mistake.. lol (also had Gnex).

Did some reading, and found a very great info from this link:

everythingandroid.org/forum/threads/i-really-messed-up-no-boot-or-recovery-img.5631/

iP5's last post (thanks a lot):

So i tried to re-flash my kernel (luckily i had a backup of custom kernel on my SD), voila!! my Gnex booting normally again.

Here are the repair steps:

1. Boot into recovery

2. Flash any (custom) kernel in your SD [if you don't have any, i think you can push it from ADB]

3. Done

HTH
[Samsung Epic 4G Touch] mattchoo:
YOU SAVED ME!! Thanks!!!
[Samsung Epic 4G Touch] wklie:
This is exactly what I experienced too on my Galaxy Nexus, following a link from another thread. :silly: Luckily I had all the necessary files in flash to reinstall my phone from TWRP.

Thanks to the OP for this thread, but may I suggest adding a warning that the recovery zip is only for Epic 4G and do not try it on any other device.
[Samsung Epic 4G Touch] Stryke_the_Orc:
Considering the forum its in, I'd say it should be pretty self explanitory. Word to the wise, always look to see what device forum you're in before flashing anything.

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] Zeuszoos:
This method definitely works! :)

Note to Noobs: Do NOT run the Apk! Copy it as instructed!

http://reflectiveresonance.com/

Sent via TapaTalk Pro, on my cool

Samsung Sprint SPH-L900 Note II

Whompasaurus ROM, JB ver 4.1.2

Perseus Kernel v3.0.36 (Alpha 35)
[Samsung Epic 4G Touch] 0Gravity:
Hi All, I used this on my E4G touch, and it worked great.... Does anyone know if this would work on a Samsung Galaxy S4?
[Samsung Epic 4G Touch] aarongillion63:
I'm running stock Android. For me I noticed that when I long-pressed into App Info, it was hosted by Google Services Framework. Since my updates were not automatically downloading, I solved my problem by simply unticking Show Notifications. Duh!

Hope this helps some,

--

<<< Say thanks if I was of help! :good:
[Samsung Epic 4G Touch] hello_world.c:
Thanks! Just a couple of days ago, what had worked for many months on my Android 4.2 and 4.3 Nexus devices to prevent the OTA update notification, unticking the show notifications for the Gogle services framework, stopped working. Simultaneously for several devices, so Google must have changed something.

The FOTAKill.apk worked flawlessly to suppress the notification, glad I found this!
[Samsung Epic 4G Touch] rocket321:
I believe that it would work fine on the S4. This has been used on various different phones at this point. Just make sure you manually copy the apk (don't flash the ZIP on a different phone)

Cool, glad this is still helping folks out!
[Samsung Epic 4G Touch] GalaxySmokes:
Is There a FOTAKill.zip for TWRP?

This looks promising. Can I safely flash this file with TWRP or is there one made specifically for TWRP?

Thanks and Happy Holidays to all!
[Samsung Epic 4G Touch] rocket321:
I wouldn't suggest flashing the zip unless you are on an ET4G since that's what it was scripted for. You can try manually copying the FOTAKill file instead on any phone. However I don't think it works for kitkat+, newer versions you might search for other methods.
[Samsung Epic 4G Touch] denshigomi:
After upgrading my Nexus 7 2012 WiFi from Lollipop 5.1.1 to KitKat 4.4.4, I tried several methods to disable the OTA nag. FOTAKill proved to be the most effective solution. The only caveat was that after installing FOTAKill, deleting the update from my cache, and rebooting, I could not swipe the notification away. I had to choose to install it (which failed because I deleted the update from my cache). Then the notification left for good. Thank you.
[Samsung Epic 4G Touch] rocket321:
I love that 3 years later this thread is still kicking...makes me want to check in on the Epic 4G forum! :)
[Samsung Epic 4G Touch] tdunham:
Yes, amazing that it still is working too. :D
[Dell Streak 7] jpmi23:
Ok, this is probably a stupid question but does a wifi only S7 have the appropriate components to run a 3G SIM card? I ask because I can get a SIM from T-Mobile (pre-paid with 10 minutes) for $0.99. I don't want to waste my dollar though. Any ideas?
[Dell Streak 7] TheManii:
no, it is physically missing the antenna/modem/modem slot/sim card tray and assembly
[Dell Streak 7] jpmi23:
That's what I figured. Thanks.
[Samsung Galaxy Nexus] arrish4:
Without rooting gnex. how can I get officially update from google android 4.1.1 jellybean.
[Samsung Galaxy Nexus] munchy_cool:
Ota
[Samsung Galaxy Nexus] arrish4:
What do u mean ota?
[Samsung Galaxy Nexus] Zehlek:
Over

The

Air
[Samsung Galaxy Nexus] patruns:
There is nothing to update to from 4.1.1 at this time. That is the latest release.
[Samsung Galaxy Nexus] kyokeun1234:
Mind if I ask you if you're running takju or yakju version, of you have bootloader unlocked and if you have gsm or cdma?
[Samsung Galaxy Nexus] arrish4:
Bootloader locked and gsm. How can I update from android 4.0.4 to 4.1.1
[NFC Hacking] NFC Guy:
I've found some talk on the internet which suggests that builds of Cyanogen mod from earlier this year enabled some sort of card emulation. The builds in question were CM9 builds from between January 20th to March 22nd 2012. This website claims that a commit was made to enable (again, some sort) of card emulation, but it was removed from future builds due to issues with Google Wallet compatibility.

Can anyone confirm this? I would try myself, but I'm currently not in posession of any of the supported devices. What I'm most interested in is if the emulated card has a static UID. This could be huge news if that's the case. Either way, the video demonstration suggests that they're able to dynamically change the data that is emulated by the phone

I searched through Google and found this page, which holds torrents of CM9 builds from within the above stated time range for the Nexus S, Nexus S 4G, GSM Galaxy Nexus, and the Verizon Galaxy Nexus. For those of you who don't know, the build date is the number before 'NIGHTLY'. By the way, this page has torrents for small update zips. You'll be wanting the larger, full OS zips (over 100mb files).

If you want to compile your own build with card emulation, you'll have to revert these changes.

I've not tested this myself, and I will not be responsible for any issues you might have. Good luck!
[NFC Hacking] NFC Guy:
If anyone is interested, I've downloaded and I'm seeding the update-cm-9-20120319-NIGHTLY-maguro-signed.zip for the GSM Galaxy Nexus. You can find the torrent here.
[NFC Hacking] Entropy512:
This might be interesting to conditionally enable this on devices that will never support GW (no SE). I'll look into doing this later this week.
[NFC Hacking] doug@simplytapp.com:
card emulation

it is actually currently active in CM9 and above the changes you see have to do with how it is activated. now, unless the app the requires emulation is in the foreground, emulation default is the SE (Gwallet). otherwise, when the app is up, the app emulates. like it should be. anyway, enjoy the patch, i worked hard at it.

-doug
[NFC Hacking] Entropy512:
Ah. Thanks for the info... I'm going to look into making it default to emulation on devices with no SE (such as I777)... But first I've gotta forward-port the patches to CM10!

so much to do, so little time. :(
[NFC Hacking] andre.brito:
I'm very interested in testing this. I have a Galaxy Nexus, but I'm unable to download any of the nightly builds, because there are no seeds. Tried the torrents from 18th, 19th and 20th March and 0 seeds. Also tried the torrent from the OP, but no joy. If anyone still has one of these builds laying around, please let me know.
[NFC Hacking] NFC Guy:
Here's a direct download link for the build that I have.
[NFC Hacking] jarnow94:
If you could do this I would be SO happy :D!

Keep us updated please!
[NFC Hacking] TheRealEdwin:
Any chance of getting something like this for the Nexus 7? I'd love to just use my N7 as my ORCA card instead of the card itself.
[NFC Hacking] LoveNFC:
Doug has yesterday ported the card emulation patches to Jelly Bean, as can be seen here. Could anyone do us a massive favour and compile a stock AOSP build for the GSM Galaxy Nexus with the patches in place?

Is compiling Android from source (with mods) difficult? I'd love to be able to do this kind of stuff on my own without relying on others for help.
[NFC Hacking] jarnow94:
If someone could compile it for the GS3 that would be awesome too, please!

Thank you for keeping us updated!
[NFC Hacking] andre.brito:
So, I managed to download the nightly build for 19th March and installed it successfully. After booting, I accessed the settings menu and noticed that the NFC option was grayed out. I tried CM9.0.2 and CM9.1.0 and the result was the same, which leads me to believe there is some sort of driver incompatibility, but I can't be sure.

Then I tried the latest CM10 nightly build and now I the NFC option is enabled and working correctly, but no card emulation. I'm currently trying to create a CM build with the card emulation port made by Doug Yeager. I'll let you know how it goes.
[NFC Hacking] jarnow94:
I can confirm SimplyTapp runs using CM10 with the latest NFC patch by Doug, but I have no idea if it works. It says "Invalid Card" with my FeliCa-based college ID card, is there another way to maybe get it to work without SimplyTapp?
[NFC Hacking] NFC Guy:
Did you compile the CM10 ROM yourself?

When you say SimplyTapp, do you in fact mean NFC Relay? Either way, there's still no current way to actually copy and use your ID card in Android. The only thing we can copy and emulate (as far as I'm aware) are certain NFC-enabled credit and debit cards.
[NFC Hacking] jarnow94:
I used this CM10 ROM, and I meant SimplyTapp.

The ID card was successfully read by other apps, but couldn't be emulated because of card emulation wasn't enabled. As far as I can tell full card emulation still isn't enabled because the ROM changelog specifically lists emulation as "Tapp Support" and nothing else.

I know ID emulation support exists, as shown by a reviewer here
[NFC Hacking] Mach3.2:
Any apps that allow the gnex to emulate the same Id or copy the Id of another card and emulate the id?

Beamed from my Maguro.
[NFC Hacking] jarnow94:
The NFC changes have been merged into CM10; if your phone has nightlies, you should see this tomorrow.

I would appreciate it if other people could check it out and let me know if they can emulate a FeliCa ID, please!
[NFC Hacking] Mach3.2:
I flashed it already, but no option to emulate a card or anything.

Beamed from my Maguro.
[NFC Hacking] LoveNFC:
I never had any luck with NFC classic, and I find it a bit odd that that's the only application where people have made claims that they're able to read and then emulate a card.

Even if it does genuinely work, does your FeliCa card use default keys? If not, surely you wouldn't be able to emulate it without cracking your card's keys in the first place.

You can test for card emulation by seeing if the Tapp app runs or force closes.

I'm trying to wait for someone to compile a stock 4.1.1 ROM with the NFC patches, but CM10 is starting to tempt me. Could someone here answer a few questions about ROMs, though?

1) How would I preserve all of my current apps and settings in my stock 4.1.1 and then restore them in CM10? Titanium backup?

2) If I want to go back to stock directly from CM10, can I just go straight into CWM and restore my Nandroid backup and everything will be just as I left it before installing CM10? Could this cause any issues?
[NFC Hacking] jarnow94:
I'm pretty sure it does.

To the second part of the statement, yes everything will be the same but you have to remember to wipe data, etc. before restoring the backup.
[NFC Hacking] Mach3.2:
Where to get the Tapp app? The market link is not accessible for me.

Could you upload the apk?

Beamed from my Maguro.
[NFC Hacking] jarnow94:
Here it is.

This is a free app, if I'm breaking the rules by uploading this I'm sorry, please remove it.
[NFC Hacking] andre.brito:
I've tried a series of CM10 builds on a Galaxy Nexus, but I'm having a weird problem. With the nightly builds from 28th and 29th August, the NFC reader works fine, i.e., I can read NFC tags successfully and the NFC option in the settings panel is enabled and active.

However, with all the builds after 29th (specifically the ones from 31st August and 2nd and 3rd September) the NFC option is disabled and, therefore, the NFC is not working (see image in attachment).

Any ideas on what might be going on?
[NFC Hacking] JulienDev:
I have posted a new conversation on Cyanogen board in order to have more informations about the new feature. You can follow it here : http://forum.cyanogenmod.com/topic/58532-nfc-card-emulation-patch-now-what/
[NFC Hacking] zwox:
hi there,

I would like to know if there is any project going on with tag emulation. Since a lot of apps on google play (almost all) have something related to emulation, but none have it implemented yet so far. I just would like to know if some of those apps are going to be rewrited with CM api, but not likely. So here's the big deal : is there a chance of getting the source of such an app, and try to do it myself ? Help would be appreciated.

It frustrate me so much to have a nfc enable device and not being able to enter my work with it :(, would be useless but sooooooo cooooool
[NFC Hacking] Damastus:
You could look at NFC Proxy for example. Basicly what was done in CM is that you can actually detect an NFC reader and get an event inside the android system to react to. But I'd like to know which apps you are talking about? Only other app that is using card emulation that I know of right now is simply tapp.
[NFC Hacking] zwox:
I can almost confirm that tapp app works. I installed it on a stock rom and obviously it didn't worked at all. Then i flashed a CM10 nightly and the app started just fine. Here's the thing : to actually verify if card emulation works, i'll have to buy some card on the app website, and i don't want to since i won't be able to use those. I'd just like to know if one already wrote an app to scan/copy/emulate a tag, just as a proff of concept. I working on such a thing right now. I'm planing to scan a tag in which i have already written some datas, scan it with the app, and emulate it and try to read the datas with a usb reader/w. But since i'm new to android developpement, and given the fact that we didn't created 48h-days. So much thing to do. That explain why i never finish anyth...
[NFC Hacking] Damastus:
Well, thats the point, tapp app is simplytapp (as I stated in my post). Don't get me wrong, but saying you can almost confirm it works is kinda useless, given that you actually can not verify if it works as you said :). I'm doing something quite similar to that what you want to do, and I can tell you already that this topic is kind of a pain in the a**. What you could do is look at the project NFC Proxy (as I also mentioned before). Might give you some insight into the matter.
[NFC Hacking] zwox:
yes, this post was pointless, but i'm trying to understand how things work, that's why i wanted to give a try to simplytapp. I wanted to know in the first place if trying to implement card emu was possible or if i was going to be a total waste of time.
[NFC Hacking] Entropy512:
Unfortunately, it seems like the easiest no-committment ways to verify that it works are US/Canada-only... Unless McDonald's Arch cards are international...
[NFC Hacking] :
Does simplytapp work in Australia
[NFC Hacking] Damastus:
Another interesting aspect of that update is, if it works with every phone, or only with phones that use NXP's PN544 chip. After inspecting the code it seems that the later is the case. At least that is what I can get out of it. If somebody could confirm or deny this I would really appreciate it.

I've been trying to contact the guys of simplytapp over at their website via this e-mail thingy. But, as expected, no one answered until now. May I add, that this "Give us your e-mail and we contact you." has this scam-ish feel to it... I even created a new e-mail just for that purpose...
[NFC Hacking] Mach3.2:
Actually I'm only interested in emulating a card for door access etc, not payment cards.

Beamed from my Maguro
[NFC Hacking] Damastus:
Same goes for me, but in the end, using knowledge gained from this here can be handy. Because without working on the os itself, we cannot get it to work. Question is, can it actually be done or are we limited to some extend. I'd like to find that out before going in on this and later realize that its simply a waste of time...

Edit:

Found the answer to the phone question by myself. Totaly did not see that blue bar on their page (duh)... Devices are here. At least now I know that my observation was correct. Wouldve been easier to see it on the page in the first place instead of reading code :)
[NFC Hacking] Damastus:
So, alright, after reading through documentations and the code etc I guess it's kinda time to give up on that route, at least for me.

As far as I understand their code and the documentations I read, it basicly still comes down to the capability of the hardware we are equiped with. Every device that can use smiplytapp uses the PN544 Chip. We can only emulate cards via it's build in capabilities. The difference is, that the standard android os does not support this, and that is what the team of simply tapp implemented. The PN544 for example can not emulate Felicia cards, which means we won't be able to do this either. At least not the way the CM Team did this.
[NFC Hacking] Mach3.2:
Damn..:(

Beamed from my Maguro
[NFC Hacking] :
so you can use it just like google wallet at any paypass/paywave place