yashsingh1/xdaforums huggingface dataset:
[NFC Hacking] pealiksuurmuna:
I am having a problems with emulating FeliCa tag with ACS122U in combination with S3.

I am emulating a Type-3 NDEF tag, phone NFC service successfully reads the NDEF Message from the emulated card,

starts my own application, and finally, when inside of "onNewIntent" handling for the ACTION_NDEF_DISCOVERED intent,

I see that the tag has following tech listed:

android.nfc.tech.NfcF,

android.nfc.tech.Ndef,

I get the NfcF tech, check if tag is still connected, and call transcieve() to invoke a POLLING command on the tag,

what happens is, I get DeadObjectException, and transcieve call fails.

Here is the stack trace

What can I try to make the transceiver work?

06-13 21:00:47.558: I/System.out(16727): NDEF discovered in onNewIntent, enabling foreground dispatch

06-13 21:00:47.563: I/System.out(16727): android.nfc.tech.NfcF

06-13 21:00:47.568: I/System.out(16727): android.nfc.tech.Ndef

06-13 21:00:48.128: E/NFC(16727): NFC service dead

06-13 21:00:48.128: E/NFC(16727): android.os.DeadObjectException

06-13 21:00:48.128: E/NFC(16727):	at android.os.BinderProxy.transact(Native Method)

06-13 21:00:48.128: E/NFC(16727):	at android.nfc.INfcTag$Stub$Proxy.transceive(INfcTag.java:405)

06-13 21:00:48.128: E/NFC(16727):	at android.nfc.tech.BasicTagTechnology.transceive(BasicTagTechnology.java:146)

06-13 21:00:48.128: E/NFC(16727):	at android.nfc.tech.NfcF.transceive(NfcF.java:119)

06-13 21:00:48.128: E/NFC(16727):	at com.MyApp.MainActivity.onNewIntent(MainActivity.java:244)

06-13 21:00:48.128: E/NFC(16727):	at android.app.Instrumentation.callActivityOnNewIntent(Instrumentation.java:1157)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.deliverNewIntents(ActivityThread.java:2193)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.performNewIntents(ActivityThread.java:2206)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.handleNewIntent(ActivityThread.java:2215)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.access$1400(ActivityThread.java:140)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1298)

06-13 21:00:48.128: E/NFC(16727):	at android.os.Handler.dispatchMessage(Handler.java:99)

06-13 21:00:48.128: E/NFC(16727):	at android.os.Looper.loop(Looper.java:137)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.main(ActivityThread.java:4898)

06-13 21:00:48.128: E/NFC(16727):	at java.lang.reflect.Method.invokeNative(Native Method)

06-13 21:00:48.128: E/NFC(16727):	at java.lang.reflect.Method.invoke(Method.java:511)

06-13 21:00:48.128: E/NFC(16727):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1006)

06-13 21:00:48.128: E/NFC(16727):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)

06-13 21:00:48.128: E/NFC(16727):	at dalvik.system.NativeStart.main(Native Method)
[JAM, MDA Compact, S100 General] johannesl:
can somebody tell what these files are ? there are 7 of this file and it's 2784K big each. Also there are 7 MsgQueueMapFileMicrosoft that are 262K big each.

thks,

johannes
[JAM, MDA Compact, S100 General] jacoch:
http://xdaforums.com/viewtopic.php?t=16081
[Sony Xperia P, U, Sola, Go] GEKTHEBOSS:
GMaps 6.14.4 MOD - No Extra Shortcuts !

All works fine!!!

http://www.file-upload.net/download-7720549/Maps_GEKTHEBOSS_CryllezZ-signed.apk.html

Byeee!
[Sony Xperia P, U, Sola, Go] Pandemic:
Wow, any screenshot or explanations what it do?

instead open a new thread with an App and thats it.
[Sony Xperia P, U, Sola, Go] GEKTHEBOSS:
Its just gmaps without shortcut of navigation,local,etc.:)

---Signature---

I'M Busy With Exams Till First Of July, So Don'T Ask Me Any Update Or Support, Byee!

