yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Accessories] armixia:
I was looking for a case that would protect the phone well and not be too bulky like an otter box and saw these.

Cant post links yet but its just vajacases

Anyone have one for their S3? I had one for my iphone 4s and it was a great case but wanted to hear from someone's experience before pulling the trigger.

Also if you have it, what color scheme did you pick ? And which S3 do you have ( pebble blue, white ) ?
[Galaxy S III Accessories] keekah:
They look really nice but they're a bit pricey. While I'm quite sure they are quality cases (I hope), there are too many less expensive alternatives, even genuine leather, out there for me to justify spending that much.

Here is the link for those who want to check them out.

http://www.vajacases.com/Samsung-galaxy-S3-leather-cases
[Nexus 7 General] e.mote:
Some Google reps had claimed that Google would cross-ship advance replacements for RMAs from the Play Store. We would all like to find out if it's true. Those who are RMA'ing defective units from their Play Store orders, please share your findings.
[Nexus 7 General] nxt:
I called them last night, was on hold for 55 minutes, told them of my issue (dent on Nexus 7 out of the box), guy said he will need to escalate the issue, asked for my email address, and that they'd contact me within 48 hrs.

I've received an email about our conversation and currently waiting for a real response...
[Nexus 7 General] raqball:
I highly doubt Google will cross ship....
[Nexus 7 General] challa3223:
http://support.google.com/googleplay/bin/answer.py?hl=en&answer=2411741&topic=2453057

If for any reason you do not wish to keep your device, you have up to 15 days from the date the device is delivered to you to cancel your purchase and intiate a refund. Please contact our support team by phone to cancel your purchase. What to expect when you call:

Our support team will ask for the e-mail address associated with your Google Wallet account, or the IMEI/serial number for the device you're returning.

We send a Return Merchandise Authorization (RMA) and a pre-paid UPS shipping label to your email address. These will be sent in two separate emails.

Print the RMA (attached in the email) and place the form inside of the shipping box you're returning.

Print the pre-paid UPS shipping label and attach the label to the outside of the shipping box.

---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------

Rep told me this. He also said i was the first person to call about exchange and that this is a new policy.
[Nexus 7 General] e.mote:
Yes, the above is the written warranty. However some Google reps said over the phone that RMA (not cancellation or refund) would have advance replacement being cross-shipped. That's a big difference from the written clause, as it could mean 2-3 day turnaround as opposed to a couple of weeks.

I would expect, and argue for, expedited service within the 15-day grace. It's a reasonable expectation, and is what the poll is trying to find out. After 15 days is another question that the poll doesn't cover.

For those who have success in getting advance replacement, please relate your experience.
[Nexus 7 General] Swoyan:
Called in to exchange mine due to screen separation issue.

The wait was very long (about an hour) but when the person finally came on they took my info and said they'd do an advance replacement and to just ship the old one back when I get the new one.
[Nexus 7 General] challa3223:
not what the rep told me
[Nexus 7 General] kumqwat:
After receiving a DOA N7 this morning, I rang the UK google support number and chose option 2 "for help with your Nexus 7".

All I said was that my N7 wouldn't switch on, Was asked if I had plugged it in. Replied that it has been on charge for 8 hours and still nothing. And that was it.

They are emailing me a link (24-48 hours) with some terms and conditions which I have to agree to (putting a hold on my wallet registered card), then they will ship a replacement and RMA package in the same package.
[Samsung Epic 4G Touch] ccattie:
I know MTP is supposed to just work in Windows, but it doesn't do anything for me. My PC thinks I have attached a camera. I can open said camera and see only 2 folders (no names) but they are the DCIM folder and a folder called "Android" with some sub garbage folders under them. How do I get to my folders using it? I have tried it on 4 laptops and 3 desktops and everytime I get the same results. I'd prefer to use the old mass storage option, but it seems like unless you root, you're SOL.

-c
[Samsung Epic 4G Touch] rangie:
Turn off usb debugging.
[Samsung Epic 4G Touch] crkdslider:
Really? For me it's the opposite. I had the OP's issue until I turned ON USB debugging.
[Samsung Epic 4G Touch] ccattie:
Resolved - I ran a ton of windows updates and all of a sudden my system said "MTP device detected". Wonder which update it was. They were all pretty basic ones, but maybe they triggered something that repaired the service.

-c
[Galaxy S II Q&A, Help & Troubleshooting] Medo Abusabha:
Hi

