yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] supratikbose:
In India 802D dual sim is released. But I want to use 802W. I wonder will there be any problem ? Any comment?

This is a review I read in flipcart (Indian online retailer):

"So please be careful before ordering which model number you order as per my research on chinese web site and XDA forum:

- HTC One 802d is CDMA variant i.e one sim slot for 2g and other slot for CDMA i.e will second sim will work only with operators like MTS, Reliance CDMA and TATA CDMA

- HTC One 802w is 3G/WCDMA variant i.e one sim for 2g and other for 3G/WCDMA i.e both sim will accept more popular providers like Airtel, Voda, Idea, Docomo, Reliance GSM etc. so it can work in 2G+2G or 2G + 3G/WCDMA"
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
I think these could help you ;)

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

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

If you found my posts helpful, Please click thanks :good:
[One (M7) Q&A, Help & Troubleshooting] karimin:
So to sum up everything here.

802w - [Slot 1 gsm (2g) / wcdma (3g)] + [Slot 2 gsm (2g)]

802d - [Slot 1 cdma] / [Slot 2 gsm (2g)]

So in countries with no CDMA (which is almost most of the world) a 802d will be like a phone with 2 sims both can NOT connect to 3g (nor 4g since there is no HTC one m7 dual have 4g) so u are stuck with E - EDGE & G - GPRS

With no H - HSDPA or H+ - HSDPA Plus WHICH MEANS u can not accept the internet from ur phone on SPEED FASTER THAN 384 kb ( 0.375 MB Speed)
[AT&T, Rogers HTC One X, Telstra One XL] rancor22:
Just did a dirty flash from 7-19 to 8-10 and bricked my device. My computer is saying it is connecting(sound) but there is no response from the device, no lights or anything. Holding the power button will get it to disconnect and then quickly reconnect.

On the first boot after flashing the device it did turn on and start the boot process but then rebooted with the CM logo on the screen and went into this state.

I am hoping this might be fixable by me because might still be connecting to my computer.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Try holding down the power button for like a minute and if that doesn't work, then plug it in for a few hours and see if it turns on.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] rancor22:
I have tried holding down power, I am going to try out JET the phone might be in Qualcomm download mode

Windows says its in Qualcomm HS-USB QDLoader... looks like its compleatly bricked. Is there any way to fix this other than sending it to HTC?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You can try the Evita unbricking thread, but if you can't enumerate your partitions using that your only other options are jtag repair or HTC repair. Jtag is the cheaper of the two.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] rancor22:
Looks like i cannot get it to enumerate, do you know a good place for jtag repair?
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
i dont see how you could of bricked. i received qhsusb_dload when flashing the icecoldjelly evita port but got it back up in a few minutes with hardware key combinations. i could get see how that qhsusb_dload could of made most people freak out and instantly think jtag time.
[AT&T, Rogers HTC One X, Telstra One XL] rancor22:
Well the hardware key combinations don't work, and the device wont enumerate when I try to follow the unbricking guide. It seems odd to me too that it bricked its self in the boot process and maybe i am following the guide wrong but ever thing i have done so far makes me think I need a jtag fix.
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
I guess everyone should run this to make sure their phone won't be prone to any future bricks caused by their emmc.

eMMC Brickbug Check
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Phones with chips that have come back sane are still bricking, so that's not the only cause of the problem.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] rancor22:
This phone was a "sane" phone. The bricking was actually the reason I upgraded because the kernel was supposed to have the fix to keep the phone from bricking (even though I didn't need it because of the "sane emmc chip).
[MDA II, XDA II, 2060 General] rictec:
i just took two print this is what ?

its buzz 2005 honestly but can you see the diferences ?

this is what i get with reser in landscape mode...

who knows?
[MDA II, XDA II, 2060 General] toenailed:
its a known bug bro of wm2005(all version)

solution is not to reset the device in landscape or if you mistakenly soft reset it just set it back to portrait

anyway there is a registry settings for that .. i once posted it in the other thread .. :)

-toe
[MDA II, XDA II, 2060 General] rictec:
find something else also

the tap screen stays in landscpe so the start screen open if you tap botton left near the bue line

it must be something with the grafics only

if you manage to get to control pannel and align the screen the almost everything is working
[Nook HD, HD+ Q&A, Help & Troubleshooting] thatguythat:
I am going to be installing cm 10.1 sometime this week, but first I wanted to know if I would still have the barnes and noble shop app and the nook ereader software.
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
If you install CM10.1 to internal memory, no. It replaces stock and those things only work on stock. However there is an Android version of the Nook reader app that works on CM10.1.