---End---
[Sony Xperia P, U, Sola, Go] Pandemic:
Ooh ok is cool, nice :)

:::[ Pandemic ..:: JB MoonBreakers 4 Ever :.

Press Thanks If You Like My Work/Advice !!
[LG Nitro HD] SeungJuny:
I ported SU640 CM10.1 Nightly to LU6200. I Change etc/init_qcom_post_boot.sh , etc/apns-conf.xml , boot.img, and fixed update-script.

But I Install CM10.1 And reboot, It shows like blue screen(?)

Why is it?:crying:
[LG Nitro HD] catlike32:
check your kernel, the kernel is already update
[LG Nitro HD] SeungJuny:
Hum,. OK. Thanks
[One (M7) Q&A, Help & Troubleshooting] sorcerer1:
Anyone else got this serial number prefix? If you have please let me know the quality of finish.

Thanks!
[One (M7) Q&A, Help & Troubleshooting] phylosoph:
I've got FA35MW, is has almost no problems, screen is properly seated. Not much gap issues. Power button seams good as well.
[One (M7) Q&A, Help & Troubleshooting] LenAsh:
Same as mine. Black One built 27th May in Taiwan. Not good.
[One (M7) Q&A, Help & Troubleshooting] sorcerer1:
Where did you buy yours? Got mine from amazon UK. What's wrong with yours?
[One (M7) Q&A, Help & Troubleshooting] LenAsh:
From similar place... screen and speaker grilles misalign - definite step between the lower grille and display, grille is slightly bowed and a gap exists which fills with dust. Large gap between top left speaker grille corner and plastic. Going back.
[One (M7) Q&A, Help & Troubleshooting] sorcerer1:
When did these problems come to light.... You mentioned on a previous thread that overall the phone was ok apart from one slight gap!
[One (M7) Q&A, Help & Troubleshooting] sorcerer1:
FWIW mine is fine
[Galaxy S III Q&A, Help & Troubleshooting] sebbe312:
Hi everyone!

I've just been thinking of what would happen if someone stole my S3.

By just using a password on my lockscreen doesn't make me feel safe, since they can always reset the phone via download mode, or factory reset the phone in recovery mode.

Even if I used a third party app that can lock the phone, I can always get into recovery- and download mode to reset the phone, and all its settings.

I mean, how secure is that?

What would've been making me feel safer would've been to set a password on Download mode and Recovery mode.

Like this; you press all the required buttons to get into download mode and before getting in to download mode you'll have to type in a password, which I can set to whatever I want.

TL;DR Is there a way to set a password on download mode and recovery mode? Any app, or recovery that supports what I just mentioned?

Cheers,

Sebastian
[Galaxy S III Q&A, Help & Troubleshooting] GuruThor:
Re:

I don't think what you're asking is possible... You can use avg to block your phone from its website which is more secure...

HIT THANKS IF I HELPED
[Galaxy S III Q&A, Help & Troubleshooting] Glebun:
no, it is not possible, and never will be. just encrypt your phone and the data will be secure
[Sony Xperia T, TL, TX, V] SanketN8:
Exclusive Xperia T Clock Widget :cool:

This Widget is modded and created by me[©Sanket Naik]

Mirroring download link is FORBIDDEN

To Install-

1.Install the NEXUS Clock Widget.apk

2.Go to widgets and select it on your desired home screen

3.Enjoy

4.Comment if u want any other changes

5.Don't forget to hit THANKS

Exclusive Xperia T Clock Widget

​

APK File :good: Xperia T Clock​
[Sony Xperia T, TL, TX, V] josephnero:
Looks nice
[Sony Xperia T, TL, TX, V] charmidz:
affter reboot my phone, it FC :(:(
[Sony Xperia T, TL, TX, V] SanketN8:
sorry for that,just add the widget again :)
[Java for Android App Development] pealiksuurmuna:
I am having a problems with emulating FeliCa tag with ACS122U in combination with S3.

I am emulating a Type-3 NDEF tag, phone NFC service successfully reads the NDEF Message from the emulated card,

starts my own application, and finally, when inside of "onNewIntent" handling for the ACTION_NDEF_DISCOVERED intent,

I see that the tag has following tech listed:

android.nfc.tech.NfcF,

android.nfc.tech.Ndef,

I get the NfcF tech, check if tag is still connected, and call transcieve() to invoke a POLLING command on the tag,

what happens is, I get DeadObjectException, and transcieve call fails.

Here is the stack trace

What can I try to make the transcieve work?

06-13 21:00:47.558: I/System.out(16727): NDEF discovered in onNewIntent, enabling foreground dispatch

06-13 21:00:47.563: I/System.out(16727): android.nfc.tech.NfcF

06-13 21:00:47.568: I/System.out(16727): android.nfc.tech.Ndef

06-13 21:00:48.128: E/NFC(16727): NFC service dead

06-13 21:00:48.128: E/NFC(16727): android.os.DeadObjectException

06-13 21:00:48.128: E/NFC(16727):	at android.os.BinderProxy.transact(Native Method)

06-13 21:00:48.128: E/NFC(16727):	at android.nfc.INfcTag$Stub$Proxy.transceive(INfcTag.java:405)

06-13 21:00:48.128: E/NFC(16727):	at android.nfc.tech.BasicTagTechnology.transceive(BasicTagTechnology.java:146)

06-13 21:00:48.128: E/NFC(16727):	at android.nfc.tech.NfcF.transceive(NfcF.java:119)

06-13 21:00:48.128: E/NFC(16727):	at com.MyApp.MainActivity.onNewIntent(MainActivity.java:244)

06-13 21:00:48.128: E/NFC(16727):	at android.app.Instrumentation.callActivityOnNewIntent(Instrumentation.java:1157)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.deliverNewIntents(ActivityThread.java:2193)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.performNewIntents(ActivityThread.java:2206)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.handleNewIntent(ActivityThread.java:2215)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.access$1400(ActivityThread.java:140)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1298)

06-13 21:00:48.128: E/NFC(16727):	at android.os.Handler.dispatchMessage(Handler.java:99)

06-13 21:00:48.128: E/NFC(16727):	at android.os.Looper.loop(Looper.java:137)

06-13 21:00:48.128: E/NFC(16727):	at android.app.ActivityThread.main(ActivityThread.java:4898)

06-13 21:00:48.128: E/NFC(16727):	at java.lang.reflect.Method.invokeNative(Native Method)

06-13 21:00:48.128: E/NFC(16727):	at java.lang.reflect.Method.invoke(Method.java:511)

06-13 21:00:48.128: E/NFC(16727):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1006)

