yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] Vinnvin:
Go to Settings, Accessibility, Is there anything other than ''TalkBack''?
[Galaxy S III Q&A, Help & Troubleshooting] dheeraj (dhlalit11):
Yes
[Galaxy S III Q&A, Help & Troubleshooting] dheeraj (dhlalit11):
Thank you man

I was really light flow after disabling it's service I am no more hearing any useless sound

And light flow is also working properly without turning on accessibility
[MDA III, XDA III, PDA2k, 9090 General] yadvani:
Hey guys..I've searched and searched and still cant get to work the bluetooth

Rom Version: 1.31.00 WWE

Radio Version: 1.10.00

ExtROM Version: 1.31.112 WWE

Applied BT Patch 3900 and BA_OEM_AudioGW.cab

But still when i get a call when pda2k is suspended my headset rings after 3 or 4 rings..

Can anyone help me fix this

Thanks
[Sony Xperia S, Acro S, Ion] 424aca:
Device: ATT Xperia Ion (locked bootloader)

Running: [Rom]Xperia GP v2.1[4.1 JB] [LBL-UBL]

2 Issues:

First one is not related to software and the second one might be though

1) Sometimes when I dont use my phone for a while (dunno how long) and then i turn on my 4g to check some stuff, when someone calls after (SOMETIMES), it makes this very odd screeching noise or like these random sounds in which i cant hear a word of what the caller is trying to say HOWEVER they can perfectly hear me.

Temporary Fix: I just reboot but thats a slight time consuming fix especially if the call is urgent

2) I experience this today. When i was called (7 attempts) there was no sound coming out of earpiece AND this time the caller could not hear me either D:.

Temporary fix: Reboot

Problem 1: also happened while running stock ICS

Problem 2: happened today first time running the [Rom]Xperia GP v2.1[4.1 JB] [LBL-UBL]
[Sony Xperia S, Acro S, Ion] Envious_Data:
there is

there is only 1 thing you can try that may fix your XS

download a Stock FTF and Flash a stock rom, (do this at your own will and if done ensure to folow instructions and requirements)

but if that doesent fix your XS then it is a hardware problem and you will have to send your XS for repairs unless you can bare with your issues
[Sony Xperia S, Acro S, Ion] 424aca:
oh so it is a hardware error :/ i was hoping that it wasnt hahah thanks though :D

and lol xD i have an ion not XS but i guess same rules apply
[Sony Xperia S, Acro S, Ion] Spectre51:
It's not a hardware issue. It's an issue with using a ROM that is probably based on one of the international firmwares. Search the ion threads for garbled audio and you will see it is a known issue when using a LT28i or LT28h firmware or based ROM on the LT28at. We haven't figured out what causes it yet or how to fix it other than reboot it run at&t firmware.

Sent from my Sony Xperia™ Z
[One (M7) Q&A, Help & Troubleshooting] jastut:
When I go to charge my phone, (just started doing this) it completely spazzes out. It wakes up and starts opening random apps, especially Google apps. Then it just sits on a screen awake and does not fall asleep. If I put it to sleep, on the 3rd time, it'll stop charging. What's happening?? Any help? Thanks
[One (M7) Q&A, Help & Troubleshooting] BenPope:
Perhaps there is some kind of short between charging circuit and the digitiser power supply. Warranty time.
[One (M7) Q&A, Help & Troubleshooting] Ciobrelis:
I had something like this on my S2, so i had to clean that micro-usb port, and it was pretty simple...just had to blow to it. Since that all those things stoped.
[One (M7) Q&A, Help & Troubleshooting] jastut:
tried it

I tried to blow air into the charging port, it didn't work unfortunately. And also when it's plugged in, the screen stays sideways
[Verizon Samsung Galaxy S III] fiodorpugach:
Hello,

Is anybody know any custom ROM for Verizon Galaxy S3 with the full support of Samsung Smart Dock (the dock with charging, HDMI, sound and 3-ports USB HUB)?

That dock is not officially supported with Verizon GS3, only with Note2 and GS4, but charging, sound and HDMI worked fine up to VRBMB1 SW release; USB hub did not work, but every USB port worked as a pass-through.

The latest Verizon OTA VRBMF1 with multi-window and bug fixes killed HDMI with the Smart Dock, it just stopped working!

I spent some time for testing, I flashed back to VRBMB1 with factory reset, HDMI worked fine. I accepted OTA for VRBMF1 - HDMI does not work again. I had to go back to VRBMB1 without multi-window, I need HDMI!