But if you install CM10.1 to SD, stock is left intact and you can dual boot.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] thatguythat:
What is the nook reader app that works on cm and just so you know I plan to install cm to internal memory so it will run better.
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
It is the Android Nook Reader app that is usually on Play Store. But unfortunately Play Store blocks installing it on the HD/HD+. The solution is to get it on the 1mobile.com store.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] thatguythat:
Thanks. Also, can you download books from barnes and noble's site for reading on the app with cm 10.1 installed?
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
Yes, the Android Nook reader app gets your purchased books for you on CM10.1.
[Nook HD, HD+ Q&A, Help & Troubleshooting] thatguythat:
Thanks! And last of all, could someone give me a link to a video showing how to install cm 10.1?
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
I know of no video, but the CM10.1 dummies guide has got rave reviews for simplicity.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] darien87:
I concur. I used the dummies thread and I got it done on the 2nd try. It's a tad scary but if I can do it anyone can.
[Xperia Arc Q&A, Help & Troubleshooting] AjayRockstar:
I probably used ics roms-ultimate hd and blue ice but it have ram issues.so i changed to gb rom-x stronger and i put some init.d tweaks on it but not working.so I enable these mods[firstboot from Xperia play,adrenaline boost] by terminal emulator all works fine but after I have battery issues.it drains 1% within 2-3 minutes.I flashed stock gb(.42 firmware using flashtool) but firstboot mos still on it.what can I do?how do I disable these mods?Please help me.

I tried wipe battery stats but nothing works.Is there is anyway to full wipe phone(means deleting the whole of tool directory like acc,data,root,sys,system,vendor etc folder) and flash 2.3 on it?
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
For full wipe, wipe the following using CWM:

/system

/data

cache and dalvik cache.

Then reflash stock GB and see if it works fine after that.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] AjayRockstar:
Bro i already full wipe cache,factory data,dalvik,battery and i also reflashed both ics and gb but nothing works.
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
Here is a message from Bajee Baskararasa the creator of Rootbox ROM on Google+:

"Bajee Baskararasa - 23 minutes ago