06-13 21:00:48.128: E/NFC(16727):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)

06-13 21:00:48.128: E/NFC(16727):	at dalvik.system.NativeStart.main(Native Method)
[One (M7) Themes and Apps] legolas63:
How have 4X5 application in the menu DRAWER
[One (M7) Themes and Apps] jimbob456:
In app drawer pull down, click 3 bars, grid size, 4x5
[One (M7) Themes and Apps] legolas63:
Thank you, I'm self-critical, I'm very bad.

Where is the exit?

Again thank you for this little trick.

:fingers-crossed:
[AT&T, Rogers HTC One X, Telstra One XL] exad:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones

all phones go through htcdev.com to unlock, att phones just need supercid first.

you should make a not in your guide that this guide wont work for at&t phones.
[AT&T, Rogers HTC One X, Telstra One XL] nerdo:
Thanks for this important reminder, note added in red on top!

You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!

Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.

So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:

I hope it's in order to add some info for European Evitas :p

guys kindly don't quote whole post(s), thanks
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.
[AT&T, Rogers HTC One X, Telstra One XL] tfngwena:
Great guide, thanks you! it worked ! :)

Now i'm stuck at the next step. ha :crying:
[AT&T, Rogers HTC One X, Telstra One XL] wee2000:
i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.

The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.

i can :

flash RUU 3.17, running a stock RUU 3.17.