Now I'm looking for some custom ROM with the full Smart Dock support. Any information will be appreciated. Thank you.
[HTC Pico (Explorer)] cyborgmanu:
Hey there everyone !

This is my first release so please go easy on me (Also Hit the Thanks Button please) ! :fingers-crossed:

Introducing MODs that will make any Sense 3.5 Based ROM look like Stock ROM.

I release this as I've seen many posts in various threads asking for Stock MODs which are flashable.

So if you like the Stock look, then please flash my MOD, I've tried and tested them myself ! :D

For Stock Looks:

(With Stock Battery Icon, Recent apps in Status Bar, No Green or Blue Scrolling Glow ! )

Older Version:

Flash this : https://www.dropbox.com/s/cpxp791ra0nha8z/Stock MOD.zip

New Version: https://www.dropbox.com/s/yr3ku5rr0urvnew/New STOCK.zip

(Fixed extra quick settings like Power Saver in status bar, fixed apps that would remain un-themed)

For those who want the Absolutely Pure and Stock Status Bar without any Extra Quick Settings (Check Screenshots) and also want t get rid of Swipe to Remove Notifications:

Flash this file : https://www.dropbox.com/s/mznh2z2jxuqm0eq/Pure Stock Status Bar.zip

If you want NextGen Battery Icon Only:

Flash this : https://www.dropbox.com/s/xsvthhrebmgzeqf/NextGen Battery MOD.zip

If you want Stock keyboard only :

Flash This : https://www.dropbox.com/s/3j23imz4j981e7v/Stock Keyboard MOD.zip

If you want to remove screen On / Off Animation.

Flash this : http://www.mediafire.com/download/badah5r5i743c8c/To+Remove+CRT.zip

If you want to add screen On / Off Animation.

Flash this : http://www.mediafire.com/download/mbq7fq9pao9d58m/To+get+CRT.zip

That's all I suppose !

Don't forget to HIT the Thanks Button.:p

Thank You ! :victory:
[HTC Pico (Explorer)] gauravrai:
Hmmmm highly customized package. Appreciate ur work:thumbup:
[HTC Pico (Explorer)] pettumuyal:
Can u reupload the files? Link is broken :crying:
[Samsung Galaxy Mini] clubkids:
Hello Everyone Good day;

I have problem first when i upgraded into gingerbread 2.3.6 here i think less than 1 yr. its from Europe built and has notice you loss signal happen some cases.. it was new release gb 2.3.6 europe version so i download and upgrade my sgm.

before i was ok, later i found out that if i switch my signals into wcdma it turn into this Ø before i upgrade the is full bars hspda.

I try to change version of gb 2.3.6 asia firmware still got this problem.

Please help me.. I can't use of my internet, 2g is really slow for internet connection

Thanks in advance

God Bless you
[Samsung Galaxy Mini] vishal007:
just use firmware of your country and this won't be a problem
[Samsung Galaxy Mini] clubkids:
still no use sir vishal007

i already did flashing firmware its not working.

Is this working http://xdaforums.com/showthread.php?t=2226030

because im a bit afraid now of flushing firmware
[Samsung Galaxy Mini] clubkids:
Thanks sir Vishal007

may mini is good as new now thanks for help
[Samsung Galaxy Mini] romarvillamor:
:D
[Samsung Galaxy Mini] F4uzan:
Spammer, spammer everywhere.

Will add this to FAQ Thread.
[Galaxy S 4 General] warwolfx0:
This was done on a stock rom (works for 4.4)

I unlocked my bootloader first

http://xdaforums.com/showthread.php?t=2363025&page=1

(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")

if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.

Thanks broodplank1337

Download root from

http://download.chainfire.eu/supersu

or for more info read here

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

and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)

Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below

http://www.clockworkmod.com/rommanager

save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"

Now open up a command prompt (I did this as "run as administrator")

type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)

enter this command

adb reboot bootloader <enter>

(or hold vol+/- while booting)

Once in bootloader,

In the command prompt type:

fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)

This will boot into ClockworkMod

goto "install zip"

goto "install zip from sideload"

in the cmd type

adb sideload UPDATE-SuperSU-v1.80.zip

This sends to the phone and write to the phones Rom.

Now reboot, if asked, select no about the stock recovery overwriting the phone

when you boot into the OS download SuperSu from the market

and we have root without ODIN on a I9505G

I disappear alot and i DON'T read everyone's post

I update this when i need re-root

Sorry for the errors in this post

1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).

2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.

3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"
[Galaxy S 4 General] broodplank1337:
Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe
[Galaxy S 4 General] Miustone:
:3