I'm trying to upgrade my firmware from 2.3.5 to ICS using Samsung kies , but something went wrong during the upgrade . It always show me that Error in downloading file !!

and sometimes it says that the operation has timed out !

Plz any one can help me !!?
[Galaxy S II Q&A, Help & Troubleshooting] It_ler:
Maybe it's a bad network/internet connection.

Try to download the latest, officially released firmware for your phone in your region with Check Fus Downlaoder from here => http://fus.nanzen.se/

Select OS (Android), your phone (GT-I9100) and your region, click Check and then download it directly from Samsung servers.

You can flash it with Odin.

Have a look here for a description of how to flash the firmware to your phone => http://xdaforums.com/showthread.php?t=1075278

No need to use Kies !
[Galaxy S III Q&A, (US Carriers)] The Root:
Chainfire needs help on twitter with testers for triangle away. Check with him on Twitter. I may test for the Sprint version.
[Galaxy S III Q&A, (US Carriers)] stevessvt:
Wait, what? I thought he gave up on the US GS3's? Now he is making them for us?

And you may want to update the thread title to not look like yet another nube looking for triangle away help, this thread is hopefully different.
[Galaxy S III Q&A, (US Carriers)] teh roxxorz:
I agree; I was all ready to say its doesn't work.

And maybe he's coming around; I did testing for him for sprint to confirm mobile odin worked on sprint, after AT&T.
[Galaxy S III Q&A, (US Carriers)] The Root:
Oops, oh well. Just tested and works for Sprint.
[Galaxy S III Q&A, (US Carriers)] pinoymutt:
Looks like Chainfire mentioned that someone else confirmed works on AT&T as well. Good news indeed.
[Galaxy S III Q&A, (US Carriers)] fireboypr:
I have Tmobile version and counter at 1. Can I test it? or test is only for counter= 0?
[Galaxy S III Q&A, (US Carriers)] The_Biz:
Ask him if you can test -> ChainfireXDA
[Galaxy S III Q&A, (US Carriers)] fireboypr:
I don't have twitter :S not facebook not g+ nothing... I think I will have to create an account
[Galaxy S III Q&A, (US Carriers)] moonfire711:
This would be the bomb. Thanks a million chainfire!!!
[Galaxy S III Q&A, (US Carriers)] zonly1:
I'm all over this like white on rice! I'll test! Hit cha up on Twitter!
[Galaxy S III Q&A, (US Carriers)] sekigah84:
Messaged him already on XDA and on Twitter lol.
[Galaxy S III Q&A, (US Carriers)] laylovj:
http://xdaforums.com/showthread.php?t=1494114

I'm not risking until I see enough good results. :p
[Galaxy S III Q&A, (US Carriers)] appdroid:
I tested it & works on At&t ! Really awesome work Chainfire.
[Galaxy S III Q&A, (US Carriers)] moonfire711:
Any love for tmo yet?
[Galaxy S III Q&A, (US Carriers)] The_Biz:
It says it works on all US variants now. :good:
[Galaxy S III Q&A, (US Carriers)] sekigah84:
Tested it on my Sprint GS3. Worked like a charm. I did it on CM10 but users on stock ROMs are reporting it works as well!

My counter was at 2. It is at 0.
[Galaxy S III Q&A, (US Carriers)] laylovj:
That's what it says. As far as I'm concerned, it hasn't been tested yet on Tmobile...at least with a counter >0 :(
[Galaxy S III Q&A, (US Carriers)] fireboypr:
This is what I don't understand. Will this reset the counter to 0 on Tmo or not?
[Galaxy S III Q&A, (US Carriers)] The_Biz:
Try it and see? :p
[Galaxy S III Q&A, (US Carriers)] fireboypr:
I'm scared... Literally
[HTC Wildfire S] rajanand:
Hi Friends

Now You can see your Black Screen Recovery!!

NO More tension of flashing Rom's With Black Screen Recovery.

