yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] StevePritchard:
As an update, I've found that the "fix" of cleaning the keyboard would only last a week or so. I've also found that trying to get behind the keys with fluid is a waste of time (the keys are simply stuck on to a membrane). This means that either the fluid is a red herring, or perhaps the fluid needs to go behind the membrane down the outside edge of the keyboard. Maybe it's the rubbing that improved things?

There's defintely an improvement after the physical act of cleaning, but I still wonder whether there's a software debounce fix that could be more effective.

Cheers,

Steve
[Motorola Droid 3] StevePritchard:
Hardware Keys skipping/doubling fix

A bit more info for anybody that's interested...

I've found that CAREFULLY lifting the edge of the keyboard (in the corners next to the ALT and right cursor keys) with a toothpick, and then spraying the switch cleaner into the exposed area under the edge, and then rubbing the keyboard seems to be a much more effective way of getting a longer lasting, and more comprehensive fix. I think lifting the edge of the keyboard actually exposes the microswitches under the membrane, and so it's those that are being targeted when we spray the cleaner in there.

The edges of the keyboard go back down no problem, so there's no visible indication that they've ever been lifted. Obviously, quite a bit of care has to be taken not to over do it - I suspect that permanent damage could occur if too much force is used, or if they are lifted too high.

The difference between the keyboard before/after the cleaning is like night and day, and I'm now enjoying my phone again. Please be aware that I can't be held responsible for any damage caused if you do choose to undertake this fix.

Cheers,

Steve.
[Motorola Droid 3] s1ice:
thanks!

You are my hero <3
[Motorola Droid 3] MrObvious:
Can you take a video to demonstrate?
[Motorola Droid 3] StevePritchard:
That's a bit tricky - the only thing I've really got to take video with is the phone itself, plus I can't really show a "before" and "after" as all the keys are working fine.

If it needs re-doing again, then I'll try and borrow a camera or something and take a video.

Cheers,

Steve.
[Motorola Droid 3] 5318008:
I think this is a pretty well-documented issue on the D3. Mine has this problem and is nearly unusable, but I plan on just replacing the entire keyboard. You can buy them on eBay for 7 to 10 dollars.

http://www.ebay.com/itm/New-Keyboar...ultDomain_0&hash=item2321e0bb2d#ht_3615wt_952
[Motorola Droid 3] 5318008:
I've got a question for any Droid 3 owners who have/had the bad keyboard issue. Anyone try a warranty return for a fix? If so, what happened? Got curious and checked online, and mine's still under warranty, so I was thinking of sending it in.
[Motorola Droid 3] niko99:
I fixed my problem with terrible keyboard, i disassembled the phone keypad unglued and glued back (because keyboard is like sticker )

now working as a new one :laugh: ( earlier i stop using hard keyboar because keys A, I, O and backspace dont work, only if i press very hard)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Hey guys,

First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.

My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.

I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.

Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
Were you on stock ICS when you did the wipe ?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Yes, downloaded via Kies.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing devices running their stock ICS. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.

When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Yeah, I feared that was the case. The problem is, I now have the yellow warning triangle on bootup, and my "binary count" has increased to 9. Does this mean Samsung won't replace it?

if that's the case, is there any way to reset the binary count and remove the triangle in its current state?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Dungeon47:
You might try resetting the counter with a jig. I don't know if it will work in its state, but you may not have much to lose.

Sent from a guy on a buffalOOooo.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
Generally - USB Jig is the only way to reset it on a bricked device.

There is one way other way though:

http://www.mediafire.com/?5bmrc6cf81w5mya

This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.

You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".

Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung. It will work only on ICS devices.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Thanks very much for your help. I really appreciate it.

So do you think it's worth contacting Samsung first - before trying to reset the binary - or do you think they'll refuse to replace it once they know I tried flashing an unsupported ROM?

Thanks again!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
I think you might try contacting them first, just ask all the info you need without giving them the serial numbers - before you send the phone in. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip. Although i'm afraid they might find out and refuse to fix it for free.

If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.

Just say that Kies messed up your phone - they'll know what the problem is :)

Hope they'll get it fixed for you. Let us know how it went.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Okay, I'll do that. Thanks again for all the info! I'll let you know how I get on.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] forest1971:
You may also try manual/adb repartition method described in here to revise your phone. cheers.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] JB calhoun:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Thanks!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Stock recovery? Where would I find that?

