yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] JoeFCaputo113:
Already figured it out as I found a page of a million dialer codes after posting this. I searched before I posted... but I guess not hard enough -__-
[Asus  Eee Pad Transformer Prime] evilcuber:
Im not sure why by every 4.2 rom i've tried runs slow and laggy in comparison to the 4.1 rom's i've had before, and i've tried several 4.2 roms, not just one. Any idea why it's slow?
[Galaxy Note II Q&A, Help & Troubleshooting] aqertmen:
I recently found out I soft bricked my phone after browsing through the forums. I looked up for the solution and it turns out that I need to reset it back, no problem with that so I installed odin back again (I rooted my phone before so I had it). I first downloaded the official firmware from sammobile or some site like that and I downloaded a PIT file for my phone because the tutorial said it was essential when resetting a smartphone. I followed every step but when I launch odin and select the required tick boxes and the PDA PITi I start it. It starts up but in the middle of the loading I shows up the DO NOT TURN OFF THE TARGET!!! message and It stops.

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004>

<ID:0/004> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

This is the error and I can't seem tı get past it. I really need to deal with this quickly so if any of you have a solution, ı would appreciate it. Thanks
[Galaxy Note II Q&A, Help & Troubleshooting] aqertmen:
Anyone has the same issue? I need to fix this ASAP.
[Galaxy Note II Q&A, Help & Troubleshooting] aqertmen:
a

<ID:0/009> Odin v.3 engine (ID:9)..

<ID:0/009> File analysis..

<ID:0/009> SetupConnection..

<ID:0/009> Initialzation..

<ID:0/009> Set PIT file..

<ID:0/009> DO NOT TURN OFF TARGET!!

<ID:0/009> Get PIT for mapping..