But again a bad News This is only visual with PC Not in phone :( .

Days are gone with BLACK SCREEN RECOVERY

Here how it works!!

You need some files.

1.Download Adb Files form here

2.Download This Droid@screen Tool,Thanks To RiboComments

3.Extract Adb "c:\ " on your pc Creating Folder Adb.

4.Copy Droid@Screen From your Downloaded folder to desktop.

5.Double click on Droid@Screen ,and locate the adb.exe form c:\ when asked.

6.Connect you phone using "Charge only mode" with usb debug on.

7.Follow The UI of Droid@Screen and when will you get your phone screen appearing.

8.Now restart your phone in Recovery mode.

And enjoy The Pleasure Of CWM.

REMEMBER: PLEASE DISABLE ANY FIREWALL (If Getting connecting error) IN YOUR PC AND INSTALL THE LATEST JAVA SDK TO MAKE WORKING THIS SOFTWARE.

Sometime if not working in CWM .

Do the following Troubleshoot .

1. Disconnect your phone.

2. Close Droid@Screen And

3. Delete all Files In temp Directory Of your PC. (Type " %temp% " Under search box of Start Menu or Under Run Command window) to navigate to Tempdirectory Directly .

4. Now connect Your phone With CWM recovery screen and START Droid@screen.

5.Click on Restart ADB . (More than once if needed)

This Tool Is Not Mine.

Original Thanks Goes to creator of this Tool RiboComments For his Great Work.
[HTC Wildfire S] BigChillin:
Ugh. Get out spammers. We have no such problem.

Also, could someone report this. My tapatalk won't.

Sent from my Marvelc
[HTC Wildfire S] Anto2:
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.

And rajanand is the only one that provides a solution.

I'll try the solution of rajanand and I will post the results

Greetings.

Sorry for my bad English.
[HTC Wildfire S] marchelius:
Works great ! Thanks again.
[HTC Wildfire S] Anto2:
Works great ! You're the BOSS.:good::good:

Thanks a lot.
[HTC Wildfire S] koowal:
Aww yeah! Great job sir!
[HTC Wildfire S] rajanand:
little knowledge it always dangerous to health, so tk care of ur health.

:p

Thanks aunto for commenting on my useful post.
[HTC Wildfire S] BigChillin:
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.

Sent from my Marvelc
[HTC Wildfire S] matt5eo:
Do not download! Maybe a VIRUS!

Never heard something about this iusses.

Why should I disable my FIREWALL?

Sounds like a virus.
[HTC Wildfire S] rajanand:
sometimes it disconnects itself due to continuous Data transfer in between adb and phone......so

To avoid interruption between ADB and Your phone.

i personally recommend it, rest is on your side.
[HTC Wildfire S] rajanand:
Go to market and purchase brand new Lot of WFS,you will surely find black screen problem in that.

Please Stop Arguing..further ,i am not here to entertain such comments.
[HTC Wildfire S] ngoralph:
rajanand: This works great!! thanks

To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
[HTC Wildfire S] marchelius:
You are not the one with this problem :) I have blank CWM Recovery too.

Rajanand helped me many times.
[HTC Wildfire S] rajanand:
Thanks for your support.
[HTC Wildfire S] rajanand:
Thanks dear for support , hope you all be with me always .

:)
[HTC Wildfire S] marchelius:
Of course I will :)

But, I have now another problem to solve: please look : http://xdaforums.com/showthread.php?t=1785689

I have blank screen with older versions of CM 7 !!!
[HTC Wildfire S] rajanand:
try these steps and try to replace boot.img

(by copying boot.img file only inside the folder),from any other working roms

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

older version of boot.img incompatible with black screen devices.
[HTC Wildfire S] insink71:
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:

1. Why the blackscreen occurred

2. Fix it

3. Take preventative measures so that it would not occur again.

But that's just me. I wouldn't build a tool to propigate my device's bad behavior.