The problem is, I cannot flash any ROM. It just hangs during the "factoryfs" process in Odin. When I try to install stuff via ClockworkMod recovery, it fails. Sometimes I get an error like "cannot mount (or access) /system."
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
Not true I'm afraid...

If you've damaged the eMMC chip:

- You can still get into recovery.

- You can still get into download mode.

If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".

It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there. I seriosusly don't know how could Samsung not see that the format command introduced in ICS ( it was not present in GB, that's why GB kernels are safe ) damages the chip... didn't they test the software at all ?

Take a look here:

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

This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.

Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:

http://xdaforums.com/showpost.php?p=26285877&postcount=12

It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).

Keeping my fingers crossed.

Thanks for all the advice, guys.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
JIG is probably the best thing to do. Clear the counter, get rid of triangle and send it in. As you said - it's Samsung's kernel that causes this, and they know it.

Good luck mate.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.

So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.

Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy? :o
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] praetorius:
Stay with what you have.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ekreed:
How much capacity do you have on your internal storage? If it is less than 11GB you may have a damaged chip and just managed to unbrick it.

I think if you can flash GB with Odin you should be fine, and once you get to GB everything is (relatively) safe.

I had a similar problem when I was trying to flash GB from stock ICS using odin, it stuck at FactoryFS and I thought I had superbricked it, but it turns out I was using a dodgy USB cable and using a good USB cable I managed to flash GB again and recover it, and now I am using CM9 - Never going back to stock ICS after this.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Yeah, it appears I only have 8GB of internal storage now. But that's not so much of an issue with a 32GB SD card.

I'm very tempted to give it another shot. I've heard good things about CM9, and I'd love to get rid of Samsung's awful TouchWiz UI.

I'll see if I can pluck up the courage to give it another shot tonight. :)

So you're saying it's best to root, then attempt to downgrade to GB using Odin, then install CM9 from there?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
If you decide to give it another try, follow these steps:

1. Downgrade to GB via Odin. Choose one of directly-rootable firmware's from dr. Ketan's guide and flash it. You might need to go into recovery and do a wipe because you were on ICS and stock GB often gives bootloops after downgrade.

Here are the firmwares:

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

2. Use Zergrush to root and install CWM - also a guide by dr. Ketan, 1 click operation.

Here's the Zergrush root+cwm script:

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

3. Flash CM9 via CWM, clear cache and dalvik.

4. Reboot

Shold work fine. And yes, CM9 is definitely worth a try. Actually i can't imagine Note without AOSP-based Android like CM9 because TouchWiz is just terrible and it should be illegal ( joking, i just really dislike it )
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
Since you got the faulty eMMC chip and you managed to reset the counter. I would suggest that you get back onto the stock GB rom (to remove traces of rooting and customs ROMs/kernels)... "soft brick" it again and take it to Samsung for warranty repairs. Youll get either the M/B or the phone replaced and the lost real estate back.

No need to call them and ask them. As long as there is no yellow triangle and the binary count is zero, they will honor the warranty. I myself got the M/B replaced twice and then sold off the "repaired" Note ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] lee yun khong:
Agreed, your deal is really good. For those who successfully revived their hardbrick note with repartitioning method, just reset the binary count by using triangle away ( download from google play or xda) and hardbrick again, then send to samsung for new mobo replacement ( if still under warranty).
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Sorry to sound like a noob, but why should I flash back to GB? The error happened under ICS, so shouldn't I try to recreate it under ICS?

I do like the idea of getting that storage back, especially since this is a common issue that Samsung is aware of. The only reason I said I'd call them is because I live in the U.K., and I have no idea where my nearest Samsung service center (or whatever they're called!) is.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
Thanks very much for this, it's really helpful. I'll definitely be attempting this over the weekend.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kill.i.an:
So I followed your steps one-by-one and I managed to install CM9 flawlessly on my Note. It's up and running without any hiccups, and the whole process couldn't have been easier thanks to your tips.

Once again, thanks very much! I owe you one! ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
Get back to GB to get it into the stock ROM without any traces of root or custom. And you can tell the service center guys that while trying to ugrade to ICS, your phone rebooted and shows this screen since.

