yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] josh995:
Since you are a new user I will help you with a little more depth, I hate seeing new users mess up their device. Give me a second to get it together and I will edit this post with some helpful info.

(EDIT)

OK so Follow the instructions on this page ( http://xdaforums.com/showthread.php?t=2416431 ) to get a custom recovery. It's TWRP, and I like it a lot. I love that it's touch, because I remember using amon ra on the HTC Evo and you had to use the volume up & down + power button to navigate the menus and it was sometimes very easy to make a mistake. This touch recovery eliminates that.

Next, go to either the original android development OR the android development section of the Verizon HTC One and choose either an AOSP rom or sense based rom. So far I've used the Google Play Edition rom and now I'm on andy's bonestock and have really liked them both.

Make sure any rom you ever flash is compatible with your phone, very, very important. if you don't know, just ask. MOST users on here are friendly and will say yes or no and not give you a hard time.

Roms are very easy to install. Just download the .zip, I download it straight from my phone, but you can also download on your computer and then transfer it to your phones storage.

(thanks to andybones advice, I have started checking the MD5 of the rom. Devs include it in thread of the info of the rom here on xda, and once you have the .zip on your phone, use a file manager to view the MD5 and compare it to what the dev has put in their thread. If it matches, you're good.

Then boot into recovery and DO A BACKUP OF YOUR STOCK AND KEEP IT!! Everything you need to backup is already checked with TWRP so that's helpful. Once you're done with the backup, then do a wipe. I wipe SYSTEM, DATA, CACHE, & DALVIK CACHE. Then, go back to the TWRP main screen and select install. Find the .zip you want to install and flash it. Some roms have aroma installer so it will bring you to a special screen that allows you to select options you want to have in the rom. check the boxes of the apps/options you want in the rom and follow the 'next' prompts until the rom installs. After you're done, reboot, set up your new rom and enjoy it!

If anyone more experienced than me has any info to add to this, feel free.
[Verizon HTC One (M7)] JonrossMaddox:
Okay so I am kind of stuck, I have tried on Ubuntu, Windows, and Mac, but I cannot get my device to show up under fastboot command. Why wont it? I rebooted into fastboot from the bootloader.

EDIT: Nevermind fixed, I didn't realize it couldn't be booted into the OS.
[Verizon HTC One (M7)] WhiteAsIce:
Just to make sure I have the steps correct:

1) S-Off the phone

2) Unlock bootloader via htcdev or other methods posted on this forum

3) ???

4) Flash a recovery

5) Flash a rom

Are we supposed to do anything between unlocking and flashing a recovery?
[Verizon HTC One (M7)] jpradley:
Before flashing any rom, you should make a backup, so that you can revert to a prior iworking state, in case the rom doesn't run or doesn't please you.
[Verizon HTC One (M7)] Zwitterion:
Can Someone Sticky This, or Create a Thread to Stick This? Then people can be pointed to it.
[Verizon HTC One (M7)] jackblack91:
just went s-off

I just successfully ran Rumrunner on my HTC One GSM and now I am leery about flashing Roms on my device. I'm currently using Twrp 2.6.3.3, and is wiping SYSTEM, DATA, CACHE, & DALVIK CACHE really safe? Cause before I would do a advance wipe for every new install..

And, is there a way to revert back S-on without locking bootloader? Cause every method I've looked up restores to stock..

Thanks in advance!
[T-Mobile Samsung Galaxy Note 3] AG0087:
I can't get it off and dont know how it got there. Anyone? Thank you.
[T-Mobile Samsung Galaxy Note 3] rickm8384:
Nfc
[T-Mobile Samsung Galaxy Note 3] kuroy301:
NFC is ON

Go to settings, then connections scroll down and make sure the NFC is OFF...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] garciacr10:
Hello Guys... i have bought a at&t galaxy s4... the phone was locked to at&t i bougth an unlock code on ebay.. cuz i want to use the phone on t mobile... when i inserted a t mobile sim card.. the phone says no sim.. so i get a sim card from simplemobile then so i put simplemobile sim card and phone ask me for a unlock code i put the code i bougth on ebay.. and says unlock sucefully .. now i can use simplemobile... but when i try using my t mobile sim card the phone still saying no sim.. i also try my friends sim card he is using a S4 too... and still says no sim.. the i try my father's t mobile sim card and the same no sim