Rob
[HTC Wildfire S] KelvinWild:
Not working, same sh*it :(
[HTC Wildfire S] rajanand:
its fully upon users ,weather they are using it on firewall on or off.(it will work on both the conditions if the "adb" have the access to the port)

its just a recommendation from my side. :rolleyes: That's it

Its fully safe from my end and free from any type of virus.

as i have already said this tool is not mine.Please consult the owner of this tool linked on first page of this Thread For future reference.

i don't know why this "black screen recovery" Problem is there with all the newly manufactured WFS.

Why occurred?

1. I am rooting and reflashing CWM on old wfs without any problem.(even rooted for the first time)

2. the same above is not working with any newly manufactured devices.(all working well but With a black CWM recovery)

3. My doubts are pointing, its a fault of hardware,or any kind of display adapters Upgradation from HTC Side.(May be HTC is planning to give supports like ICS etc for future)

4.Also Some rooting errors can be the catch,(Again if HTC upgraded something)

4.CWM is fully working without any error.(Blindly)

5.only the four keys are lighting up,

6.This tool is The only option in that case to flash any custom ROMS.
[HTC Wildfire S] rajanand:
Have you tried "m1ndh4x8r_ROM"

if not give it a try click here to download
[HTC Wildfire S] insink71:
Does your hboot also give black screen?

If not, take lock key you got from HTC.. relock.. then flash RUU.

That should get it back to original state. Then, upon upgrading again (should you choose not to disable the updrade(s)), don't do the same root method [as you know that method is causing you grief]. Mind if I ask which rooting method is causing grief? When manually applying, I've not experienced an issue with Heritz guide/method.. and there is always the kitchen as well you can use to root rom(s).. I would try the step back, step forward do-see-do.. and I've been able to do such by relocking then flashing RUU [even with s-on device].. but I have heard some have trouble with migrating backwards.

Regards,

Rob
[HTC Wildfire S] kagevazquez:
Rob I think HTC made a new batch of phones with a different screen or screen drivers kinda like what happened on my old OV it used to make the screen black when it entered recovery but everything still worked the same
[HTC Wildfire S] rajanand:
Hboot is working properly,

Ihave already tried locking and return to my old original factory rom and tried all rooting tools,

(I have rooted and reflashed old ones also with no error with the same tools)

I support you kagevazquez .

.................................

upto some extent rob is also right but

Conclusion is that ,if going with ROB's Idea ,again a question arises,

"WHY THIS IS VISUAL IN PC?"

And not in WFS Screen?

any idea?
[HTC Wildfire S] ngoralph:
i think your idea is the only possible answer since it works on pc :)
[HTC Wildfire S] rajanand:
Until new Custom recovery...

How to get rid of this?? :confused::confused::confused::confused::rolleyes:
[HTC Wildfire S] ngoralph:
anyone tried cwm v6 already??
[HTC Wildfire S] marchelius:
Not work on my WFS - stuck on white screen with green HTC logo
[HTC Wildfire S] WoefulDerelict:
So, if I understand this properly...

Users with newly purchased HTC devices bearing the Wildfire S name for the European GSM market are having display issues when injecting any custom recovery? I'm also to understand you have no such issues with the stock recovery?

I've had two users complain in my threads regarding TWRP complaining about issues with "Black Screen Recovery" devices: marchelius (1, 2) and sorinaugusto (1)

As none of them complain about these issues with ROMs those packages also support their hardware properly. I would say this is a legitimate issue involving some discrepancy with the recovery software and their hardware. I have yet to see a enough log data from one of these users to determine anything about the issue. I know the one user reported in with an ro.carrier of HTC-EastEurope where as my device chimes back with ALL. Reports back with the same baseband, bootloader and revision number as my device tho. I'd be curious to know if the users can boot an eng build of a ROM. I'd really appreciate some deeper log data that could show me if there were any display errors as there should be some squawk somewhere if something is failing to that degree.
[HTC Wildfire S] insink71:
I also have gotten pm regarding black screen.. but like you have yet to peep any logcat data.

I will say this. Some versions of cwm (on some devices) do turn screen off when power button is pressed; however, it is supposed to reappear when power button is pressed again.. Surely we wouldn't have that simple a solution.. heh.

I do concur though; to get a dev (or even hobbyist's help) we need some logcat data.

PS I could also see the possibility of swapping out to newer 7x27a chip on newly shipped devices. Since cwm does carry a mini device tree, this could present challenge. The newer chip (if shipped with newly released wfs) is neon (or adv simd) compatible; This would make some wfs truly ics capable as they could get openmax il codecs (7x27a) and some not (7x27).. which would piss a lot of users off. Although the new chip costs little more and is same size and almost same clock...

I wonder if this has been done. If so, get ready for a recall petition ;)
[HTC Wildfire S] WoefulDerelict:
Well...

Most recovery software doesn't logcat but, you can still pull the kernel dmesg with adb shell dmesg > dmesg.txt and upload the result. That included with the recovery.log from /tmp/recovery.log should at least provide some help.
[HTC Wildfire S] WoefulDerelict:
Tasty logs and other info...

sorinaugusto posted some tasty log files in this thread which is already dedicated to determining what has changed in the recent hardware revision. It seems the problem extends to all community kernels and not just those included with recovery images. I'm curious to know which kernels the users are substituting that work for them.
[HTC Wildfire S] rajanand:
Sorry friends!!

But its already Proved That CWM is Fully Capable and Workingon WFS,So problem is in WFS Screen(LCD) that HTC Have upgraded,(it can be in any means software or Hardware)