You got it working again :thumbup: so no need to get into the bricking scene again now. :)
[Sprint Samsung Galaxy S III] hotstocks:
If anyone can help, I can't believe I can't figure this out.

On my old HTC Evo, when replying to a text message, you can

press the microphone button and speak to text then send it.

On my new GSIII, the keyboard has a setting option to see the

microphone speak icon on the keyboard. I have it checked and

I can NOT see the microphone icon or input button using voice?

Is this a rom problem that needs update, or am I missing something

here? How do I get the mic button to show on texting to use voice?

Thanks, and I am rooted but stock rom/kernel. Rom manager also

does not work for me, says I need to install clockwork recovery,

but when I rooted it, it did. Also Rom manager doesn't have GSIII

in its list yet.
[Sprint Samsung Galaxy S III] ghostzyden:
Belongs in Q&A.
[Sprint Samsung Galaxy S III] clark44:
Doesnt belong in this section bud. Anyways the option isent available in texting i beileve. Just download a custom keyboard from the market. I recommend Swift Key:)
[Sprint Samsung Galaxy S III] Darkshneider:
I have the mic icon on my keyboard and it works... long press the "gear" button and then select the mic one.
[Sprint Samsung Galaxy S III] ghostzyden:
Wrong thread lol
[Sprint Samsung Galaxy S III] hotstocks:
Sorry about the wrong forum.

But thanks a million, I was just pressing the gear.

I've had android for a year and never knew you

can LONG press the gear and get more options,

the mic shows up now!
[Sprint Samsung Galaxy S III] Darkshneider:
No problem. Usually buttons that have, the 3 little dots on them, have different settings or do different actions.
[Sprint Samsung Galaxy S III] 816jared:
I know this is an old thread, but I seem to be having the same issue...

EXCEPT, when I long press the gear I do not have the microphone as an option. the voice input option is checked in settings, any suggestions?

I'm on FreeGS3 v0.2.0 if that makes any difference
[Sprint Samsung Galaxy S III] Dalmus:
I had the same problem with voice-to-text with the stock keyboard and the stock Swype... The icon was there, but it would error out. I installed the latest Swype Beta and its working again.

I'm running FreeGS, too.
[T-Mobile Samsung Galaxy S II SGH-T989] JPOKeefe:
I went on the CM website and our phone isn't on the device list. I was wondering because any phone with official CM9 will most likely get CM10 which is based on jelly bean.
[T-Mobile Samsung Galaxy S II SGH-T989] snguyen0730:
It is. Look under goo / cm / hercules

Sent from Samsung Galaxy SIV
[T-Mobile Samsung Galaxy S II SGH-T989] VoiD_Dweller:
I'd say this would mean it is supported.

http://download.cyanogenmod.com/?device=hercules&type=nightly
[T-Mobile Samsung Galaxy S II SGH-T989] JPOKeefe:
Thanks guys
[T-Mobile Samsung Galaxy S II SGH-T989] turphed:
yeah somewhat.. I mean it's nightly but it runs beautifully for me.. you should try it :)
[HTC Rezound] jumpoff609:
I was using newts one xxx but Im looking for a non sense 4.0 Rom with Polaris office. Any ideas?
[HTC Rezound] Superm@π:
Download any rom and just download the Polaris office apk online or extract it from the rom.
[HTC Rezound] jumpoff609:
I already tried that, it kept force closing. I tried on slimrom and clean Rom standard
[HTC Rezound] Superm@π:
I don't know why that is. I'm running slim rom with Polaris
[HTC Rezound] jumpoff609:
Really? that's the Rom I want to use. Did you extract from a Rom or find a download online
[HTC Rezound] NilsP:
Just push the apk to system/app with adb
[HTC Rezound] jumpoff609:
I got the apk to system app but for some reason I'm still getting force closes. Currently on slim rom
[HTC Rezound] fo0you:
you also fixed perms and rebooted?
[HTC Rezound] jumpoff609:
I only restarted I don't know what permissions to toggle
[HTC Rezound] AshtonTS:
Rw-r-r
[HTC Rezound] jumpoff609:
OK so I just did that and still getting force closes. I guess I'll just go back to newts rom. I'm pretty disappointed I really like this slim rom with the red theme
[HTC Rezound] funnyangrykid:
try this rom. http://xdaforums.com/showthread.php?t=1630696 after i flashed it, i noticed it had the app while browsing through the app drawer