does anyone can help me please.. i have my plan whit t mobile.. i dont want to switch to simplemobile
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
The SIM card may be locked to the device it was activated on. I suggest going to a T-Mobile store to see if they can help.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] garciacr10:
i tried 3 sim card ... DId they lock all the sim cards?? .. thanks for the suggest i will go to t mobile today
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
It is likely that they lock the cards to the device that the card is activated with. It seems like it is the only possible reason that you can't use T-Mobile cards.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] garciacr10:
I went to t-mobile. They tried another sim car and the phones was the same no sim... the said that the problem was with the phone cuz the sim cards are news and working on other phones... i dont know why the problem is only with t-mobile sim cards.. they say that if the phone was from t-mobile they could change me for another phone but it is at&t.... do u you think that it will be any problem if i go to at&t and tell the that my phone is unlocked but it doesnt read t-mobiles' sim cards
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
They could help. Might as well try. It is a very weird situation. If other SIM cards are working with it, it shouldn't be the phone...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] garciacr10:
Yes the problem is only with t-mobile... but i will take the phone to at&t tomorrow
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] graydiggy:
Is it possible that you didn't unlock all the bands on your device? There is a tutorial around here somewhere that shows how to unlock all the bands for use with absolutely any carrier. From my understanding it is different then just unlocking with a code.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] garciacr10:
Yes but it should said invalid sim car or ask me for that code when i insert t-mobile sim card... but the phones says no sim.. it doesnt even read the sim.... and when u unlock with a code i think is like factory unlock cuz my father unlock his phone with a code and his phone works fine
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] garciacr10:
I went to t-mobile and at&t and they said that the problem was problably with the phone.. and they can do nothing to help me... so i sold the phone.. i will get another
[General Topics] Dubhead:
Hello,

I will be travelling to Hong Kong over Thanksgiving holiday and was wondering if there was a good contact for HTC products at wholesale. I am interested in distributing/purchasing some of these and would love to get in contact with a wholesaler. Please let me know if anyone has any suggestions for where to find these devices there and/or contacts I could make. Thanks for all the great information on this site! Keep it up!

David
[General Topics] shu_sum:
The distributor of Dopod in Hong Kong is called "SiS International":

http://www.sis.com.hk/
[Verizon Samsung Galaxy S 4] thunderbls:
Here's my sugestion ...delete what you have on sdcard for the root process..put the zipped file on the root of your sdcard... Download a zip extractor app(free on play store) use it to extract the zipped root file straight onto your sdcards root dont change anything then follow the instructions from there in the emulator.
[Verizon Samsung Galaxy S 4] k1mu:
I answered this in the General forum "all things ME7" thread.

The problem is that when the root zip file was unzipped, all of the files were extracted to the root directory.

You need to unzip and create the proper folder structure on the sd card - then it'll work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mr.squiggly:
Hello everyone,

I was fedup for my samsung bloatware and stuff so I decided to root my device and was using CM 10.2 for sometime.

so far I liked this custom ROM. But due to some touchwiz specific features I want to go back to the touchwiz UI, specifically for camera, multi window etc. but the bloatware which comes free with it scares me off.

so can you please suggest if there is any custom ROM available which is based on touchwiz and at least provide android 4.2.2 if not 4.3

or if there is any other ROM out there ( non touchwiz based ) which does provide samsung camera and multi window functionallity.

with thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
What you need to do is have a look at development forum and look thru the roms available for the features you require. that's your best bet at finding what suits you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
^^ This ^^

As these threads usually spiral into arguments about which rom is "better" than another and are full of opinion, this thread is closed.
[Nexus 7 General] Basener:
I purchased a bluetooth keyboard (an ezoware bluetooth keyboard ) and it turns out that it's incompatible with my Nexus 7 (32gb gen 1, droid v4.3)

I read that v4.3 has issues with bluetooth keyobards that 4.2.2 did not, and thus I am wondering if my best course of action is to revert back to 4.2.2, and the BEST way to do so.

I already found a zip with the 4.2.2 rom.

There's little other possible issue with compatibility because for one 4.2.2 is a very recent release and for two this particular tablet will be used near exclusively for word processing.