Now the error goes like this and nothing more.
[Galaxy Note II Q&A, Help & Troubleshooting] doc1975:
I'm getting the exact same problem, can't fix it :(

Have you made any progress?

Thanks.
[Galaxy Note II Q&A, Help & Troubleshooting] Dethskul:
Hi

Do you have a custom recovery?

Which phonemodel do you have?

U can install TWRP through Odin using a tar file. Go to TWRP and search your model, get the tar file and install it.

From TWRP u can sideload a rom using ADB.

You can push files to the phone using it, that way u can push the rom to the phone and install it through TWRP.

A long way around but worth trying when all else fail.
[Xperia SP Q&A, Help & Troubleshooting] nitun07:
I have just installed the new recovery for locked bootloader on my C5302 and tried to perform backup. The backup did complete but it didn't backup my sdcard 2nd partition where all my user apps are linked to(using Link2Sd). Even the partition was not shown in mounts and storage menu of CWM. Is this a bug?
[Xperia SP Q&A, Help & Troubleshooting] puneethv:
u need to get into advanced menu and mount ext-card.....
[Xperia SP Q&A, Help & Troubleshooting] nitun07:
There is no mount option for sd-ext2 in advance menu. No mount option for sd-ext2 in mounts and storage menu either.
[Xperia SP Q&A, Help & Troubleshooting] zolaisugly:
Got this same issue... Think it is because the cwm that is posted its not really for our device. It works but not 100%
[Xperia SP Q&A, Help & Troubleshooting] nitun07:
Have you tried the CWM for unlocked BL? Does it have the same problem?
[MDA III, XDA III, PDA2k, 9090 General] rakh1:
Hold it for a second or so - seems to work for me...
[Micromax A110] akashvfx:
Port Android 4.2 notification bar for android 4.1.1
[Micromax A110] lead3r1:
dude wrong section post in general section/q&a section
[Micromax A110] Divyesh49:
Same qui.?

Anyone have idea???:confused:
[Barnes & Noble Nook Tablet] Caradineme2:
I've tried two different roms in the last week with the same end result. The first was caynogenmod 10.0 stable and nightly. Now i just tried with slimbean 4.22. Installs are both successful but when the nooks gets passed the caynoboot screen and shows the splash screen from the rom, it freezes then powers completely down. I've noticed an error in wiping data/factory reset which says "E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2", i was wondering if this may be what is causing my issue? I'm using clock work mod recover version 5.0.2.8. My wipe methods are data/factory reset, cache partitions, and dalvik cache. Any suggestions or opinions would be greatly appreciated. Thanks in advance.
[Barnes & Noble Nook Tablet] asawi:
I have no idea if this is causing your problem, but as I understand you're supposed to use CWM 6.x.x when installing CM10 or 10.1.
[Barnes & Noble Nook Tablet] Caradineme2:
I will try that then, I haven't messed with the nook in sometime now and had actually thought about updating the recovery. Any recommended version or just whatever is the latest?

Sent from a Galaxy within my palm
[Barnes & Noble Nook Tablet] digixmax:
You can find Succulent's recent compilation of CWM and TWRP at his recovery repository http://goo.im/devs/succulent/acclaim/recovery. Use "***sdcard.img" for SDcard based recovery (rename it to recovery.img before copying over to the SDcard boot partition). "flashable[recovery].zip" are recovery image you can flash onto emmc.

FWIW, you can find pointers on how to install CM10 internally at http://xdaforums.com/showpost.php?p=43326042&postcount=123.
[Xperia Play Q&A, Help & Troubleshooting] Streiff353:
On Wednesday, I was helping a friend move on a nice, hot day. I was sweating like a filthy pig and my phone was in my pocket and within a few hours it would not turn on when I tried to do so. That night I really didn't know what was wrong and the next morning I tried to turn it on and the red LED would flash 3 times in succession. I looked this up and they said "dead battery." Sure enough, I charged it and it took a minute for the LED to turn on, and as it charged it was red, then orange, then green. But even once fully charged, when I tried to turn it on it would only vibrate, but no screen action whatsoever. Note: the battery was at around 60% when the phone quit responding. The next morning it was dead. I have had the phone for a year now and the battery will last me at least 2 days if I don't play games and such.

The next morning, when using the flashtool it would go into blue LED'd fastboot and green LED'd flash mode. I thought I had backed up everything, but somehow those files were nowhere to be found. So I flashed the original 2.3.3 firmware, and still nothing. I used PC Companion and it said "Problem: The phone/tablet contains modified software that cannot be updated. Details: Sony Update Engine failure (error 2003)." I contacted Sony and I am still awaiting a response. So, on friday I'm ready to take this turd into the Verizon shop and I turn it on and wait about 30 seconds and I get the SE logo. It loads just fine. I set it up and try to update, but it won't allow me. I'm thinking, great, I'm stuck with 2.3.3... until I turn the screen off and try to turn it back on. And again, nothing. No response. So I'm thinking I will bring it in Saturday. I re-lock the bootloader in some attempt to hide that I rooted the phone, and flashed the 2.3.3 again. Note: I rooted my phone in December and have had no problems. I didn't flash any ROMs or Kernels. I am a simple man.

Saturday morning, after my phone has been off for 10 hours, it turns back on again. Same thing happens. Also, I spent a while on Thursday, Friday, and today trying to research and solve this problem. My brain hurts. But alas, I only had it off for 3 hours and it turned back on, and it did the same damned thing when it turned off. It simply doesn't turn back on. I don't know if it's the screen, or if there is moisture under there, and I haven't researched taking it apart yet. Any advice?
[Xperia Play Q&A, Help & Troubleshooting] Sprint_ST_1050:
Hum...

Did you try with the software : Flashtool v0.9.11.0?

and flash one of those FTF file?

> Sony Ericsson Xperia Play > Xperia Play Android Development > [FIRMWARE][FTF] Collection of Xperia Play R800a/i/at/x firmware

or

> Sony Ericsson Xperia Play > Xperia Play Android Development > Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S

or

> Sony Ericsson Xperia Play > Xperia Play Android Development > [FIRMWARE] Working Xperia Play FTF Collection (AndroidFileHost)
[Xperia Play Q&A, Help & Troubleshooting] Streiff353:
I downloaded the newest version of flashtool, (9.11), and I downloaded the "Poo-Tang/Xperia Gamer" R800x Verizon 2.3.3 (CDMA) a few days ago, and flashed it already. Other information: When I attach the phone to the computer, it makes the docking and undocking sound, but the normal menu for accessing the phone does not show up, even when the phone actually came on recently. That is abnormal. Also, flashtool states that my phone is still Rooted, although I supposedly re-locked the bootloader. These last two comments may be pointless, but I figure the more information I give, the better. Any other ideas, kind sir?
[Xperia Play Q&A, Help & Troubleshooting] Sprint_ST_1050:
Not that much...

It looks like you can connect into fastboot mode (search button - blue led) so you can use this command:

fastboot.exe -i 0x0fce getvar version

or recovery mode (back button - green led). And you can flash...

When you turn on it vibrate,means the kernel start. But you can't enable debuging. Can't use adb.

And the SD card doesn't show-up in windows, means the system doesn't finish to load.

Correct?

So just flash the good Ftf and send back to Verizon shop if it's under waranty.
[Xperia Play Q&A, Help & Troubleshooting] Streiff353:
Thanks, that's pretty much what I ended up doing. Luckily, it's under warranty. But thank you for sending me those other links with the ROMs and Kernels, I will be using them with the new phone, as well as properly backing everything up.
[Xperia Play Q&A, Help & Troubleshooting] Sprint_ST_1050:
One last thing, try the software s1tool.

Connect the device in recovery and clic the button RESTORE.
[Galaxy S II Q&A, Help & Troubleshooting] Hamodi:
my laptop had shut down it self when updating the S2 to JB with odin

now the phone do now statrup and cant go into download mode any more

did i bricked it ??

is there any way to fix it ?
[Galaxy S II Q&A, Help & Troubleshooting] Hamodi:
is there any way to fix it ?

i still get a usb connect when i pluge it

it show driver with the name SEC S5PC210 Test B/D
[Galaxy S II Q&A, Help & Troubleshooting] GamingDj:
Mobo replacement will help.If no download Mode,nor recovery,then go to the service center.you can't do anything.
[Galaxy S II Q&A, Help & Troubleshooting] Hamodi:
i had send it to service center nothing i can do

i had read about the JIG usb but dont have one
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Service centre said "no way"?

If so, I don't think you'll be able to do it yourself.

A jig? You can try that.

Jtag? Why not.

Mobo replacement? For sure.

You weren't trying to flash a pit file did you?

Sent from...this is not even my S2
[Galaxy S II Q&A, Help & Troubleshooting] Hamodi:
some one had call you here ???

i dont see any usefull for your post :) so why dont you just stay away from Q&A section :) you just bother others not only me :)