Note: Download is in Post 2

ScreenShot:
[HTC Rezound] Superm@π:
Yeah but its not his rom because I have Polaris installed on slim rom.
[HTC Rezound] topgun1953:
I wonder if you backed up Polaris with Titanium Backup within Newts, flashed Slim Rom and then restored it it that would work?:confused:
[Desire HD Q&A, Help & Troubleshooting] Chovky:
On my HTC HD I have a custom ROM and ROOT. I wanted unroot. Im flash RUU original ROM (.zip) but Im flash US and I have europe device. Im flash US rom occurred error - reboot phone. Now, my device I turn after several times the switching on and remove the batteries. I don´t can get in bootloader!!! Install RUU ROM (.exe) my computer write error. Please help I want Unroot and original ROM.

Sorry for my bad English Im from Slovakia.
[Desire HD Q&A, Help & Troubleshooting] IonXda:
I recommend you to use the aahk to revert to stock. Put the stock to germany because at that ruu the ota update works . It's with sense 3.0 and android 2.3.5:good:
[Desire HD Q&A, Help & Troubleshooting] Chovky:
Original ROM error

Please manual or video. Thank you very much.
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Chovky, if your phone is not booting and u don't have at least fastboot, you won't be able to flash a RUU...the question is, is not booting at all or is very slow and u are stuck in the splash screen?
[Desire HD Q&A, Help & Troubleshooting] Chovky:
Original ROM error

Phone can be turned on, but cannot go to Bootloader. I tried to install .exe RUU (WWE)through PC but write error (exe RUU from the site -shipped-roms).

error 155: Update menory error
[Desire HD Q&A, Help & Troubleshooting] Chovky:
Original ROM error

Please AAHK write: Imput PASS KEY and press ENTER

What is pass please ???
[Desire HD Q&A, Help & Troubleshooting] Muikkuman:
You find the passcode in the effen manual :thumbup:

And it generates a new passcode every time you start it.
[Desire HD Q&A, Help & Troubleshooting] Chovky:
AAHK wants to restart the phone, but phone can not reboot
[Desire HD Q&A, Help & Troubleshooting] Muikkuman:
Why can't your phone reboot?
[Desire HD Q&A, Help & Troubleshooting] Chovky:
Don't turn on
[Desire HD Q&A, Help & Troubleshooting] Muikkuman:
If you cant turn on the phone then try to connect your charger before trying to start. And if it doesn't start then I'm afraid you bricked and need to send in the phone to HTC or buy a riff tag box (don't know if the spelling is right).
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Chovky, all what u are describing is in the effen manual. Take some time to read for comprehension. If you keep trying things you might mess the phone to no turning back issue.

If your phone boots to a black screen, then just fix your pc and re run the Kit from that screen. That is in the Manual....:good:
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
Nexus 7 not going into recovery. It just hangs at the Google screen
[Nexus 7 Q&A, Help & Troubleshooting] knightnz:
More information required.
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
I think i've really screwed up this nexus whole system. It is bricked.I can get into CWM recovery if i flash it. I cannot get it to stay though. On boot it just hangs at the google icon with the unlocked bootloader on the bottom. I'm a novice when it come to fastbooting and ADB. I'm still learning. I've downloaded the image file from google but it is in a .tar form. I'm not running linux and i suck at linux. This device just needs to be rebuilt from the ground up software wise.
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
Oh by the way I forgot to mention that i've been fllashing files for the last 2 hours. Don't really know if they are the right one either.:p
[Nexus 7 Q&A, Help & Troubleshooting] DarkRyoushii:
send it to me and ill fix it right up but can't guarantee ill send it back >.<

In all seriousness though, you should be extracting that stock image with a windows program like 7zip and then fastboot flashing the .img files. That's how I'd do it at least, there are probably other easier ways if you run linux or OSX.
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
Even if it's a .tgz file from Google
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
I think i got it
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
YAAAAAAAAAY I GOT IT. Jumping up and down like a little girl who just got a pony. I had to redownload the Nexus file from Google. First file was corrupt. Thank all of you for your help. I understant fastbooting a little better now. Live and learn.
[Nexus 7 Q&A, Help & Troubleshooting] albundy2010:
You're more than a novice at fastboot / adb. Novice at computers and common sense period.