Help would be appreciated.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
This is a work in progress. All that is needed is now are the correct libs or a lib fix. Tap and Pay will not even attempt to set up with the stock build.prop. What you have to do is change the build.prop to the Galaxy Nexus and then it will have you turn NFC on and attempt to set up the phone but we will need a lib fix much like for the S4

​

IMPORTANT INFO AND LINKS - PLEASE READ - ESPECIALLY AOSP USERS​

​

Work in Progress - Method 1 - Preferred - This will be what it looks like - Universal for TW/AOSP/Deodex/Odex ROMS

1. Make sure you don't have the wallet apk installed and if you do, wipe the data and cache of the app, then uninstall or if you have it in the system, delete it.

2. Make sure you turn off "auto-update" in the play store for the wallet app.

3. Download

TouchWiz Only----> DO NOT DOWNLOAD YET!! Patched Wallet & NFC Lib Fix

AOSP Only----> DO NOT DOWNLOAD YET!! AOSP Wallet

4. Change build.prop to Galaxy Nexus - Use Jrummy Build.prop Editor (Changes did not stick with reboot) or Root Exolorer - (DO NOT RESTART UNTIL ALL 3 PARTS ARE CHANGED)

Galaxy Nexus

ro.product.device=maguro

ro.product.model=Galaxy Nexus

ro.product.name=yakju

5. Reboot into Recovery

6. Flash Note 3 Libs You downloaded in Step 2 - (ALWAYS WIPE CACHE AND DALVICK BEFORE FLASHING ZIPs)

7. Reboot Phone

8. Open the wallet app and start the setup. Wallet should already be installed from when you flashed the zip in recovery! It might take some time, so be a bit patient. (Make Sure NFC is ON)

10. Set Up Tap and Play so it's 100% and ready to make purchases (you should see the credit card you have on file - if not Add One).

11. Reboot again, just so you can test

12. Change Your build.prop back to stock once you verify Wallet Opens with no issues

T-Mobile Galaxy Note 3

ro.product.device=hltetmo

ro.product.model=SM-N900T

ro.product.name=hltetmo

MORE INFO

Give Thanks To:

Hopefully Can Fill This In Soon!

If you were left out its not by intention just PM Me
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
CLICK RED LETTERS....... IT IS A LINK ON WRITE UP TO MODIFY NfcNci.apk to use secure element

Based on this read, all I think we need is the nfcee_access.xml with the google Keys which I already have.....and then we need to modify the NfcNci.apk

As far as the libs go, they might be extra, however they don't cause harm being in the system at all....I want to try with and without...I will if I can learn how to decompile the apk like in the write up. Pretty close to an answer at this point
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Got the Release Keys from AOSP ROM and got past the error above but Wallet is foreclosing......I have tried pulling the libs from sprint but im sure there is some framework edits minor if at all. Giving it a rest tonight...Reaching out from help and keeping a look out on progress
[T-Mobile Samsung Galaxy Note 3] firefreak664:
Op I don't know if this will help you any but it worked well on my old s3 alot of people claim it works on the s4 you might want to check it out.

http://xdaforums.com/showthread.php?t=2457569
[T-Mobile Samsung Galaxy Note 3] darkjedi:
Just to warn everyone, as it says in the OP, do not flash that package at all. Especially since TWRP restoring doesn't work.
[T-Mobile Samsung Galaxy Note 3] TheNewGuy:
Glad you are taking this project on!I'll I can't wait until you get it figured out! Keep up the Good work!
[T-Mobile Samsung Galaxy Note 3] wing_addict_usa:
Anyone try ISIS?

It's ****. They disable amazing gwallet for this stupid proprietary ****.

Doesn't work on root, only supports 3 card companies.

Note 3 came with isis card and bloatware, yet they forgot this app. Avoid this trash. They are cowards.

Let's get gwallet working :)
[T-Mobile Samsung Galaxy Note 3] siraltus:
It works on root if you install the ISIS Root Bypass mod for Xposed.

That said, it is utter garbage. Slow, clunky, poorly laid out, and generally trash. Good it uses the secure element in the ISIS SIM card and not in the phone so you can use Google Wallet concurrently.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Def am looking at that, thanks for that info, I am trying to pull from the international version as well as any CM bases
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
[MENTION=1195110]bdorr1105[/MENTION] I see something in the zip that may be causing an issue....

