yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] ASMI1:
Hey bro follow this to make clean install (but this will wipe your data)

DO IT AT YOUR OWN RISK

1- make sure you have kies installed or just install galaxy sl usb drivers (thanks to Zulfauzi).

2-Download odin3 v1.85 from the attachments.

3-Download full DDLF2 from here (thanks to (thanks to sgatechwork).

4. Run Odin3 v1.85.

5. Check Re-Partition, Auto Reboot and F. Reset Time.

6. Click PIT button and select this file: latona_20110114.pit

7. Set it to download mode : Press Volume down + OK first, then hold Power button.

8. Connect USB cable and the program will detect the phone's Com number.

9. Click Start button to download the PIT file to phone.

10. After it is Done Click on Reset button [Partition box should be unchecked automatically - Thanks to jaskir].

11. Click PDA button and select this file: CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5.

12. Click PHONE button and select this file: MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5.

13. Click BOOTLOADER button and select this file: APBOOT_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5.

14. Click CSC button and select this file: GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5.

15: You should unplug usb cable, remove battery, insert battery and bring it back to download mode. I have never been able to bring it to download mode with usb plugged in. [Thanks to jaskir for this suggestion to make it clear to new users!].

16. Click Start button to flash these files to phone.

17. Do not touch anything till you see PASS on the program window.

18. Factory reset.

19. [To fix issues that pertain] Reflash from steps 9 -15 again, No need of latona at this point.

thanks to Misledz for the instructions (original thread here)(I only edited file names).

Now download any Jb 4.2.2 rom and carefully follow the OP instructions.

I suggest CM10.1 A8 by dhiru1602 (thanks to him), rom is verry stable and smooth.

if I helped you please hit the "thanks" button:)

Best regards;)
[Samsung Galaxy SL i9003] dr_amjad:
Thanks for your reply

but there's another method about updating by CWM RECOVERY

do you know how this method done ?
[Samsung Galaxy SL i9003] mustafahussain:
yes there is another way if you have recovery installed. Just tell us what ROM you are on (your 4.1.2 ROM name) and try to find out if you have CWM recovery(volume up+home+power). Let us know this this then we will proceed.

[MENTION=3374872]ASMI1[/MENTION] :He is on a 4.1.2 OS means he have a custom ROM and re-partioning is not mandatory because he is comming for a CM10 base.
[Samsung Galaxy SL i9003] dr_amjad:
Thank you very much mr mustafa

i download the ROM from video on youtube and this is link of video

http://www.youtube.com/watch?v=VqypSD3JBJk

It's CM 10 Alpha 3

And in the video there's a download link of the Rom and this is the link which in the video

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

by the way : when i click power key there is an option called : Reboot

when i click on Reboot tell me that i can Reboot my phone and recovery and download mode

Thanks for your reply
[Samsung Galaxy SL i9003] Drizzt_Kueh:
If you like the jelly bean 4.1.2 (CM10) by Dhiru, surely you'll like the CM10.1 version.

It is in here. Review it for more details.

You will need the latest CM10.1 in Dhiru1602's downloads and this gapps..

Download both on the SD card. Then, basically this will be the instructions to install it:

Upgrading from previous versions of CM10
1. Reboot to Recovery.
2. Select the ROM zip from your SD Card and flash.
3. Flash Google Apps.
4. Reboot

PD: By the way, you can use the Reboot -> Reboot to recovery option you've mentioned.
[Samsung Galaxy SL i9003] dr_amjad:
Thank you very much for your reply

i will try and tell you

but i will not do any thing about : Data wipe/Factory reset & 5. Format dbdata﻿. , right ??
[Samsung Galaxy SL i9003] dr_amjad:
I tried it

When i choose zip from sdcard and choose the rom tell me :

Installing : /sdcard/others/Cm10.1-Galaxy SL - JDQ39E-Alpha8.zip

Finding Update package ....

opening update package ....

