yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] nickp27:
I am on MK9 4.3 with root and knox 0x0

Several posts:

http://xdaforums.com/showpost.php?p=50894257&postcount=3840

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

http://xdaforums.com/showpost.php?p=50452568&postcount=1635

suggest it is possible to upgrade to 4.4 and keep root and knox 0x0 using mobile odin but I haven't been able to find any posts where this has been confirmed for the i9505.

My understanding is that if I have the NB8/9 rom and NB8/9 bootloader files separated I could perform this. Does anyone have these or has been able to do this successfully?
[Galaxy S 4 Themes and Apps] Jose0726:
I manage to get these of the GS5 Dump files. Enjoy! (Its a rar. pack) :highfive:

DOWNLOAD GS5 WALLPAPERS:good::cool:

​
[Galaxy S 4 Themes and Apps] TheLegend90:
Those are pretty sick actually
[Galaxy S 4 Themes and Apps] Jose0726:
They actually are :)
[Galaxy S 4 Themes and Apps] TheLegend90:
Don't see that from stock very often

Sent from my Bean§talked Galaxy 4
[Galaxy S 4 Themes and Apps] avi.laza:
:D:D:D +1
[Xperia Z1 Q&A, Help & Troubleshooting] jfireman:
Hi, I just encountered a weird thing today, the majority of photos I took using my Xperia Z1 are gone. I set the camera to store the photos in external card ever since I bought my phone .

Most of the photos stored in DCIM folder in my external card is now gone. This is just annoying. Luckily I just performed a full backup a few days ago and enabled Google+ photo auto backup, however some photos haven't been backed up yet.

Did anyone encounter this kind of problem too? And does anyone know how to fix this or where the source of the problem is? FYI, my Z1 is has been updated to KitKat.
[Xperia Z1 Q&A, Help & Troubleshooting] xXFlippyXx:
are just the photos gone or is your card completely empty?
[Xperia Z1 Q&A, Help & Troubleshooting] harfot:
As I suppose you are able to see your pictures if you read the card from a PC, you're suffering from the new Google Android KitKat security "feature" that prevents app from writing freely to the SD card which you can read a lot more of in the thread, Reverting KitKat SD card changes.
[Xperia Z1 Q&A, Help & Troubleshooting] jfireman:
Not completely empty, most of the photos are just gone. Other files like videos I stored are still there.
[Xperia Z1 Q&A, Help & Troubleshooting] jfireman:
Nope, I can't see the picture even if I insert it to my laptop's SD card slot. I checked the used storage space of my SD card and found out that it now has way more free storage space than before.

I manage to recover my photos by using a recovery app but I really hope this doesn't happened again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
I found out that the phone had 4.1.1 on it and the guy tried to flash 4.2.2 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....

Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization

Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment

In Kies, enter your phone model (SGH-I747)

Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies

Connect the phone when prompted and follow the rest of the instructions

Wait for firmware upgrade to complete

Good luck!

If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...

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

The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3

PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?

For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.

It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.

I am lost for now. If you guys can think of anything new let me know and thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
You didn't mention if you tried the Kies option. I had a similar problem once when upgrade to 4.1.1 via Kies failed during the process and that was how I was able to recover. However, since you bought this from the secondary market, there is no way of telling for certain what the previous owner did wrong which would have been useful for recovery options.

One of the nice things about Odin is that you usually know the results immediately. If it says Pass, therefore, that's likely what it means. So Odin did flash something. But what did it flash? The counter you saw in download mode shows how many custom system installations there have been and 6 does show there has been some previous heavy tinkering with the phone. As you are still able to get into download modes, I would suggest you try flashing custom recovery (TWRP or CWM) via Odin. If this works and you are able to get into recovery mode, you may then try doing a hard wipe/reset via recovery. You may also try flashing the other (rooted) 4.1.1 file via Odin. At this stage, you really have nothing to lose in trying all options. I guess if you can get into recovery mode, the problem is almost solved as this leaves plenty of options.

A jig wouldn't help as that only gets you to download mode which, for now, you don't have a problem with. JTag should always be a last resort option only. Let me know how far it goes and good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
This damn phone is starting to annoy me. I can still get into download mode but my phone gets usb device not recognized now. I have access to another I747 phone so my question is if I have access to the pit file from that phone can anything be done with the Debrick utility and a SD card with only download mode access? Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Go into download and let us know what is shown on the screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
Odin Mode