Hey guys I know I've gone missing from G+ and XDA but I've been extremely busy with work these past few days. Unfortunately I won't be able to invest any time for RootBox for at least a week or two. I planned to get 4.3 builds rolling by this week or so but my situation clearly didn't allow that to happen. I'll try my best to set aside time for RootBox but since I got this new job it'll take some time to adjust myself and get a proper schedule. Another factor that will eventually impact my time is University starting in about 3 weeks.*So enjoy stable V4.2 build for now (which I'm running as well) or you can *always try out other roms who released Android 4.3, until then enjoy the summer and the good weather! (wherever you are)

Post this message in your device's thread. Thanks +Myles Nystrom*in advance since you will eventually post this message in almost all the threads ;)"

I think this says it all....enjoy the summer and enjoy V4.2
[Verizon Samsung Galaxy S 4] jova33:
Except data don't work for our phone :(

Edit: unless you know something I don't.
[Verizon Samsung Galaxy S 4] winkx01:
On the 4.2 build, I could intermittently get the data to work by messing with settings in the network settings. I just turned LTE off/on a few times, then turned data off/on a few times, and also would cycle airplane mode. After doing these things randomly, I eventually got data to turn on, but it doesn't stick. If you turn data off or reboot, it back to not functioning and I have to try getting it to work again. It's very strange.

JamesPumaEnjoi, do you maintain this device at all? if not, do you know who to direct this problem to? The data worked fine on the 7/3 nightly, but hasn't worked correctly since that. I've seen a few posts on G+ Rootbox community about it, but they get very few responses.
[Verizon Samsung Galaxy S 4] jova33:
I wish I knew a dev that could have a looksee at it. Bajee is maintaining this for like 20 devices, with a few maintainers for their specific device. I mean, I emailed Bajee directly about it lol, but it probably landed in his "waa waa waa! This is broke!" mailbox.
[Verizon Samsung Galaxy S 4] winkx01:
Yeah, I'm not sure why no one has fixed it yet. It would be one thing if the problem was trivial, but data is a pretty important thing on a smartphone. I'm pretty sure it's one of the only roms that has this problem. It also happens to be the only rom I want on my phone! Lol! I've even gone as far as making a build box and attempting builds myself, but still haven't had luck getting things to work.
[Verizon Samsung Galaxy S 4] jova33:
Someone else I asked to look at it said it must be the drivers. It's stuff pulled from three different ROMs that do work on our device. I might start building and putting stuff together like Frankenstein
[Verizon Samsung Galaxy S 4] winkx01:
yeah, I just don't know enough at this point to pinpoint the cause of the problem. I wish I knew more.
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
He's just been super busy lately 4.3 will be out soon enough
[Verizon Samsung Galaxy S 4] jova33:
Well something was up with data on the Rootbox builds fir 4.2.2. Was he aware of it?
[Verizon Samsung Galaxy S 4] winkx01:
Well, only 1 official rootbox build for verizon in the last month and a half (including 2 "stable" builds) has had working data. I don't know how it can be considered stable with data problems, but maybe that's just me. I'm not knocking Bajee or anything, since he has a lot on his plate... it's just a little frustrating is all since that's the only issue I've seen on the builds and it hasn't been addressed.

If any there's any dev that has any ideas on how to get data working properly, I know there's a few of us who would greatly appreciate it. I've searched all over for details on how to fix no data, but had no luck in finding a solution (tried porting the rom, swapping lib files from working roms, building my own build)... I've also got a logcat of the data not working, then turning on for about 3-4 secs and turning back off, if there's someone knows how to interpret them.
[Verizon Samsung Galaxy S 4] jova33:
Something to do with the RIL?
[Verizon Samsung Galaxy S 4] winkx01:
I tried looking into any RIL files from the 7/3 (working) and 7/7 (next nightly stopped working) releases to see if that might be it, but I don't know enough to determine if it was a problem. I also checked the changelogs between those releases on rootbox(dot)basketbuild(dot)com to see if there were any specific changes that might have affected the verizon s4. There were 2 commits that I'm not exactly sure how they affected things:

7/4: "jf: revert ril changes"

7/6: "jf: bring back samsung ril. problems with slow data on certain modem"

I'm definitely an amateur when it comes to dev stuff though, so I would need someone else to explain if these might have been what broke data again. Either way, I'm slowly learning more about building, github, and such.
[Nexus 7 (2013) Accessories] virus86:
Which type of NFC tag works on the new Nexus 7?

I use NTAG203 versions and they work on the HTC One, S4, and the Nexus 7 2012 version.

I thought my NFC was broken on my Nexus 7 2013, but Android Beam worked with my S4.
[Nexus 7 (2013) Accessories] Phamwich:
I have a few NTAG203 stickers I had gotten to use with my HTC One, and they also work with my Nexus 7 as well. It's just a little awkward having the NFC reader right in the center of the back of the Nexus 7.
[Nexus 7 (2013) Accessories] player911:
My tags like the N of Nexus on the back. I haven't gotten mine to work anywhere else.

I have some of the 203s.
[Nexus 7 (2013) Accessories] Kenny B:
nfc tags

What else can be used besides the 203's. Iv been looking everywhere. I can't find anything about the nexus 7 2013 and NFC tags.
[Nexus 7 (2013) Accessories] rmm200:
Check with Tagstand. They have a plethora of tags, as well as the best NFC apps in the app store.
[Nexus 7 (2013) Accessories] Kenny B:
Thanks but that still doesn't tell me what type of NFC tags work with the new nexus 7. I went to their site and no mention of what tags work with what device. The best I found is that under some descriptions it says "works with most phones".
[Nexus 7 (2013) Accessories] rmm200:
Everything I have bought from them works with my new nexus. I can't tell you part numbers though. Good guess would be any tag made for NFC. You could also call them.
[Nexus 7 (2013) Accessories] player911:
Why don't you want to use the 203s? That's the most common. Just buy some and be done. NFC tags use a standard so they should all work. Various chips mostly differ by size and range.

I did a big project with 30 N7s and wristband NFC tags. They cheaped out and bought a different chip and it didn't work. Complete waste of like $4,000.

The 203s work well and recommended. I haven't tried a bunch
[Nexus 7 (2013) Accessories] wilsonlam97:
I have a thread in the Nexus 4 accessories section talking about Tagger.ca

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

They sell Topaz 512 chips and it's only $7 for 10. I can confirm compatibility with the Nexus 7 2013, Galaxy S4, Nexus 4, and Galaxy Nexus. Just a few weeks ago they sold the NTAG203 but now they seem to have gotten rid of it. It's a really great deal if you ask me.
[Nexus 7 (2013) Accessories] toxicpaulution:
I had just ordered them tonight and will report back when they come. I wanted the black nfc but it will work either way.
[Nexus 7 (2013) Accessories] virus86:
I still cant get my NTAG203 to work on my new Nexus 7.

http://www.amazon.com/gp/product/B00AJPSTLS/ref=wms_ohs_product?ie=UTF8&psc=1

Edit: Format/erase didnt help. Im going to exchange it. Good thing Im still within the 15day return policy with BB.

Edit: Exchanged worked. My NFC sweet spot is at the U.
[Galaxy S 4 Q&A, Help & Troubleshooting] turkim:
I dropped my Galaxy S4 (i9505) and the screen was broken, also touch is not working.

My question: is the replacement screens for i9500 compatible with i9505?

I see Amazon selling replacement screens that says they are compatible for both models, but the local dealer says that they are not compatible, and I'm waiting for the display part to arrive since 15 days now (I'm not in the US)
[Galaxy S 4 Q&A, Help & Troubleshooting] turkim:
Any help is appreciated.
[Galaxy S 4 Q&A, Help & Troubleshooting] gee2012:
The screens seem to be the same for all S4 variants, scource http://www.ebay.com/itm/US-Samsung-...reen-Digitizer-Touch-Lens-White-/230982528483.
[Sprint HTC One (M7)] deadhead_fred:
If the verizon htc one is launching with 4.2.2 shouldn't the red htc one on sprint launch with it and shouldn't we get an update shortly after?
[Sprint HTC One (M7)] Tilde88:
no
[Sprint HTC One (M7)] sauprankul:
We have no way to know for sure. We don't know for sure if the red One is coming to Sprint. We don't know if Verizon is getting the One. If it is, we don't know when. We don't know if North America is getting the 4.2 update. If it is, we don't know when. We don't know if Verizon is causing this delay. We don't know if the carriers have even received and tested the update yet.