system > lib > hw > nfc_nciMSM8960.so

MSM8960 is for dual core qualcomm not quad core. For Note 3 it's nfc.MSM8974.so

If you're going to add a nfc_nci patched file, it'd still have to be MSM8974 I believe...
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Yea thanks I have the MSM8974.so from the sprint Note 3, thats what I am pulling from as well as from the international and seeing what works. Those zips are for the Note 2, its just an example, I didn't remove the links from my other OP, I am just giving a preview of what the OP will look like
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
AH I see ok gotcha. Great, if anything comes to mind I'll let you know bro...
[T-Mobile Samsung Galaxy Note 3] thinkjoey:
huh?

Restore worked for me....
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Thanks appreciate it
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Which version are you using?
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
So I tried everything so far, libs, etc, I noticed that NFC will turn on with the NFC apks, but when you swap back to the originals NFC turns on, I am still stock and I think ODEX has something to do with it, I will experiment now on the Deodexed ROM and see what happens.
[T-Mobile Samsung Galaxy Note 3] thinkjoey:
I am trying to find it. I guess i can go into recovery

i have v2.6.3.1

I had to restore yesterday when something did not install alright...restored fine
[T-Mobile Samsung Galaxy Note 3] itsmikeramsay:
Yeah I'd recommend using a deodexed ROM... Try stock deodexed....

Ok cool, seems the most stable is 2.6.3.1, users can't restore with x.x.x.0 or x.x.x.2
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Def trying stock deodexed, the libs are not named the same either....

I can give examples from the lib folder....changing any of the names of the Sprint libs to match TMO Stock don't work, but I think i was on to something, I think the can coexist together, and it will use depending on the nfc.apk, but ODEX cause me issues, I redolved the Google RSA Keys issue, thats bypassed, if I can get NFC to turn on after the lib swap then hopefully will be good. the NFC Access is good to go. I know it didnt force close NFC until I went back to the stock NFC apk
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
No luck still....wallet force closes, not exactly sure what is causing it. I switched the NfcNci.apk and NfcTest.apk with Sprint and it broke NFC....went back to stock and NFC turns on. I can only fix Insufficient RSA Keys.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
OK then yeah I was meaning something else..... Thanks
[T-Mobile Samsung Galaxy Note 3] siraltus:
More news pointing to an updated Wallet platform that won't need a secure element:

http://www.geek.com/android/nexus-5...le-wallet-that-works-with-all-phones-1575354/

The upcoming Nexus 5 does not include a secure element, just like the 2013 Nexus 7. The "Settings" menu in Android 4.4 KitKat now includes a "Tap and Pay" item.

It would be the dumbest thing for Google to release a flagship phone that doesn't support Wallet, so I'm pretty damn sure KitKat will include a Tap-and-Pay framework that will not rely on a hardware secure element and Wallet with Tap-and-Pay will become available for all NFC-enabled phones.

This will be a huge win for Google in the NFC-payment market as carriers will no longer have any leverage of blocking them at the hardware level. They can (and likely will) still choose to disable the new tap-and-pay framework in their stock ROMs, though, but that's what XDA is for. ISIS is getting a big F-U from Google, finally.

For those of us preferring the Samsung stock ROM, which will be stuck on 4.3 for a long time, we'll probably be SOL, unless a very brilliant Dev figures out how to perform miracles and backport the framework (not very likely given there will be TONS of changes from 4.3 to 4.4).

For those of us who prefer to run AOSP-based ROMs like Cyanogen, it will only be a matter of waiting until 4.4-based ROMs are out. I'll personally be ditching Samsung stock as soon as Cyanogen starts building nightlies for our phone.
[T-Mobile Samsung Galaxy Note 3] nightfox11:
http://www.androidauthority.com/and...low-end-phones-leaked-document-claims-312750/

Yep let's just wait until 4.4 kitkat is here !

sent from my Mighty Note 3
[T-Mobile Samsung Galaxy Note 3] siraltus:
Aaaaand it's official: http://developer.android.com/about/versions/kitkat.html#44-hce

This can go two ways for stock ROM users - either the carriers force Samsung to somehow disable this framework and ISIS continues using the secure element in the SIM cfard, or ISIS updates their Wallet app to use this new framework and carriers leave it enabled, allowing Google Wallet to coexist. Personally, I'm not counting on the latter, but who knows - hopefully the HCE framework will at least remain enabled on non-carrier-customized stock ROMs.