Product Name: SGH-I747

Custom Binary Downloads: Yes (6 Counts)

Current Binary: Samsung Official

System Status: Official

Qualcomm Secure Boot: Enable

Green Android Icon Downloading...

Do not turn off target!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
OK I plugged the USB in and out a few times and it allows to write every few tries. Back to my question can I do something in download mode if I have another i747 that I can copy stuff from? I also tried the suggestion to uncheck auto-reset pull the usb cable then the battery and try to go to recovery but it doesn't.Any suggestions are welcomed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
I will try it again I think I already did but when I put the battery back and click the Vol+ Home Power I get the blue writing and then black screen. Should I wait like 10 min on the black screen or it should be quick. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theUsualSuspexx:
If u can get it into download mode u are never ever hard bricked my friend...take it from a guy who had to dust off his old galaxy sll last weekend & still can't get into d/l mode on my s3 after a week & even with a jig lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.

Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gica69:
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
I couldn't find one either although you may be able to create yours using the command line posted in the thread below ...

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

You may also try using a jig to get back into download mode. Have you, however, considered exercising any buyer protection options you have on the phone since, it would appear, the guy sold you a lemon?
[Sony Xperia ZL] Oswaldo212:
Good day everyone!

I was wondering if it's possible to change the framerate of our Xperia ZL to record video at 24fps.

I used to own an Xperia Mini Pro and what i did was to edit the media_profiles.xml file located on system/etc

but when i tried that on my ZL it did't work i got an error message that said "Camera not available"

I also tried using some apps like Camerapro and LG camera from the market but that didn't work either.

Does anybody know a way to modify the frame rate to record video at 24fps? or about an app that can do this?

Thanks a lot!
[Sony Xperia ZL] danieldp1990:
why would you like to lower the framrate of the videos? O.o
[Sony Xperia ZL] Oswaldo212:
I would like to have the option. It gives the video a movie like effect 'cause movies are filmed with that frame rate ;)
[Sony Xperia ZL] detective zero:
You won't see the difference between 24 and 25. 24 is just helpful if you want to combine your footage with other material in a 24 fps editing project in your editing software.
[Moto G Q&A, Help & Troubleshooting] rohit_soni:
Recently I bought Moto -G. It came with 4.4.2 Android Kitkat update. I am facing some serious issues with my phone.

Whenever network is not there than my SIM slot 1 automatically gets disable and to again enable it have to remove the

SIM from slot -1 and again reinsert it than it starts working.:crying: The same is happening with my friend also who is having MOTO-G.

Can you please tell me how to get rid of this problem ?
[AT&T Samsung Galaxy S 4 Themes and Apps] Jose0726:
I manage to get these of the GS5 Dump files. Enjoy! (Its a rar. pack) :highfive:

DOWNLOAD GS5 WALLPAPERS:good::cool:

​
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cagliostro:
Hello everybody

Yesterday I tried to use "lokiwiz - HTC Wizard Unlocker v0.2b" for my new T-mobile MDA Vario because otherwise I was not able to upgrade the ROM from 1.6.2.2 to the latest one. But.. in the end I got a problem. To be honest this problem was appearing periodically before unlocking/upgrading but now it presents permanently. I simply can not dial any phone number. The systems responds as: "SIM card is not installed or invalid" (something like that from translation from Dutch into English, originally: "SIM-kaart ontbreekt of ongeldig").

I already tried to use this SIM in my previous phone (SE T630) and it still works perfectly. I can dial numbers, I can SMS, whatever. But in my new T-mobile MDA Vario this SIM card just does not admit dialing the phone numbers.

Does anybody have any thoughts, what it might be?

Thank you very much in advance!!!

P.S. Honestly, in case of warranty during unlocking process I kept my SIM card out off the MDA.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cagliostro:
Just for info...

When I bought MDA the version of ROM was 1.6.2.2 NLD

After upgrading I got ROM 2.21.2.5 NLD and ExtROM 2.21.2.108