E: Can't open / /sdcard/others/Cm10.1-Galaxy SL - JDQ39E-Alpha8.zip ( bad )

Installation aborted

What can i do ??
[Samsung Galaxy SL i9003] acuicultor:
Redownload rom.
[Samsung Galaxy SL i9003] ASMI1:
try to remove the rom zip from sdcard and copy it again from pc, this worked for me when I tried to install slim CM 7 by TheFrankenstain (here the thread if you wanted to try it..rom link here)(You rom is awesome TheFrankenstain...thank you:))

If this didn't work then try to redownload the rom (don't use your phone to download roms...bad idea:D).

to make sure rom's archive is not corrupted, check you rom MD5 sum (Dev-Host server provide the correct MD5)

HashCheck is a good tool for this.

---------- Post added at 09:52 PM ---------- Previous post was at 09:29 PM ----------

BE CAREFUL...You can only update to CM10.1 rom (or any other rom based on CM10.1) only if you have CM10 Alpha4 rom (or any other rom based on CM10 Alpha4)

But in your case (you have CM10 A3), you have to follow the whole guide mentioned in the second post.

This is what LoLaTiOn said:

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

thread here.

If you are worried about your data make full backup using recovery and you can restore your apps or your full rom at any time...clean Install is always recommended over updating from previous versions.

BTW...I think full Nandroid restore is dangerous due to different partitioning in ICS/JB roms so it's recommended always to reparation using odin and install full firmware again.

Also, any custom rom is rooted and deodexed and has CWM recovery pre-installed.

sorry for my bad english:)
[Samsung Galaxy SL i9003] dr_amjad:
Thank you very much mr ASMI 1 for your reply

but sorry i am still Noob in android development and updating :(

but according to your reply i must do :

- Wip Factory

- Format/system format/emmc

- Flash Carbon and gapps

- Reboot recovery

- Wipe cache and dalvik cache

Right ??

and please is there a video about my case (( updating samsung gt i 9003 from cm 10 alpha 3 to cm 10.1 alpha 8 )) ??

and sorry for annoyance you :)
[Samsung Galaxy SL i9003] dr_amjad:
(( if older base CM10 Alpha3 Full KPE please !!! ))

what the meaning of KPE ??

and i must do this ?? (( if older base CM10 Alpha3 Full KPE please !!! ))
[Samsung Galaxy SL i9003] mustafahussain:
it means that if you have a base older to CM10 Alpha 3 then you should proceed with full KPE,,,

so IF YOUR CURRENT ROM IS ON CM10 Alpha 3 I would suggest just flash CM10 Alpha4 base ROM by Dhiru then,

-Wipe Factory

- Format/system format/emmc

- Flash Carbon and gapps

- Reboot recovery

- Wipe cache and dalvik cache
[Samsung Galaxy SL i9003] dr_amjad:
Now i have Cm 10 alpha 3

you want me to do these steps :

-Wipe Factory

- Format/system format/emmc

- Flash Carbon and gapps

- Reboot recovery

- Wipe cache and dalvik cache

and update my phone to Cm 10alpha 4 or cm 10.1 alpha 8 ?????????
[Samsung Galaxy SL i9003] ASMI1:
No, to upgrade from previous version of CM10 follow this:

and then

-Wipe Factory

- Format/system format/emmc

- Flash Carbon and gapps

- Reboot recovery

- Wipe cache and dalvik cache

here where to download CM10 A4 and google apps(20121011 for CyanogenMod 10.0.x) (thanks to master dhiru1602).

BTW, in the past we used to install XXKPE stock rom (pit, bootloader, PDA, Phone, and CSC)(this is what meant by full KPE) and then install DDLF2 as PDA in download mod. But now full DDLF2 is out so we don't need XXKPE anymore to make clean install, you just install full DDLF2 (pit, bootloader, PDA, Phone, and CSC) the same way you install XXKPE and then proceed with installing your custom rom.