unlock bootloader

flash custom recovery(twrp mess with my internal storage)

i cant :

root my device on stock rom

touchscreen wont work on custom rom

any help will b greatly appreciated.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Do not make multiple posts about the same thing. It is strictly against XDA rules.
[AT&T, Rogers HTC One X, Telstra One XL] wee2000:
sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
You cannot
[AT&T, Rogers HTC One X, Telstra One XL] Jawed_ali:
sir how to back or normal cid help me

sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Fastboot oem writecid whateveryourcidwas

This will only work once with s-on after supercid but will work as many times as you want if s-off.
[AT&T, Rogers HTC One X, Telstra One XL] NismoR31:
ignore this post. found a relevant thread
[AT&T, Rogers HTC One X, Telstra One XL] ernstlustig:
How to upgrade bootloader to 2.14

So what if you are not on HBoot 2.14?

EDIT:

Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here

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

and the tutorial for upgrading RUU on a previously modded phone here

http://xdaforums.com/showthread.php?p=26260005

I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.

First you need the superCID from this post:

http://xdaforums.com/showthread.php?p=42351491

Next Step S-Off:

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

Then RegawMOD the appropriate bootloader from this thread and flash:

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

The procedure was easy once I had found the appropriate threads on XDA ;)
[AT&T, Rogers HTC One X, Telstra One XL] exad:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
[AT&T, Rogers HTC One X, Telstra One XL] ernstlustig:
New CM10 and derivates require HBoot 2.14

I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.

The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.

All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.
[AT&T, Rogers HTC One X, Telstra One XL] salt204:
How did you get s-off? i have a rogers version
[AT&T, Rogers HTC One X, Telstra One XL] ernstlustig:
Links to XDA threads updated. (Sorry.) Please look again.
[AT&T, Rogers HTC One X, Telstra One XL] henry084:
Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?

as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.

I have tried the hex with adb method, but it doesn't work.
[AT&T, Rogers HTC One X, Telstra One XL] fly23:
This worked for me. I don't know how many hours I have had searched. I have CM10.2 installed and first the "su" command didn't work.

I had to activate root access in developer options für 'Apps and ADB'. Then it worked instantly.
[MDA III, XDA III, PDA2k, 9090 General] markmills2000uk:
how do i chang the imei on blue angel xda 2s
[MDA III, XDA III, PDA2k, 9090 General] benyeap:
I doubt u can do it easily
[MDA III, XDA III, PDA2k, 9090 General] numanoids:
Also, isnt it illegal in the UK to change the IMEI of a handset?
[MDA III, XDA III, PDA2k, 9090 General] Bassey:
It certainly is. On the grounds that there is only one reason why you'd need to!
[MDA III, XDA III, PDA2k, 9090 General] Bonzo:
Actually, it's very easy!

DISCALIMER:

I take no responsibility for the procedure.

If you loose data, not my fault!

If your device gets borken, not my fault!

If this is illegal in your country, not my fault!

Ok, here we go!

1. Open phone app, and dial *#06#

2. Write down your current IMEI number.

3. Make complete backup.

4. Buy a new device

5. Restore backup.

6. Open phone app, and dial *#06#

7. Confirm that your device now has a different IMEI..

And for the future: Don't buy stolen goods!
[MDA III, XDA III, PDA2k, 9090 General] M4io:
I can do this for you, and it will only cost you 750€
[MDA III, XDA III, PDA2k, 9090 General] Marqnet a Guest:
:lol: LOL sound about right :shock:
[MDA III, XDA III, PDA2k, 9090 General] Derek_Powell:
Actuallly, there are a number of very valid reasons why you may want to change the IMEI of you phone. For Instance.

I have a PDA2k and a Vodafone 7100v with blackberry enterprise account. I recently installed the Blackberry Connect software onto my PDA2K and went to the website to enter the New IMEI number and PIN cod for my PDA2K. This was refused by vodafone because it is not a "Vodafone phone IMEI". So my thinking was to take over the IMEI of the 7100v and the the problem goes away.