As I see now it connected to T-mobile network but still can't dial any number, reporting of the possible problems with SIM card. In the same time this SIM card is working with no any problems in my T630.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Koksie:
This is a very strange problem indeed. When you turn your device on or soft reset, does the device ask for a PIN code for the phone? If it asks for a PIN code and it accepts that code and starts searching for a signal, that means that the device can read the SIM card. It is very strange that when you have a signal, the device cannot make call. Either it should not be able to compare your PIN code to the one on your SIM and give an error message, or if it accepts your PIN code, you should be able to make calls. Perhaps there is a hardware problem with your SIM slot that makes the device unable to read the info on your card? Since it works in your other phone, the SIM does not seem to be the problem. You can try flashing another ROM on it to test if the device works with that ROM. If that does not work as well, flash back to an original T-Mobile NL ROM and call T-Mobile for your warranty.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cagliostro:
When it is loaded it shows up the Telefoon screen with the following message: "Ongeldige of ontbrekende SIM-kaart. U kunt nog wel alarmnummers bellen, als uw seviceprovider dit ondersteunt." If I type numbers it show stars, like I would enter the password. Why stars? I already tried to input my unlocking code but it didn't help, as looks like it expects something else that this. I may just press Annuleren and continue working with other available functions of MDA but still may not use the phone.

Could you please share the info how to downgrade back to 1.6 ROM?

Thank you very much for your response!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Koksie:
Ok, this indicates that your device cannot read your SIM card. The screen you get on start-up is the screen where you normally enter your PIN code, if the device can read your SIM Card. That is why you see only stars when you enter a number there. Seems to me that your device cannot read your SIM Card and therefore cannot compare the PIN you enter to the one on your SIM card. You should not be able to get a signal from T-Mobile, since your phone cannot read the SIM and cannot register with the network. This can be caused by three problems: either your SIM card slot is broken, or your ROM is faulty (try flashing it to another ROm first, for instance a Qtek ROM from the ftp server, there are many ROMs available there) or the SIM card is defective ( seems not to be the case here, since it still works in your other phone).

I recommend that you first try another ROM on your phone, e.g. a Qtek ROM. If the problem goes away then, just keep the Qtek ROM or try flashing the T-Mobile ROM again. If that does not help, flash the latest T-Mobile ROM (from their website) to your device and claim your warranty for a broken sim slot.

As far as I know it is not possible to downgrade to the 1.6 ROM, it is a non-AKU ROM and cannot override an AKU ROM. Perhaps someone can correct me, since I am not a 100% sure of this. You do not need the 1.6 ROM at all, if the Qtek ROM does not work, just flash the latest T-Mobile ROM to your device and claim warranty. Since you then have an official T-Mobile ROM on your device, warranty should not be a problem.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cagliostro:
Would be that a problem to flash latest T-mobile upgrade back from Qtek? I need to know it just in case I would not be able to do that. Cause otherwise, sorry, but im ****ed up in front of warranty office..
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Koksie:
It should not be a problem to flash the T-Mobile ROM over a Qtek ROM. You can first try a hard-reset to see if that solves your problem. You can also call T-Mobile Klantenservice and tell them your problem. Tell them you want to use a Qtek ROm to figure out the problem and ask them permission to do so. They are known to give permission for such actions if that can save them from repairing your device. Be sure they make a note in your file stating that they give you permission, that makes your case stronger if there is a problem with your warranty later on. Good luck!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cagliostro:
Do you think it's illegal installing even T-mobile NL ROM updates by myself, i.e. not asking T-mobile to do so?

Like I said the previous version of my ROM was 1.6.2.2. Then I actually tried to flash the latest UK version (2.21.2.5). The network signal was actually appearing from time-to-time but then it just died. Then I tried to install the latest NL version (2.21.2.5NLD) to check whether the signal would appear. But it didn't help.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Koksie:
Installing official T-Mobile updates is not illegal. T-Mobile NL made the upgrade available on their site. These updates are meant to be carried out by the users themselves, therefore the file and instructions are placed on their site. For other brands ( Nokia, SE) these updates cannot be done by the users themselves, but Windows Mobile updates are meant to be done by you, thereby saving T-Mobile the costs of performing the upgrades for you. So if an official T-Mobile ROM is on your device, they can never deny you your warranty. You can try to replace the radio Rom only (there is a thread on this) to see if that helps, but I recommend flashing an official T-Mobile NL ROM on your device and claim your warranty. Since you have tried different ROMs, the problem obviously resides in the hardware. If a hard-reset does not help, use the lokiwiz application to sim and cid lock your device again and T-Mobile will not be able to see that you had unlocked it. Just mention that you tried a hard reset and that you tried upgrading to the latest official T-Mobile ROM and they will have to honour your warranty.