All we know is that nobody in North America has a One that is neither black nor silver, or has received the legit 4.2 update. Also, Verizon is the only major carrier so far to not have the One.

But:

If all the rumors are true, then the Verizon exclusive One will debut at the end of the month running 4.2 on Verizon. Then the red One will debut on Sprint and maybe other carriers. The update will be sent to carriers for testing, and we will receive the update 1.5 to 2 months later. But usually rumors aren't true, so...
[Sprint HTC One (M7)] hellot1M:
In our flyer today about the new bogo for the HTC one that starts on the 16th has the red HTC one in it.. I wonder if that means the red HTC one comes out the same day the bogo starts or at least a confirmation we are getting it. I'll take a picture Monday and post it here
[Sprint HTC One (M7)] eXplicit815:
Well, no... Because if the red Sprint HTC One comes out with 4.2.2, there would be no reason why the rest of them wouldn't get it. They all contain the exact same hardware. Just because it's red doesn't change the internals. If the red HTC One ships with 4.2.2 on Sprint, you better believe the rest of Sprint's HTC Ones would have the update before it hits the first customer's doorstep.
[Sprint HTC One (M7)] eyeisdasteve:
I wouldn't take a picture. But I can confirm the Red HTC One and HTC One BOGO both launch Aug 16th.
[Sprint HTC One (M7)] sauprankul:
No picture, please. Wouldn't want you to lose your job.

And where is a BOGO when you need one? Darn!
[Sprint HTC One (M7)] raptoro07:
Another [Q] not in the the Q&A forum.
[Sprint HTC One (M7)] Kraizk:
Why would the red one launch with 4.2.2? If the update has not made it to the carrier and has not been tested by Sprint as people are alleging, there is no reason to believe they would write the system on the device at factory with anything other then 4.1.2
[Sprint HTC One (M7)] hellot1M:
It's fine. We're allowed to tell people about the promo so sharing the picture is fine
[HTC Rezound] BrahManty:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.

So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.

I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
[HTC Rezound] acejavelin:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
[HTC Rezound] BrahManty:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...

I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
[HTC Rezound] acejavelin:
Hey, wait a sec... :laugh:

My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
[HTC Rezound] BrahManty:
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
[HTC Rezound] BrahManty:
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
[HTC Rezound] acejavelin:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/

Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!

Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there... :cool:

You should then be S-ON, completely stock. You will need to unlock again to do anything more