Good one! :good:

btw....

your link is not working... this LINK here is working
[Galaxy S 4 General] WhiteSRT69:
hey thanks!!

will give it a try tonight!
[Galaxy S 4 General] taney:
Will this work on 4.3?
[Galaxy S 4 General] ChaoticUnreality:
Attempting to do this and for the life of me I can not get adb sideload to work correctly.

when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.

I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.

So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.

I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.
[Galaxy S 4 General] Chahk:
Try re-installing the USB drivers while in recovery mode.

Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
[Galaxy S 4 General] ChaoticUnreality:
I'll have to try that when I get home. thanks.
[Galaxy S 4 General] wilbarger:
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.
[Galaxy S 4 General] ChaoticUnreality:
Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks
[Galaxy S 4 General] gadams999:
Great write-up

This was my first ever root on my first ever Android device. It went well.

There were a couple things confusing about the post, I just want to make sure I did things correctly.

]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file

Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?

Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.

However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:

;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01

At that point when it booted into CWM recovery, I installed the drivers and was able to complete.

Now the happy owner of SuperSU running phone. Thanks again warwolfx0
[Galaxy S 4 General] SamuriHL:
I hope no one minds, but, I automated this.

<see new version later in thread>

Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.

Credits:

warwolfx0 for the OP

Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver
[Galaxy S 4 General] The111:
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.

So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.

Thanks.
[Galaxy S 4 General] SamuriHL:
Correct.

Etched in blood by a katana
[Galaxy S 4 General] carrot34:
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")
[Galaxy S 4 General] carrot34:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?

Thanks, Alan
[Galaxy S 4 General] SamuriHL:
Yes.
[Galaxy S 4 General] The111:
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).

Discussion here.

But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.

This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post. :D
[Galaxy S 4 General] occupational_hazard:
Apparently we also have a device specific Odin flashable auto-root file.

The link below goes to ChainFire's website. The zip includes a version of odin.

http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
[Galaxy S 4 General] SamuriHL:
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
[Galaxy S 4 General] MJHawaii:
Warwolfx0 can you update the OP with the new CF Auto Root Package SamuriHL posted including adding CF Auto Root to the title ..thanks MJ

Title should say How to Root I9505G this works on any version 4.2 or 4.3
[Galaxy S 4 General] SamuriHL:
Slight correction. What I posted is not a CF Auto root package. It's simply a script I put together to automate some of the steps from the OP.
[Galaxy S 4 General] MJHawaii:
No that is a CF AutoRoot package with the auto root .tar file with Odin

Download it unzip it with 7zip put your phone into Download mode click on Odin open it up select PDA then select the cfautoroot jgedlte .tar file and press start it will auto root the I9505G
[Galaxy S 4 General] occupational_hazard:
SamuriHL posted a zip that includes script, tools, etc. A zip that he put together, it includes his root script that I assume is flashable through recovery also. I posted the cf auto root link. Just to clarify things.

Sent from my Galaxy S4 GPE.
[Galaxy S 4 General] SamuriHL:
Therein lies both our confusion then. Thanks for clearing that up. :)
[Galaxy S 4 General] SamuriHL:
I've updated my version of the root method:

http://www.mediafire.com/download/fvsycsam9q8bffg/S4_GPE_ROOT.zip

o) Made it dynamic so you can replace the recovery*.img and update-supersu-*.zip files with new versions as they're released

o) Updated the ADB driver to the latest

o) Updated to 1.65 super su.

I used this to re-root MH5 a few minutes ago. Enjoy!
[Galaxy S 4 General] gchahinian:
will this work with the new jwr66y build?
[Galaxy S 4 General] SamuriHL:
Yes, that's why I stated that I used it on the MH5 build. :) That's the version for jwr66y.
[Galaxy S 4 General] gchahinian:
Got it, posted for a friend, wasnt sure what that meant. Thank you!

He should just grab the OTA, then he'll lose root, then just run the RUN.bat in your zip right?
[Galaxy S 4 General] SamuriHL:
That's what I did, yea. I had to flash the OTA from my external SDCARD cause it wasn't being pushed to me yet. Rebooted, ran the new script and had root back in less than 5 minutes. Should be pretty straight forward.
[Galaxy S 4 General] gchahinian:
Awesome...thanks again!
[Galaxy S 4 General] VZSpyder:
Thanks for putting this script together, SamuriHL. However, using both the original version and the new version of the script, I get stuck on "error: device not found", "< waiting for device >". I have USB debugging enabled. Is there something else I have to install or do to get the script to work?