im glad i dont have this phone for my self ,, to see someone like you on every thread just make fun of other pissing off :@

so just stay out of busness :@
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
1) I dunno who you are, never seen your username before.

2) Do you think I was making fun of you? Re-read.

3) what's listed above is what you can now do with your phone.

4) I didn't brick it, you did.

5) I'm in it for the sake of the devices, not the users.

Sent from...this is not even my S2
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
If a service centre can't/won't fix it (I don't believe this; they make a mint every time they fix a phone like this, money for jam for them) then throw it in the bin, because you're certainly not fixing it yourself given the mess you got yourself into in the first place
[Galaxy S 4 Q&A, Help & Troubleshooting] Mister Jozo:
Some time after upgrading to MEA firmware my proximity sensor is malfunctioning.

I installed an app that tells me when the sensor is covered.

When i pass my hand over the sensor it says status covered and it stays like that until I lock and unlock the screen.

This translates to problems with everyday usage. Like when answering calls my screen turns off and it won't turn on until locking and unlocking.

I am using stock samsung firmware that I upgraded over Kies. Rooted with chainfire auto root.

I clean my screen regularly and don't have a case or screen protector.

Can anybody help?
[Galaxy S 4 Q&A, Help & Troubleshooting] Mister Jozo:
The MEA firmware updates the camera firmware when you first enter the camera app after upgrading.

The proximity sensor and light sensor are somehow connected.

Because I don't use the camera I didn't get the camera firmware update which bugged out my light sensor and caused problems with the proximity sensor.

Just entered the camera app and everything is working :)
[Galaxy S 4 Q&A, Help & Troubleshooting] aHcVolle:
i have the same problem but i couldn't fix it yet.

i'm on cm10.1 and this is what i did:

flash omega v9 (MGA) with cwm did a factory reset and started the camera app.

It didn't help the problem was still there.

flashed I9505XXUBMGA-PRE-ROOTED-ODEX-FULL.tar.md5 with odin, did a factory reset and started the camera app. didn't help

flashed I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5 with odin, did a factory reset and started the camera app. didn't help

do you have any other ideas ?

Can you tell me which FW you are running right now, maybe it helps if i install the exact same one.

- Chris
[Galaxy S 4 Q&A, Help & Troubleshooting] rseijen:
This is also not solving my problem with the sensor. I tried different kernels, differents Roms, did a full wipe, factory reset, etc... Still my sensor stays on... Any ideas?
[Galaxy S 4 Q&A, Help & Troubleshooting] aHcVolle:
the funny thing is that after posting here my sensor started to work again .. at least kind of ..

sometimes it works, sometimes not.

Try to go in a dark room (0lux measured buy the light sensor) and see if your proximity sensor is working in there. It does for me sometimes.