Of course, if you prefer AOSP ROMs like Cyanogen, you will get this as soon as they rebase with KitCat 4.4 code.
[T-Mobile Samsung Galaxy Note 3] gakio12:
I'm excited for this. No more secure element required. I was afraid I wouldn't be able to put Wallet on my note 3 (even with Cyanogenmod). Now with 4.4, I will definitely be able to. Even if Samsung disables that framework, I'm sure devs will figure out how to put it back in (with or without root).
[T-Mobile Samsung Galaxy Note 3] siraltus:
Keep in mind Samsung disabling HCE only matters for stock ROMS; on Cyanogen and other AOSP ROMs, we'll have it for sure. :) They already have the 4.4 source code so I'm guessing nightlies will appear sometime in December.
[T-Mobile Samsung Galaxy Note 3] gakio12:
I'm just waiting for CM for the Note 3, 4.4 or not :laugh:. I got this phone over a Nexus 5 because I need a stylus, TouchWiz makes me regret it :crying:
[T-Mobile Samsung Galaxy Note 3] siraltus:
You and me brother. Plus the huge removable battery, bigger and AMOLED-based screen, and SD card slot, and the extra gig of RAM.

Hang in there, should be a couple of weeks until we have 4.3 nightlies. :D

This is a Snapdragon 800 phone, so it will be MUCH easier to bring up and maintain than the Exynos 4 nightmare that was the Note 2.
[T-Mobile Samsung Galaxy Note 3] nightfox11:
well according with David Ruddock " In theory, every Android 4.4+ device should just work with Google Wallet as long as it has NFC. Being part of the core Android OS also means carriers and OEMs can't strip out the functionality, as it would be a violation of their CTS certification agreement with Google. Stick that in your pipe and smoke it, Verizon".
[T-Mobile Samsung Galaxy Note 3] gakio12:
Bam.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
And a big middle finger to AT&T and T-Mobile
[T-Mobile Samsung Galaxy Note 3] siraltus:
Even better. Finally!
[T-Mobile Samsung Galaxy Note 3] @rbiter:
Yeah Samsung needs to get in the ball and give us 4.4 already.

sent from my sm-9005.
[T-Mobile Samsung Galaxy Note 3] blacklabel2020:
Updated NFC

The new NFC mechanism on Android 4.4 allows users to store important information, such as credit card details, on their devices in NFC powered apps like Google Wallet, without needing to access to the secure element on SIM cards. Now the secure element, which keeps important information safe from prying eyes, is controlled virtually by Google and not mobile carriers, which should now allow NFC powered applications to flourish on Android.

http://www.ibtimes.com/android-44-k...new-flavor-android-check-out-details-its-many
[T-Mobile Samsung Galaxy Note 3] TheNewGuy:
Did anyone read this article I linked a few pages back?

http://arstechnica.com/gadgets/2013...ntrolling-open-source-by-any-means-necessary/

I admit kit kat sounds great! And it sounds like Google did a lot of great work, I think the guy who wrote the kit kat description is right. This is the android update we have been waiting for.

Problem is I feel like I am falling for their plans by liking it.

Google will "own" my Android os more then ever before. And if that article I linked is true,(and I understand it) and Google closes development on the open source branches, while steaming ahead advancing the usability of there own proprietary api's. Then soon no one will be able to keep up... imagine no home replacements.... Because if you do, you loose the great "all tied together" features in the Google home... And those features are googels.

By the time ADW writes their own code to achieve the same thing, Google is on to the next thing we all love and can't live without.

Am I wrong? Can someone tell me where I went wrong and why this is all ok?
[T-Mobile Samsung Galaxy Note 3] @rbiter:
Google would shoot itself in the foot closing android. Devs and many fans of open source would move on. I don't have a problem with Google doing what they're doing right now. It has actually helped android a lot. I do hope Google gets 64 bit android right. Even better I wouldn't mind a rewrite of some of the code to optimize it more. Dalvik VM is hurting it now. The 64 bit rewrite would be the perfect opportunity for Google to do this as it wouldn't alienate anybody because we'd all have to get new hardware sooner or later.

sent from my sm-9005.