So Try to concentrate on The right way dont look for any tasty stuffs and please dont deviate the topic to other endless way.
[HTC Wildfire S] WoefulDerelict:
Pretty sure looking at kennel messages from affected devices and searching for errors is the best way to determine what is causing the issue. From the logs I can already see complaints about looking for hardware that doesn't exist. The problem my dear users may be due to a hardware change but, nothing in Linux works if the kernel can't talk to it and we need to know which kernel versions DO support the new hardware in order to help narrow the search. I have done what I can to move this discussion away from your thread but, if you would like to see an actual resolution to this problem it's best to let developers with more of a clue decide what is and isn't relevant and true without standing in our way.
[HTC Wildfire S] rajanand:
yeah!

this could be great if dev's Rush to find some solid reasons.

but my senses are saying it is hardware fault (which is residing in the LCD of the device)

Hope for best!!!!
[HTC Wildfire S] aminclick68:
black screen on new custom rom

Hi guys

after installing new custom and reboot device now i have black screen on the new custom rom too

plz help
[HTC Wildfire S] aryan41:
hey, there is a new post in the general section about the recovery screen visual. i dint try but hope it will work out. check it out for those who want their recovery screen back no matter what..!

here is the link : http://xdaforums.com/showthread.php?t=1827541
[HTC Wildfire S] ngoralph:
been gone for a while any update regarding the problem??
[HTC Wildfire S] cyberkhan:
Perfectly working.

Thanks :)

Just a tip, while the "recovery" is visible on PC, highlight menu by using phone's volume buttons and INSTEAD of POWER button USE SEARCH (led) to select.
[HTC Wildfire S] ngoralph:
what rom are you using now in wfs??
[HTC Wildfire S] Keioboy:
Rajanand you're the BEST!!! Worked like a charm!!!!!!!:victory:
[HTC Wildfire S] linkin_p:
big thank to you this is working like acharm now
[HTC Wildfire S] amirsaishi:
after searching five days, your method finally worked :)

thanx alot for sharing it..
[HTC Wildfire S] jackorsen88:
i have a feeling that only users using wfs purchased in europe are having problem with black screen...maybe i'm wrong...
[HTC Wildfire S] Yogeehemp:
Oh My God!!!

Thanks a lot!!! I spend many hours working in my Wildfire and you....I love you!!
[HTC Wildfire S] rajanand:
M back now!!

NOT YET...I was lill bit busy with my Painful life...

now i am fully out of it.....

so i hv lots of time for updates..... :)
[HTC Wildfire S] M4rt1n94:
Also worked for me but ...

... this is just a temporary solution, because dont want to put my Handy on my Laptop everytime I want to flash something ..

does anybody got a working Touch-CWM-Recovery / CWM-Recovery?

Thanks in advance ;)
[HTC Wildfire S] nitin95:
Worked like a charm, thanks man!
[HTC Wildfire S] colinmc8:
I've been having trouble with recovery too. downloaded the progams you suggest but all the step involve installing toolbars and crap???? What the hell is this?
[Android Software/Hacking General [Developers Only]] prasad12ka4:
Is there any apk or app for FM radio on CM 7.2?

I dont want to try Spirit FM as it screwed my system last time.

Any built in apk from previous versions?
[Nexus 7 Q&A, Help & Troubleshooting] Praesidium:
With my settings set to Automatically lock (immediately after sleep) and power button instantly locks with a visible patter screen lock, my Nexus 7 on wake-up [pushing the power button immediately] either right after an invalid pattern code (where device then sleeps) or waiting a few seconds with no activity until the device sleeps (where the Nexus 7 fades to a black screen) will have a delay in bringing up the lock screen OR sort of flicker presenting some sort of black and white bar lines background at the bottom half of the screen for a split second before bringing up the lock screen. In essence, when waking the phone from sleep, the screen "glitches" for like a fraction of a second where the "glitch" is a set of white lines that flash on the screen before the lock screen appears on the display. This "rarely" occurs and has to be done fairly quickly, but I have seen it a few times as I continuously tried it over and over again; you can blame my OCD :P Anyway... I was wondering if this is normal or it is in fact a defect? It doesn't seem to affect the performance of the device itself.

The following are video recordings of the "issue":

http: //youtu.be/lFhr0DxhA_Q

http: //youtu.be/yTmrWgBoAjQ

Does this happen for anyone else?

Thanks in advance!
[Nexus 7 Q&A, Help & Troubleshooting] Praesidium:
*Bump*