it is recommended to make clean install always before installing any custom rom (CM or rom based on CM) to prevent any issue (installing custom rom over another custom rom may cause some problems like lags and no signal issue...etc) just make clean install.

I advise you to upgrade only if, for example; you want to update to REMICS rom and you have previous version of REMICS rom or you want to update to carbon rom and you have previous version of carbon rom or you want to update to CM10.1 A8 rom and you have previous version of CM10.1 A7 rom...Do you get my point?
[Motorola Droid RAZR] xMrArnoldx:
so ive tested about every rom and without a doubt liquid smooth is my favorite. my only issue is performance control will not work. ive done a completely clean install of liquid smooth, redownloaded it and reinstalled but no matter what any app i use to overclock or anything like that crashes. ( ive only tried performance control and pimp my rom) any solutions to this crashing?
[Nexus 7 (2013) Q&A] cyaclone:
Safe mode appeared on the bottom left corner of the launcher screen when enabled. I thought that I had turn off the unit but when turning it on the next day, found that it was in Safe Mode.

How do you get to Safe Mode?

What is different about Safe Mode than the normal Start?

I noticed that icons were random along with widgets that were never selected.
[Nexus 7 (2013) Q&A] danvee:
IIRC, if you hold down the power button while at the shut down menu it'll do that.

Safe mode, like on a PC, just loads needed system apps. No 3rd party stuff.

Used for diagnostics.

Just reboot and it should be gone.
[Nexus 7 (2013) Q&A] sfhub:
See this post:

[Info] Guide to entering safe mode, bootloader, stock recovery
[Transformer TF300T Q&A, Help & Troubleshooting] mcflyy_:
My tablet is stuck in bootloader .... how do i factory restore ?
[Transformer TF300T Q&A, Help & Troubleshooting] Fred@asus:
Simply press the power button and the vol down button and that will allow you to restore.
[LG Optimus L9 P760, P765, P768, P769] Mysterious_X:
The phone, a P769, is stuck with the weird touch screen. This occured when I flashed some kdz in an attempt to unlock the bootloader. Now I cannot flash any kdz as it gets stuck at 16% in the analysis stage when the phone is in SW upgrade mode. If I try to flash when the phone is turned on normally it gets stuck at 6% on the update stage. Fastboot will not work at all, and I can't boot into recovery to flash the fix for the screen... Please help.

Additional info: I can root it and install the recovery installer, but I can't boot into recovery.

Edit: Fixed the issue, finally.
[Samsung Galaxy Nexus] tchaikin:
Hi all,

I'm running the newest Slimbean 4.3 beta with the Slimbean 4.3 GApps installed on my VZ Gnex. I tried to Chromecast from Play Music today, and I get the error Cannot cast to '<Chromecast>' where <Chromecast> is my device's name. I can Chromecast just fine from YouTube and Netflix on my Gnex, and have no issues casting from Play Music on my Xoom running CM10.1.

I was wondering if anyone else was having this same issue. I'm fully aware that running beta software is bound to have bugs, so I'm not expecting the experience to be perfect, but was trying to determine if it's something messed up with my setup or a true bug.

Thanks,

TC
[Samsung Galaxy Nexus] jimmyco2008:
I don't think anyone else here has a Chromecast.... But I would try out maybe a 4.2 ROM, since that's what the Xoom has.
[Samsung Galaxy Nexus] tgtoys:
I'm having the same issue with my Nexus 4 running slimbean. Seems like this is a common problem for Motorola users (lots of topic results via search) but can't understand why it doesn't work for a Nexus device running 4.3. All other apps work no problem. Hope it isnt another root block attempt by Google...that would be tragic.
[Nexus 7 (2013) Q&A] xGary:
I can clearly see the light bleed on the notification bar, under normal light, and at 70% brightness. I didn't have to turn off the lights or turn it to max brightness or make the screen completely black or anything.
[Nexus 7 (2013) Q&A] Matrix_19:
Take a picture?
[Nexus 7 (2013) Q&A] aimfire72:
Mine is simaler and it bugs me. Tried to ignore, but eye is always drawn to it. Taking it back tomorrow