Windows 7 x64, clean install. new out-of-box sgs4 google play edition.

Thank you
[Galaxy S 4 General] SamuriHL:
Sounds like you don't have adb set up properly. The first time adb tries to connect from a new machine, you need to accept the connection on your phone. It'll prompt you for it. If you don't do that, it won't work. I'm simply using adb to reboot into the fastboot mode. You could comment that line out of the script and reboot into fastboot mode manually (power off, hold volume up and down and press power) and start from there.
[Galaxy S 4 General] VZSpyder:
Thanks for the reply. Yeah, I'd heard that the phone was supposed to prompt for accepting the connection, but I've never gotten that prompt, I don't have any clues for why. I've tried re-installing ADB a few times, and on different computers (XP, 7) but still no luck.

I'll try the manual fastboot, thanks again.
[Galaxy S 4 General] SamuriHL:
Do you have adb in your path somewhere? If so, it could be an older version which isn't compatible with 4.3. That's always possible. Anyway, edit the run.bat script and change:

adb reboot bootloader

to

rem adb reboot bootloader

Then you can put your phone in fastboot mode and run the script and it should do what you need. But if ADB isn't recognizing your phone, it may have problems with sideloading, too, so, we shall see.
[Galaxy S 4 General] VZSpyder:
Alright, editing the script as instructed and skipping straight to fastboot worked successfully- I now have root. Odd that ABD wasn't working for the first step, but it's all good now. Thanks a lot!
[Galaxy S 4 General] SamuriHL:
Awesome! Glad it worked. Not sure about your adb issue. Might wanna look into that. :D But at least you have root now.
[Galaxy S 4 General] occupational_hazard:
Delete
[Galaxy S 4 General] ZypherZ:
I previously had no problems with device not found when running the fastboot command. When running the sideload command it would say device not found. What I had to do was update the driver to the composite driver. Yes, I had to do it at both screens. Once when starting the process (phone already on) and once after navigating to the sideload option in the recovery menu ( after fastboot )
[Galaxy S 4 General] chongwj:
Thank you for your help. Followed your instructions and worked, got my S4GE rooted again. :good:

Is that mean we have to do this every time there's OTA update?

And can we just rerun your script and work everytime?
[Galaxy S 4 General] SamuriHL:
Yes, you'll have to re-root after each OTA. And yes, that's the theory. Just run the script and it should re-root you without overwriting stock partitions.

---------- Post added at 02:54 PM ---------- Previous post was at 02:46 PM ----------

@warwolfx0

I sincerely didn't mean to hijack your thread. I only meant to create some automation for your awesome process. If you want me to start a new thread for my script I can do so. Apologies to you.
[Galaxy S 4 General] GoodToGo1:
Having trouble with the Adb drivers, really frustrating.
[Galaxy S 4 General] SamuriHL:
Did you use the latest one from Koush? That's what I use and it works fine for me. Also you need the latest adb version. And you need to make sure you allow the adb connection on your phone the first time you make it.
[Galaxy S 4 General] othermark:
Thanks for documenting the non-flashing way to do this! Of course, the number one issue people will have problems with is the adb device drivers during this process, because it requires three different drivers.

1. The adb driver when USB debugging is enabled. (verified via adb start-server -> adb devices)

D:\i9505g\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>.\adb devices
List of devices attached
96865499 device

2. The fastboot device support. (verified via adb reboot bootloader -> fastboot devices)

D:\i9505g\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>.\adb reboot bootloader

D:\i9505g\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>.\fastboot devices
96865499 fastboot

3. The sideload driver. (verified via .\fastboot boot [recovery image] -> install from sideload -> windows device manager).

For this you may not have it and have to do something like this:

http://xdaforums.com/showthread.php?p=37981336#post37981336
[Galaxy S 4 General] SamuriHL:
For the record, I've not had any issues using Koush's universal ADB driver in all ADB modes.
[Galaxy S 4 General] jasunto:
hope this question isnt too trivial, but can i just fastboot flash recovery recovery_blah_blah.img and flash it so i can always run cwm and flash.zip for SU from SD card?
[Galaxy S 4 General] SamuriHL:
Sure. That's the more traditional way to do it. This method is for people who don't want to overwrite stock recovery for whatever reason.
[Galaxy S 4 General] jasunto:
tried to flash recovery and that produced a FAILsecure - secure check failed. Guess i have to research this. Maybe it has to do with the secure boot enabled showing in the bootloader. Sorry im coming from HTC and havent seen this before.