Also try to change your phone orientation, it seems that my sensor doesn't like the phone beeing on a flat surface or holding it vertical...
[Galaxy S 4 Q&A, Help & Troubleshooting] rseijen:
I tried that. My sensors works but somehow sees something close by.. Especially when its bright. On average mij ADC is 40.. Thats way to high but I cant change the threshold of the sensor.. :( Else I could increase the tollerance and get it back to work..

I hope someone figured out how to change the parameters of the sensor or how to re-calibrate the thing... :(
[Galaxy S 4 Q&A, Help & Troubleshooting] - Overlord -:
I solved!

Hello guys, maybe I found the solution (at least for me it worked completely), but it's not so straightforward...

I had the same exact problem as the OP and tried almost everything but in the end, when I was almost convinced to return it so Samsung, I tried to watch a disassembly guide and discovered that it wasn't so hard to open the device... (following the first guide I found on youtube with keyword "s4 disassembly")

So I took the risk and in 20 minutes with just a small (+) screwdriver and my nails i opened the thing, detach the proximity sensor/speakerphone and blow it with my mouth, then just reassemble and everything was working again! I don't know if it was a software of hardware thing or both...it just worked :)
[Galaxy S 4 Q&A, Help & Troubleshooting] rseijen:
I even tried that and also I just replaced the whole speaker/proximity sensor.. I was kinda hoping it was broken. But nope, even the new one is misbehaving. It really seems to look like a software-problem..
[Galaxy S 4 Q&A, Help & Troubleshooting] aHcVolle:
how can i read out the raw data from the sensor ?

[edit]

got it,

cat /sys/devices/virtual/sensors/proximity_sensor/raw_data

mine is on 46 all the time ...

the thresholds are 60 & 45 .. so how can we edit them ?

ok i got it but you need to be root.

thanks to greaty in this thread

i was able to recalibrate my proximity sensor and it's working great again.

my prox_cal now shows:

24,84,69

instead of before

0,60,45

maybe the distance is a little lower now i've got no problem with this at all
[Galaxy S 4 Q&A, Help & Troubleshooting] rseijen:
Tried this too and also no solution
[Galaxy S 4 Q&A, Help & Troubleshooting] aHcVolle:
didn't it work ?

for me it is perfect right now ...

if you couldn't recalibrate maybe it's because you're on a samsung rom.

try to flash CM (do a nandroid backup before) and recalibrate, after that you can restore your samsung rom. The calibration data is stored on your efs partition so it will survive rom flashs and will still be active in oyur samsung rom.
[Galaxy S 4 Q&A, Help & Troubleshooting] mcelicalderon:
Fixed It

This is amazing! I've tried so long to fix this. I'm using the CyanogenMod nightlys (CM 10.2) on my galaxy s4 google play edition (i9505G).

Finally everything is perfect just by running those three commands:

su

echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

------------------------------------------------

raw_data = 51

thresh_high/low = 89,74

Thank You!!
[Galaxy S 4 Q&A, Help & Troubleshooting] kaz219:
fixed!

Fantastic. fixed using the three commands.

$ su

$ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal

$ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
[Galaxy S 4 Q&A, Help & Troubleshooting] aHcVolle:
i'm glad it helped :>
[Galaxy S 4 Q&A, Help & Troubleshooting] kage00:
I tried this and nothing worked... I wasn't able to recalibrate anything, the settings all stayed the same. I think I have a physical problem with the sensors - not something that can be reset with calibrating files or changing firmware...

I rang samsung from here in France and got transferred to a call center in Morocco, a lady told me to go to settings and turn after screen capture on, then go to the proximity sensor settings in call settings and turn that off, then make sure back up and restore was set up and then do a factory reset, the problem was still there and by then she had already hung up on me (great customer service!)

So I used triangle away from chainfire and reset the flash counter to zero, and then got rid of any signs of root apps from the internal memory.

Then i took the phone to a samsung repair center in the city and he said to come back in a few hours and he was going to flash a new firmware on it and that would make it work properly... I'd already tried various differernt firmwares though and it didn't work. When I went back to see him he told me that it didn't work and the phone would have to be sent away to Samsung and it would take anywhere between 2 - 6 weeks...

that was 1 week ago.

I'm really hoping that it is only going to take 2 weeks!
[Galaxy S 4 Q&A, Help & Troubleshooting] aHcVolle:
hmm i guess now it's so late to help but just for my information, did you run

cat /sys/devices/virtual/sensors/proximity_sensor/raw_data

and did you values change when you put your hand over the sensor?
[Galaxy S 4 Q&A, Help & Troubleshooting] kage00:
I don't think I did that no, I did follow what was written in this thread and most of what is written in this thread too, but I'm not sure if I entered that command though.

I did however enter *#0*# into the phone after flashing back to a stock samsung rom and the sensor was working and I noticed when I put my hand infront it changed, the problem was that my hand at 30cm distance was still able to affect the reading of the sensor
[Galaxy S 4 Q&A, Help & Troubleshooting] abdali_m2:
u0_a261@jflte:/ $ export PATH=/data/local/bin:$PATH

u0_a261@jflte:/ $

u0_a261@jflte:/ $ su

root@jflte:/ # echo 0 > /sys/class/sensors/proximity_sensor/prox_cal

root@jflte:/ # echo 1 > /sys/class/sensors/proximity_sensor/prox_ca

su-mksh: can't create /sys/class/sensors/proximity_sensor/prox_ca: No such file or directory

1|root@jflte:/ #

There is wrong with code ??

And see the picture maybe its help
[Galaxy S 4 Q&A, Help & Troubleshooting] kage00:
Just got my phone back from being sent off to Samsung for repairs, it took them over a month to fix it and get it back to me!

At least its working now...
[Galaxy S 4 Q&A, Help & Troubleshooting] booleanbetrayal:
SAVED!

This was such a huge annoyance. THANK YOU for posting this solution!!! :D
[T-Mobile, Samsung Galaxy SIII] rage913:
Hey guys. So the 4.3 camera got released early and it's been all over the place. I found out about it yesterday. Some people have been hit or miss with it. So here's the run down.

I've got the .apk installed and it's in fact working... Except for ffc. Every time I try and take a picture with it phone goes into a hard reset. Quite annoying really. I've moved the apk over to my /system/app folder and im still getting the issue. And I even renamed the original gs3 gallery app to .app . bak and I still can't get her up and running.

It's nifty and I was using photosphere for the first time yesterday was awesome. So just wondering if anyone had any ideas? Running cm10.1 7-6 nightly stock cm kernel (which I need to go back to ktoonz :p)

Thanks peeps!
[Galaxy Note II Q&A, Help & Troubleshooting] balkyny:
I just noticed that this button does not work

Once I reboot phone, it starts to work... but only for one call. After that call, it does not work again.

Anyone have this problem? know how to fix this?

Tried to disable the button and re-enable... does not affect it. Still same problem.

Thank you.

it runs JB 4.1.2
[Galaxy Note II Q&A, Help & Troubleshooting] $ideWinder:
WTH are you talking about man?? :confused:
[Galaxy Note II Q&A, Help & Troubleshooting] balkyny:
There's a button "volume increase" that appears during a call. What's the confusion? Need to read the TOPIC not only the post. :)
[Galaxy Note II Q&A, Help & Troubleshooting] jujuburi:
It gets disabled when you use Bluetooth, just fyi.
[Galaxy Note II Q&A, Help & Troubleshooting] balkyny:
thanks for attaching the picture...

I do not use Blue Tooth, thus it is always off.
[Galaxy Note II Q&A, Help & Troubleshooting] bhowanidin:
Try unchecking, rebooting, then re-checking the option shown under Phone settings.
[Galaxy Note II Q&A, Help & Troubleshooting] jujuburi:
Maybe Rom then? I'm sure you're on Stock kernel. Mine never was disabled!
[Galaxy Note II Q&A, Help & Troubleshooting] balkyny:
I tried to uncheck, reboot, check it again... same result. It works, then you disconnect, make another call, and it does not work again :(

I have no idea. It is a T-Mobile (USA) phone... I am not that advanced with stuff like this when it comes to phones.
[Galaxy Note II Q&A, Help & Troubleshooting] bhowanidin:
For T-Mobile, follow the link and basically follow directions for unrooting. It will load stock everything for you. File other directions if you want to root afterwards.

http://xdaforums.com/showthread.php?t=1955423
[Galaxy Note II Q&A, Help & Troubleshooting] balkyny:
xprtol hazards

Thanks, but won't it void my warranty? I tried it with another phone, and right after that when I tried to get updates, it said that my phone is not eligible for updates anymore.
[Galaxy Note II Q&A, Help & Troubleshooting] bhowanidin:
Returning to stock will put your phone back in warranty state. Just don't root and you'll be fine.
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] mohamed dx:
is the galaxy grand good for gaming with out roms root etc games like (most wanted asphalt 7 dark night rises) and can i move apps to sd card without root ?