Sent from my Nexus 4
[Nexus 7 (2013) Q&A] player911:
I've looked for the light bleed and I can't find any on mine. I know there are some, but not this bad where it is noticeable.
[Nexus 7 (2013) Q&A] Matrix_19:
Mine is very smaller

I tried to reproduce the same thing on your picture (with the same light) but it is not as bright as yours

I won't return mine but in your case you should have it replaced
[JAM, MDA Compact, S100 General] lourd:
for caller id...
[JAM, MDA Compact, S100 General] duke911:
nice job.. 8)
[JAM, MDA Compact, S100 General] Bubisch:
Lourd, this is a really great skin! Very nice job, mate!
[JAM, MDA Compact, S100 General] alexfendi:
would u be kind enough to upload the pit maker. i have lost mine. thanx
[JAM, MDA Compact, S100 General] bimmer9999:
i have no idea how to install it? can someone pls help,thanks!!
[JAM, MDA Compact, S100 General] lourd:
i've used this...
[JAM, MDA Compact, S100 General] double_ofour:
Thanks for sharing buddy!
[JAM, MDA Compact, S100 General] alexfendi:
thanks lourd!!!
[JAM, MDA Compact, S100 General] nsriza:
Good s/w and sample.
[JAM, MDA Compact, S100 General] chakra:
how do I install it?? can you help
[JAM, MDA Compact, S100 General] alhambra:
copy lourd.pit to My Documents/Templates...

thanks lourd,

...give me more nice templates...!!!
[JAM, MDA Compact, S100 General] Micman:
I installed as said, but it still doesn't work !

Do I need to soft reset ?

Put it in MyDocuments\Templates

Thanks for your help
[JAM, MDA Compact, S100 General] spin_x:
Micman, u wan to install the pit tool v2 or lourd.pit template.. if install u just need to run the pit tool.exe file cos it's pc application .. no need to install ..for the lourd.pit.. u juz need to copy n paste the file in the \my documents\templates.. that's it
[JAM, MDA Compact, S100 General] dalewinterstein:
K call be stupid but..... I cant install this thing.

I copied the .pit file to the /my documents/template and nothing. Do I have to rename the file, OR specify it in a program. I tred resetting and still nothing
[JAM, MDA Compact, S100 General] Micman:
Same for me !
[JAM, MDA Compact, S100 General] ajong:
go to Caller ID/Photo Contact application ....Tap & Hold... your one of contact ...tap Assign Photo ...in Display Setting.. choose template : lourd

test with Preview ...

HTH
[JAM, MDA Compact, S100 General] Micman:
I am sorry but I must be really stupid, even though i pretend to know this JAM pretty good.

But if you do that , you can only choose between a JPEG, BMP or GIF File an not a pit file. As well as if you change that , the only thing that happens is that it changes the internal view of the PIT an not the PIT.

Anyone else has an idea ?

Sorry for bothering.
[JAM, MDA Compact, S100 General] admisi:
Dont worry, had the same problem myself.

The trick is - you have to assign a photo first, then the rest of the options come up including the template which you can change to lourd. The same applies to the default pictures, choose any jpeg, and all the options will come up. Really badly designed app is Phot Contacts.
[JAM, MDA Compact, S100 General] dalewinterstein:
Got it,

Thanks for taking the time to explain dude
[JAM, MDA Compact, S100 General] Micman:
OK, works now for 1 contact.

Do I have to do that with every contact ???

Thanks for your help man
[Nexus 4 Q&A, Help & Troubleshooting] Galaxo60:
Just as the title says, does anyone know any mod or guide to make those 2 transparent on Android 4.3(JS)?.