Haven't achieved anything yet and if it IS illigal to use one of my IMEI numbers in another of MY phones then the law is an ass.

Kindest regards,

Derek
[MDA III, XDA III, PDA2k, 9090 General] zohaer21:
hi

to those of us that dont live in UK and this rule does not apply (as no legal legislation exists where i live that says this is illegal) we actually might wanna try yhis just for fun.. so does n1 know how to change the imei?
[MDA III, XDA III, PDA2k, 9090 General] nomadman:
This topic also applies to those who baught a used device and didn't know that the emei was blocked by one carrier because of bad credit that was never resolved by the original owner.

Now IF the original owner sold the unit to an unaware buyer, then the buyer would be SOL. IMO, it is NOT the buyer's fault, NOR it is assumed that the unit was "stolen". Some guys here seam to jump into there own conclusions.
[MDA III, XDA III, PDA2k, 9090 General] AlCapone:
still no news on the IMEI changing ?
[MDA III, XDA III, PDA2k, 9090 General] Pyrofer:
It is illegal in the UK to change the EMEI, it doesnt matter why you are doing it, its just illegal. End of story. If you get caught doing it, you get arrested.

To be honest, there are NOT loads of reasons youd want to legally change the emei, so far 2 have been presented,

1> vodaphone emei required to do something on phone

2> previous owner had bad credit and sold on phone

Case one, rare. A pain, yes, but rare so I dont think anyone will go to all the effort and law breaking to solve just this.

Case two, even rarer. And for the person in this situation, they could just call the network and explain it to them, its possible the block would be lifted if its not actualy a stolen phone.

I beg people to stop asking about EMEI changes on here, we dont want this board shutdown, and I can garantee that will happen if an emei tool appears. Its GOOD that you cant change the emei because this board isnt a place for criminals as it would be if emei tools were supplied.
[MDA III, XDA III, PDA2k, 9090 General] nomadman:
Yes it's illegal. IN YOUR COUNTRY. In your Case 2, the network would be glad to meet with you so they can confescate the phone since it was not paid for. The original owner left the country and never came back. Anyway, I seam to recall there was a way to change the EMEI on the MDA I.

Unless there is a rule posted on this board about asking for something like this, people will always ask. I think it should not be a board rule because it doesn't apply to most counties.
[MDA III, XDA III, PDA2k, 9090 General] Pyrofer:
And because its illegal here then its ok for people in other countries to help criminals here?

I was posting to a UK person, trying to help them avoide legal trouble, and it does apply to people in many other countries. Its just not a good thing to do, has little legitimate merit, and is a lot of work for little reward.

I dont know of any country that welcomes reprogramming of phones so why not stay away from it to avoid bringing trouble on the board?

Just because some countries havent made a specific law against it, it doesnt mean its a good idea.

And it the original owner of a phone sold it without paying for it, then it IS a stolen phone. Buying stolen goods is buying stolen goods, if the network would confiscate it back, then you ARE doing something dodgy by reprogramming the emei, therefor removing case 2 from my legitimate reasons list. So we are left with this one bizare rare case where its needed.

All that legal risk for that?
[MDA III, XDA III, PDA2k, 9090 General] nomadman:
If you were trying to assist member from the UK, then state so. But making it a board rule affect every board member, not just the ones who live in the UK. I guess the site admin you have to decide about the rules. Neither you or I admin of this site, so I guess we have no say either way. If you are an admin, then you can keep me from posting the EMEI changer when or if it is released.

You have just insinuated that I knowingly bought stolen goods from the original owner. If I had know that there was a problem like this before hand, I would not have given my $600 to the person that sold it. Would you give back the unit knowing that you will not get the money back from the original owner? What sane person would? If the network told me that they would refund my money, I would gladly give it back and buy a new one. Since that isn't happening anytime soon, I will not not be discuraged and make the best out of my predicament. If the Johnny Law catches up to me, then so be it. At least I knew what the consequences are and that I had a choice. No one on any forum can tell me what I can and can't do to anything I own.