I have tried some here on Nexus 4 forums, but they always make bootloop for me.

This is my currently ROM:

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

Thanks.

:fingers-crossed:
[Nexus 4 Q&A, Help & Troubleshooting] Good Guy Mark:
With my experience slim ROM is able go make them transparent and PA might be able to make them transparent too

Sent from my SGP311
[Nexus 4 Q&A, Help & Troubleshooting] Galaxo60:
Thanks for the answer, but I'm trying to get these particular mods for the ROM I already have, because 4.3 is not perfectly stable right now on 4.3 and these ROM's have many features I don't really need.

;)
[T-Mobile Samsung Galaxy S 4] samomamo:
Hi does anyone have a problem with proximity sensor of the Galaxy s4? I noticed after owning the phone for 2 months and flashing lots of Rom's now the proximity Sensor is not working no matter what Rom I install. When I make a call the screen turns off and doesn't come on until I press the home button. And some apps that use the proximity Sensor don't work. So I called t-Mobile and they are sending me a new

Sent from my
[T-Mobile Samsung Galaxy S 4] ed20932:
Hi..I had the same problem..but mine started after 3 weeks..Never flashed a rom just rooted..I took it and they just game me another phone..you might have a defective phone..but if you're gonna take it back I suggest you flash it to stock and use Triangle away app. This one I had I flashed custom rom 2x..had it for 2months..No problems:good:
[T-Mobile Samsung Galaxy S 4] numb3r5z:
what things use a proximity sensor? never heard of it:eek:
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
You using an Otterbox? I only ask because it can cause headaches with the proximity sensor, but it's an easy fix.
[T-Mobile Samsung Galaxy S 4] samomamo:
No the phone is naked

Sent from my phone
[T-Mobile Samsung Galaxy S 4] samomamo:
Bump
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
I got another one; are you using a screen protector at all?
[T-Mobile Samsung Galaxy S 4] Skipjacks:
I'm starting to be pretty sure the S4 got shipped with a bad batch of proximity sensors.

Mine has suddenly failed as well with no case or screen protector or any of that kind of thing involved.

Same story as everyone else who has this problem. The sensor reads as though it's being covered 100% of the time, so as soon as the phone.apk is initated and looks for the sensor value, it says the sensor is covered and blacks out the phone. Nothing brings the screen back on until the call ends.

I searched around Google and found quite a few message boards with various people describing the same exact problem.

I have tried various things to fix it.

I have cleaned the glass thoroughly to no avail.

I have tried the sensor recalibration from this thread . But that did nothing.

I installed this app from the Play store. That was very interesting because it tells me how long it has been since the sensor was last uncovered, and that value grows indefinately as long as the app is on. Meaning the sensor never reads as uncovered.

I even tried to mask the problem by getting apps that are supposed to keep the screen on during calls but they also fail.

I'm going to Odin back to stock tonight and see if that helps, but I think I've got hardware failure. Mainly because this started to go downhill over a couple weeks where the screen off during calls slowly started to work worse and worse until now when it just totally locks me out.

If I have to get this phone replaced and they send me a refurbished one I'm going to be super pissed. I had to do that with a MyTouch4G with T Mobile and that was an absolute nightmare. Every replacement phoen they sent me had a different defect, and then they had the freakin' nerve to try to charge me $10 each time they sent me a refurbished phone. So I had what was basically a defective brand new phone that was 2 months old that they wanted me to pay $60 more to be replaced with a used phone.
[T-Mobile Samsung Galaxy S 4] samomamo:
Well I called T-Mobile they send me a new GS4 and it works perfect
[T-Mobile Samsung Galaxy S 4] Skipjacks:
O

Yeah I just called about mine too and they are sending a new one.

Just kind of annoys me that I spent full price on a new phone 2 months ago and now I will have a refurbished one despite paying full price. Especially since this is the second time this has happened with a new phone from them.

Does yours seem and look like new?
[T-Mobile Samsung Galaxy S 4] mnasledov:
That sucks! Did they really send you a refurb? When my wife broke her screen and we went through insurance, we got a brand new one which amazed me -- it means we got an extra battery sand stuff.

I'm having the SAME problem with my M919 now. I thought I was going crazy over the last week being unable to hang up calls (can't get the screen on!) or dial codes mid-call.

I ended up recalibrating the sensor by doing this procedure directly on the sysfs stuff: http://xdaforums.com/showthread.php?t=2045569&page=2

It works now but I see now why it failed initially -- there's a TON of dust under the glass right over the proximity sensor! Needless to say, I am getting it replaced under warranty because that's just not cool at all. I've had this one for 2 months, tops.

It was weird, CPU-Z was showing the sensor as dead but when I was reading the state over sysfs it seemed to actually be doing something, indicating to me the calibration was way off.

Well, at least I don't have to be bothered with the sensor problem for now as I wait for my (BACKORDERED!) RMA...

EDIT: Oh and it's doing somethng fun. I flashed a nightly a few days ago and it wouldn't boot until I later decided to reflash + wipe cache. OK, that was weird because no one else had to. Well, earlier I turned it off and when I turned it back on, same deal! Had to go into recovery and wipe cache.

I'm starting to get disappointed with the build quality on both the S3 and S4. My (retired) S3 has the most "fun" problem -- its eMMC likes to get corrupted periodically. It doesn't manifest as problems while running (no file corruption that I can tell), but if I ever have to Restore Backup, it usually fails and then I have to not only fsck it in recovery mode but usually do some other tricks like remove the duplicate lost+found inode and use the alternate superblock with fsck (fsck -b 32768).
[T-Mobile Samsung Galaxy S 4] lucksp:
i have had a replacement device now for about 2 months. the proximity sensor worked for about 2 weeks before failing again. There is clearly an issue. i am going to try a 3rd device or ask for a different device entirely.
[T-Mobile Samsung Galaxy S 4] bobolinko:
Just as a test, do this:

using the stock dialer, enter *#0*#

then when the menu pops up, hit "Sensor" square.

then place your palm with an open hand about 2.5 inches away from the top right front area where the sensor is located. Yhe upper area of the screen should turn green, and also should vibrate.

if that test passes, then the sensor is not the problem.
[T-Mobile Samsung Galaxy S 4] Skipjacks:
I've seen a lot of places that indicate the proximiy sensor is prone to failing due to dust build up. This is often be solved by using compressed air shot into the speaker grill on the front to un-foul the sensor.

It might not save every phone with a failing sensor, but it can't hurt to try and I've seen a couple people say it was an instant cure.

I don't think you evne have to be able to see the dust for it to cause fouling. Just a spec or two can mess it all up. But the compressed air cleans it right out.
[T-Mobile Samsung Galaxy S 4] 0ptimus82:
Check if fast dormancy is enabled

I had the same problem after installing Crash ROM v13, my phone was working fine with JB 4.2.2, the only thing I changed after flashing the new rom was "fast dormancy", after trying different configurations what I did was to toggle back fast dormancy to enabled and now my screen and proximity sensor works perfectly fine.

It also could be related with the kernel, I'm using Perseus Kernel, I was using Adam Kernel previously.
[T-Mobile Samsung Galaxy S 4] duka25:
proximity sensor fix

I had same problem and i fix The problem in both of my s4 .buy the air spray and spray in earplug for about 20 sec .and try it will work
[T-Mobile Samsung Galaxy S 4] gypsy 1O1:
I'm having the same issue, did this test and it turns green and vibrate but never turns off when I remove my hand....I've been checking around and people have said it is an issue with dirt/lint getting through the speaker grate and gathering on top of the sensor. I tried some compressed air and it resolved the issue for a short time. Seems like the only real fix would be to pull the screen and add something to block the opening between the sensor area and the speaker grate.