Related
Dear xda'er from the USA: To the disappointment of some in this forum, the xda-team has decided to split the sections on the Samsung Galaxy S i9000 and its US-counterparts into SEPARATE sections! You will be able to get some help here but you will likely be better helped/supported/suited in the forums that belong to your specific device!
Note: Many of the FAQs may still apply to you and you are welcome to make use of our setup. However, if you have open questions I suggest directing them to the above mentioned forums.
IP-Notice: You are welcome to use the information in this thread! If you do, please link the original source.
I try to give credit where due. If you feel I am using your content without your authorization or proper credits, please contact me!
General Note: There are now four official models of the Samsung Galaxy S outside the US: the GT-I9000 (International), GT-I9000M (Canada), GT-I9000B (Brazil), GT-I9000T (Mexico). All information in this FAQ is based on the GT-I9000 International version. Most of them also apply to the other models. The I9000M and I9000T are virtually identical to the I9000 and are mostly compatible with I9000 software. The I9000B has an added digital television receiver and is generally not as compatible. Please check carefully before starting to mess with the firmware on your device, check for possible compatibility issues beforehand and ALWAYS make sure you have three button recovery (see FAQ#A12)
Note: The I9000B has a separate FAQ
Note2: For the Korean Galaxy S SHW-M110S, please see this separate FAQ
Disclaimer: This FAQ is provided as-is without any warranties to completeness/correctness. I will take no responsibility if you break/brick/damage your phone.
Contents:
Post#1: Frequently Asked Questions
Post#2: HOWTO Section
Post#3: ADB Tutorial
Post#4: Tutorials and Fixes
Post#5: Tips & Tricks
Post#6: Firmware Selection Guide
FAQ Sections:
A. General
B. Firmware
C. Modding
D. Applications
E. Recovery
(A) General:
1.How can I reset my phone?
2.I have flashed a new firmware and now my phone won't connect to 3G. What's wrong?
3.Can I disable 2G broadband like on the Desire/N1?
4.I flashed a new firmware and now I cannot download protected apps and Market-enabler doesn't work. How can I still install protected apps?
5.My phone takes forever to get a GPS-fix? Is there a solution to this problem?
6.I am experiencing long loading times when opening apps/intermittent lags when switching screens. What is the problem?
7.My G-sensor seems to be off. How can I calibrate it?
8.I have a SIM-Locked phone. Is there anything I need to look out for?
9.When will Ice Cream Sandwich be released for my shiny new phone?
10.I'm running Linux. Can I still flash my firmware? Do I need to install Windows?
11.Most phones have a bunch of codes that can be entered in the dialer for special functions. What are they on the SGS?
12.My phone cannot enter download mode or recovery mode using the buttons combos. What can I do?
13.I live in Canada/Mexico (The Americas in general). Can I get my phone to use the 850Mhz bands with I9000 Modems?
1.How can I reset my phone?
On the Galaxy S the soft-reset is achieved by pressing and holding the power button. A hard-reset can executed by pressing and holding VolumeUP+Home+Power. There you will find the options "reboot", "apply sdcard:update.zip", "wipe data/factory reset" and "wipe cache partition". (Note: The list of options can vary considerably after installing modified firmware/kernels)
The "wipe data/factory reset" option will restore your phone to the original configuration of the firmware YOU LAST INSTALLED (including any updates made via update.zip). This will NOT bring your phone back to the firmware installed when you originally bought it unless you haven't flashed your phone.
You can navigate the recovery screen using VolumeUp & VolumeDown and use the Home button to select.
2.I have flashed a new firmware and now my phone won't connect to 3G. What's wrong?
The CSC you used is most likely not intended for your area. This means that the broadband provider settings are not included and need to be configured manually. To do this, go to Settings->Wireless and Networks->Mobile Networks->Access Point Names, press the settings-button and select "New APN". You will then need to enter the respective data as provided by you mobile operator. APN settings can usually be found on the operators website.
3.Can I disable 2G broadband like on the Desire/N1?
As of firmware XWJM1 (July 2010), this function is available in the wireless settings. All current firmwares now have this feature.
4.I flashed a new firmware and now I cannot download protected apps and Market-enabler doesn't work. How can I still install protected apps?
This is done by google to protect commercial applications from piracy. This usually only happens on internal beta firmwares. Use Eris Market Fix from the Market or the tutorial in P#4,T#1. Both fixes require root privileges (See FAQ#C1)
5.My phone takes forever to get a GPS-fix? Is there a solution to this problem?
It appears that the XWJM1 and XWJM2 firmwares have mostly fixed the major GPS issues and the general consensus is that these firmwares deliver consistently better GPS results than previous firmwares. The usability, however, still varies per location and sometimes the software gets no fix despite seeing plenty of satellites.
To date, there appear to be no better fixes available. There are still many reports that GPS is flaky and it appears as if Samsung is no longer working on improvements in this area.
6.I am experiencing long loading times when opening apps/intermittent lags when switching screens. What is the problem?
The Samsung Galaxy S uses the internal SD to store cache data by default. This storage uses the severely outdated RFS (FAT-related) filesystem. Next the to poor performance in a good state, RFS appears to rapidly manifest massive amounts of filesystem errors which cause the experience on the SGS to degrade over time.
Currently almost all custom kernels fix the problem by replacing the RFS filesystem with ext4 on (virtually) all partitions (some do not touch the /efs partition). Original credit for the discovery that the filesystem was the problem belongs to mimocan and the fix has since been refined by RyanZA, z4ziggy, sztupy and most notably supercurio.
7.My G-sensor seems to be off. How can I calibrate it?
The G-sensor calibration appears to be off in a lot of shipped devices. Current firmwares can calibrate the accelerometer in the Display menu.
8.I have a SIM-Locked phone. Is there anything I need to look out for?
As of now there are several reports of successfully flashed SIM-locked phones and no reports of any (related) problems.
This means that as of now (there seem) to be no specific restrictions for SIM-locked phone except the lock itself. However, the lock on the Galaxy S can be easily removed. Please refer to T&T#20 for unlocking your phone.
9.When will Ice Cream Sandwich be released for my shiny new phone?
At the moment, there are no indications that Samsung will release a fully featured Android 4.0 firmware for the Galaxy S. They are, however, porting several ICS features to Android 2.3. While this is very disappointing, there are several ICS ports based (in part) on the sources for the Nexus S available already which will probably result in a relatively stable build in the long term.
10.I'm running Linux/OSX. Can I still flash my firmware? Do I need to install windows?
If you are running Linux or OSX you do not need to install Windows. You can either run Odin in a virtual machine or alternatively use Heimdall by Benjamin Dobell. Heimdall runs natively on Linux and OSX and has reached a well tested release state.
11.Most phones have a bunch of codes that can be entered in the dialer for special functions. What are they on the SGS?
There is a list of "secret codes" here. There are also several apps in the market with these features in the market.
12.My phone cannot enter download mode or recovery mode using the buttons combos. What can I do?
Some batches in various countries seem to not have this feature. However, Samsung Canada has released a fix via Kies (for the I9000M) and it has been adopted to suit a larger audience (I9000 and I9000M). Instructions on how to update your phone to get the three-button-combo can be found here or here. Note: Follow the instructions in that post CAREFULLY and read it completely BEFORE attempting to do anything on your phone. If done improperly, this can still brick your device!!!
13.I live in Canada/Mexico (The Americas in general). Can I get my phone to use the 850Mhz bands with I9000 Modems?
Users in the Americas will find that the I9000 modems use the 900Mhz band which is not used in the Americas. However, since the I9000 is virtually hardware-identical to the I9000M and others which do use the 850Mhz band, the band can enabled on the I9000 modems. There is a guide here.
(B) Firmware:
1.What is a ROM/firmware?
2.Can I update my firmware?
3.Why are there sometimes multiple files in the firmware archive/folder?/Why do I get three different versions when using *#1234#?
4.Can I mix PDA/Modem/CSC files from different firmwares without bricking my phone?
5.My phones software version says I9000XXJF3/XXJF5/xxxxx. What does this mean?
6.I want to install new firmware but I want to have a backup of my original firmware to go back to in case I need to go back for warranty reasons. Can I backup my original firmware somehow?
7.Can I flash an Asian ROM on my European device or vice versa?
8.What is the .pit file? Why are there different versions?
9.I flashed a new firmware using Odin (or Kies) and now my phone is acting weird (force closes etc)? Also, my settings are also still there.
1.What is a ROM/firmware?
The firmware/ROM is the software that runs on the phone. In case of the Galaxy S this is (currently) Android 2.3.5 Gingerbread. The Galaxy S was initially released with Android 2.1 Eclair and will most likely not receive any major firmware upgrades anymore. Samsung is porting several features from newer Android versions but has refused to bring a fully-featured Android 4.0 release on the grounds that the TouchWiz UI together with ICS would be to big for the normal system partition.
2.Can I update my firmware?
Most likely: Yes. You can update your firmware through Samsungs official application (Kies) and with firmwares that have been leaked or otherwise been obtained for installation without using the Samsung Kies software. You can find firmwares made by Samsung for phones all over the world, here. You will also find a guide to the installation in HOWTO#1 in the second post of this thread.
Note: Please also keep in mind that not all firmwares that come with phones are available. Reflashing to stock may not be possible because the specific firmware isn't available!
3.Why are there sometimes multiple files in the firmware archive/folder?/Why do I get three different versions when using *#1234#?
Galaxy S firmware updates come in three parts (which are sometimes packaged as one file):
-The CODE itself (called PDA). This is android and all the applications that come with it. (The archives/folders will be named after the version of this file)
-The MODEM (called Phone). This is the firmware of the wireless chipset of the device and will operate you WiFi, Blutooth and 3G/2G/GSM connections. (ie Radio ROM)
-The CSC (short for Customer Specific Customization). This includes connection data for the broadband networks as well as apps that are only available in certain languages/intended for a specific area.
If we ask for your firmware, we want to know all three!
Since not all of these require updates simultaneously, often then CSC and MODEM files will have lower version numbers.
(Also when packaged in one file the repartition option should NEVER be checked in Odin because it will mess up your partition layout and will require a reflash with three-part firmware!)
Most firmwares that are currently available are no longer split up into the three parts and instead delivered as one which can be flashed by entering it as the PDA/CODE in Odin.
4.Can I mix PDA/Modem/CSC files from different firmwares without bricking my phone?
Yes. Most Modem/CSC files will work with any PDA. However, there may be compatibility issues which may force you to reflash your phone. Note also that newer CSCs usually include newer versions of the software that comes with them (Some of which may not be upgradable via the market or other means).
5.My phones software version says I9000XXJF3/XXJF5/xxxxx. What does this mean?
The first two letters describe the country while the third gives the year, the fourth gives the month and the last number/letter is the version of the firmware (from that specific month. Numbering starts at 1-9 and then uses letters from A-Z). For an extensive list of the country codes, see this thread.
Note: To better distinguish the firmware releases based on a new Android version (2.1 vs 2.2 vs 2.3 etc), Samsung has shifted the use of the third and forth letter and these are now no longer coherent with the year and month according to Samsung's old system.
6.I want to install new firmware but I want to have a backup of my original firmware to go back to in case I need to go back for warranty reasons. Can I backup my original firmware somehow?
You can backup most of your firmware through Clockwork Recovery, however, since this already requires root it is not suitable for a warranty return. Nevertheless virtually all firmwares that are currently being shipped with the phone are available and thus a restoration is almost always possible.
7.Can I flash an Asian ROM on my European device or vice versa?
Flashing firmwares between several areas is easily possible. Please make sure you have the correct model before flashing. The international SGS has the model I9000. The Korean version and the US variants have significantly different model numbers and firmwares for those phones should NEVER be flashed on the I9000 or vice versa.
8.What is the .pit file? Why are there different versions?
There are now three different versions of the .pit file. 513.pit, 512.pit and 803.pit. Most firmwares since the end of 2010 do not require a .pit file to be selected. Generally only the 512 version is used. The .pit file is only necessary if you intend to repartition the phone. If you do, you inadvertently wipe all your data (not the internal SDcard). Since the partitioning of the device has not changed for more than a year, repartitioning is almost never necessary unless you used a custom firmware like cyanogenmod, which changes the partition sizes.
The .pit file maps partitions on the NAND storage.
9.I flashed a new firmware using Odin (or Kies) and now my phone is acting weird (force closes etc)? Also, my settings are also still there.
Some firmwares that can be flashed via Odin and the firmwares that are flashed using Kies, do not touch your settings and they do not empty your cache and appdata partitions. As a results, there is data there from previous firmwares which may lead to unforseen complications. Especially so, if your previous firmware was based on a different android version (i.e. flashing from XWJM6(android 2.1) to XXJPC(android 2.2)). You can attempt to overcome this by wiping the cache. Usually, to resolve this, you have to do a factory reset according to FAQ#A1
(C) Modding:
1.What is root/rooting?
2.What are customROMs? How do I get them?
1.What is root/rooting?
root is the user account in Linux with all privileges. The root user can edit anything on the system. For safety reasons, users do not have all those privileges. When you root your phone, you will gain write access to areas of the phone you couldn't previously access and are allowed to run more commands in the terminal. Because applications do not get a lot of priviledges, some of them require you to root the device in order for them to function properly (or fully). There is a tutorial for rooting in the Post #2 and there is a Chainfire Root that works most firmwares. CF-Root essentially is a kernel that is flashed over the original kernel.
If all of this means nothing to you then you are probably wise to NOT root your phone. Mistakes using root can break your phone very easily. (Usually, but not always, these can be solved with a reflash)
2.What are customROMs? How do I get them?
Custom ROMs are modified versions of the Samsung firmware or complete rewrites of the Android OS for the Galaxy S such as Cyanogenmod (and the derivative MIUI). Almost all current custom ROMs are based on Android 2.3 with some now being based Android 4. They can be found in the Android Development Subforum.
(D) Applications:
1.I tried using Allshare/DLNA but it will not recognize my device/play any files?
2.Can I change the default homescreen of the Touchwiz Launcher?
1.I tried using Allshare/DLNA but it will not recognize my device/play any files?
As of now a lot of DLNA certified devices/software do not work with Allshare. However, Samsung TVs should work and Windows Media Player 12 as well as Samsung's PC Share Manager work in most cases.
2.Can I change the default homescreen of the Touchwiz Launcher?
You cannot change the default Homescreen in the settings. However, if you are rooted, there is a way to change the default homescreen. See T&T#5 for more info.
(E) Recovery:
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
Most likely: YES! In almost any case, you should still be able to turn off the device (if necessary by removing the battery) and start into download-mode (VolumeDown+Home+Power) or recovery-mode (VolumeUp+Home+Power). After (for example) an unsuccessful flash, you can retry the flash in download-mode (same steps as when flashing a functioning device). If a flash to a functioning f/w (without applying any update.zip) doesn't help or you cannot get your PC to flash at all, you can ask for help here.
If you see a symbol asking you to connect to the PC, depending on how you arrived at this point, it may be sufficient to connect to the PC and run Odin (i.e. press "start" when the phone is recognized) without adding any files. This may, however, leave some residual issues if (for example) had an incorrect/incomplete flash so you may want to do a normal flash after this!
If you do not have download mode and for some ludicrous reason felt the need to go ahead and modify your firmware regardless of this lacking, there is now a guide on creating a home-made JIG which will force your device into download mode without the actual button combo here. Also pre-fabricated JIG dongles can be purchased on ebay for a couple of EUR/USD.
-----------------------------------------------------------
Changelog:
[12th July] FAQ created.
[12th July] Added Flash HOWTOs in Post#2
[13th July] Added list of CustomROMs in FAQ#10
[16th July] Added notification for US phone users
[18th July] Added rooting to HOWTOs
[18th July] Added ADB tutorial in Post#2
[19th July] Moved ADB tutorial to Post#3
[19th July] Added Tutorial/Fix section in Post#4
[19th July] Added "Protected Apps Market Fix" in Post#4, Tutorial#1
[24th July] Removed SIM-Unlocked as a requirement from flash HOWTO (Post#2, HOWTO#1).
[24th July] Added Tags for categorizing the FAQ
[26th July] Added Tip&Tricks section in Post#5
[20th August] Added a ROM-Selection Guide in Post#6
[30th August] Major Rework of the FAQ section
[8th October] Added "Installing any official firmware using Kies" in Post#4, Tutorial#2
[17th October '10] Added "Extracting Samsung Phone Drivers from Kies Installer" in Post#4, Tutorial#3
[2nd March '11] Began Major Update
[5th November '11] Updated to recent release of Android 2.3 and other changes
[7th January '12] Some updates to reflect recent changes regarding software and Android 4.
[6th April '12] More updates regarding Android 4.0 and some other updates.
Flash/Update Guides
!!!READ THE GUIDES AND NOTES COMPLETELY!!!
General Note:Flashing may refer to both methods. However, Method 2 requires files to already be on the phone. Therefore if you semi-bricked your phone, method 1 is usually the preferred way to fix it.
General Note 2: Flashing firmware and/or factory resets will WIPE your APN settings. Make sure you are using the right APN if that is a possible issue with your provider.
Important General Note: Several batches of phones that were sold have the download-mode button combo disabled (VolumeDown+Home+Power or alternatively Home+Power on some phones). Check if the download-mode combo works BEFORE flashing! Please refer to FAQ#A12 and T&T#23 for a fix for the download mode if it doesn't work on your phone!
HOW TO:
1.Flash Firmware and kernels using Odin.
Note: This will in (almost) all cases erase all your data and applications (includind root!). It will NOT touch the internal or external SD card.
Requirements:
-Odin3 version 1.82 (Note: Odin should be on the system partition (the partition where windows is installed) to avoid possible issues)
-".PIT" file for the Samsung Galaxy S (See FAQ#B9 or the source of the FW for the version to use! Not needed for kernel flashes.) .PIT files are usually not necessary anymore since the partition layout of the SGS hasn't changed since the end of 2010
-USB cable
-Desired firmware package or desired kernel package
Procedure:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connecting the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (For kernel flashes, only PDA is required. For FW flashes, at least a PDA is required. Some PDAs have Modem and CSC integrated. If you decide to repartition, make sure you choose the right file, currently almost always the one with the ending 512.PIT)
[Optional]3.Check the "Re-Partition" checkbox. (Only do this if you have separate packages for PDA, Modem and CSC AND you have a .PIT file selected! Don't do this for single PDA flashes or kernel flashes!)
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.When the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
2.Update to CustomROMs/Mods/Root using .zip files
Note: Depending on the firmware you selected, this may or may not wipe your applications and the respective data. In any case, it will not touch your internal and external SDcards!
Requirements:
-ADB (from the Android Software Development Kit) -- Optional
-CustomROM File
-USB-cable
-2e recovery, Clockwork recovery (can be installed using HOWTO#1 and an appropriate kernel) (Note: 3e recovery will not allow the installation of .zip files that aren't signed by Samsung and is as such not usable for this procedure)
There are two methods for applying the update. Procedure A requires some basics in using a terminal (and ADB). Procedure B can be carried out by anybody but usually isn't available if the bootloader does not have download mode. See FAQ#A12 for more information on download mode using the button combo.
Note: The recovery screen can be navigated using the Volume Up and Volume Down Buttons (Up and Down) and the Home Button (To Select)
Procedure A: (Requires ADB)
1.Copy the CustomROM/root file to the "/sdcard/" folder on the phone and (if not already the case) rename to "update.zip"
2.On the phone go to Settings->Applications->Development and check "USB debugging"
3.Extract the Android SDK and navigate to the /tools/ subfolder of the SDK folder using cmd.exe.
4.Run "adb reboot recovery" to enter recovery mode
5.Wait for the recovery screen en select "apply: /sdcard/update.zip"
6.Wait for it to finish and reboot.
Procedure B: (Does NOT require ADB)
1.Copy the CustomROM/root file to the "/sdcard/" folder on the phone and (if not already the case) rename to "update.zip"
2.Restart in Recovery Mode by pressing an holding VolumeUP+Home+Power.
3.Wait for the recovery screen en select "apply: /sdcard/update.zip"
4.Wait for it to finish and reboot.
If you encounter trouble with the ROM afterwards, enter recovery mode again and select "factory reset/wipe data/cache" and confirm before seeking help.
ADB Tutorial
ADB Tutorial
Many tutorials, fixes and mods are written assuming a basic knowledge of ADB. ADB is a command-line tool that is part of the Android Software Development Kit (a.k.a. Android SDK or ADK). This tutorial is aimed at getting you acquainted with the basic functions/workings of the ADB tool.
(Note: I do not currently use/have Linux installed. For now, this tutorial will be Windows-only. However, I suspect Linux users are versed in command-lines already and do not need a tutorial like this to open adb)
Requirements:
-Android Software Development Kit (you do not need to run "SDK Setup.exe" to use ADB!)
-Rooted Samsung Galaxy S
-Busybox (installed from market and updated!)
Basic Setup:
In order to use ADB you will first need to decompress the Android SDK. For simplicity, decompress the folder "android-sdk-windows" into the root of one of your partitions. (I am using the root folder of my D: partition for the purpose of this tutorial)
You now need to start the Windows Command-Line tool "cmd". This differs per Windows version:
XP: Go to the start menu and click "Run", type "cmd.exe" and confirm with "Run"
Windows Vista/7: Go to the start menu, type "cmd.exe" and hit enter.
You will now see a command-prompt open (I erased my username):
As stated before, my "android-sdk-windows" folder is located on my D: partition. You will now need to navigate to the "platform-tools" subfolder of the "android-sdk-windows" folder:
Before we go any further we will now have to complete some steps on our phone:
-Make sure the phone is rooted (find the application "Superuser Permission")/has the latest version of busybox installed (Run "BusyBox installer" and make sure it says, that the latest version is installed). If not, root your phone according to the HOWTO in Post#2 and install busybox from the market (and follow the instructions in the description) respectively.
-Put your phone in USB debugging mode: "Settings"->"Applications"->"Development" and check "USB debugging"
-Close all other applications on your phone and go back to the TouchWiz Launcher Home Screen
-Connect the phone to your PC
Now, we are ready to run ADB:
I hope this helps all those who were clueless so far on all the adb-based tutorials for fixes etc.
Tutorial for Market Fix
Note: This section is strictly a work in progress and new tutorials will be added when they become available and have been confirmed as working!
Content:
1.Market Protected Application Fix
2.Installing any official firmware using Kies
3.Extracting Samsung Phone Drivers from Kies Installer
4.Backing up the /efs folder
Tutorials/Fixes:
1.Market Protected Applications Fix
Background: In order to prevent the illegal copying of copyrighted applications google has integrated what are called protected apps. These applications have some copying protection which means they cannot be backup-ed without root. In order to prevent rooted/modified phones from getting those applications, google market checks the build.prop file in the /system/ folder against a verified list to see if the version of your firmware is an official release. This tutorial will show you the steps to replacing the build.prop of the firmware you installed with that of a firmware that is verifiedand accepted by google.
Note: MoDaCo's r2 and the derivatives thereof have a fix included for this in the ROM (can be found in "MCR Scripts").
NOTE: As of now, "Eris Market Fix" from the android market seems to work on the SGS. It uses a similar procedure and should achieve identical results (for now). The app itself can be uninstalled after the fix is working.
Requirements:
-Rooted Samsung Galaxy S
-ADB (from the Android Software Development Kit)
-build.prop from a recognized official firmware
Procedure:
1.Download and extract "build.prop".
2.Copy the "build.prop" to the root of your internal SD card (to the folder "/sdcard")
3.Make sure the phone is rooted (find the application "Superuser Permission")/has the latest version of busybox installed (Run "BusyBox installer" and make sure it says, that the latest version is installed). If not, root your phone according to the HOWTO in Post#2 and install busybox from the market (and follow the instructions in the description) respectively.
4.Run the following commands in ADB (for a tutorial on ADB, see Post#3):
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
busybox mv /sdcard/build.prop /system/build.prop
reboot
5.Wait for the phone to reboot. Check if can see protected apps (for example the paid version of tapatalk)
6.If you cannot see protected apps, you may have to wait a while in order for market to recheck the build.prop. This process can be helped bu setting the system time (manually) to 23:59 (i.e. 11:59PM) and wait for it to pass the 0:00 (i.e. 12:00AM) mark. Then return the time to the correct time setting and reboot. (You may still need to wait a few minutes before you can actually see protected applications)
7.If you still can't see protected applications, restart in recovery mode ("Volume Up"+"Home"+"Start") and wipe the cache of your phone. (You may still need to wait a few minutes before you can actually see protected applications)
For the interested, here a explanation of the code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount is the linux routine to mount a device to a specific path
-o will allow you to issue several commands to the mount routine, separated by commas
remount will unmount and then mount the filesystem again
rw will cause the filesystem to be mounted with read/write permissions
-t is the parameter used to define the filesystem
yaffs2 is "yet another flash file system 2"
/dev/block/mtdblock3 is the hardware-location of the system path
/system is the path to which you want to remount the hardware location
busybox mv /sdcard/build.prop /system/build.prop
busybox causes the following commands to be executed by busybox instead of default android
mv moves files from one location to another
/sdcard/build.prop is the path to the file that is being moved
/system/build.prop is the path where the file gets moved to
2.Installing any official firmware using Kies
Background: In August 2010 Samsung started (if only scarcely) to release official and test updates for the i9000 firmware. Since many users have flashed different firmware and the ways of backing up original product codes were not know at the time, most people who flashed their phones do not have the original settings from their country and/or provider and can thus not get the official updates for their area. Forthermore, some updates were only released in one or a few areas and people outside those areas wanted access. Consequently, Zangieff figured out a way to fake the phone information for Kies in order for it to find and install updates from a specific area. This is a slightly adapted version of his fix.
NOTE: There have been no firmware releases for some areas and providers through Kies. This fix is only able to upgrade to versions that have actually been released on Kies.
Requirements:
-Samsung Galaxy S
-Samsung Kies
-Basic knowledge of regedit
Procedure:
1.Run Kies, connect the phone and make sure it is properly recognized.
1.1.If you have never before opened the firmware upgrade widget with your phone connected before, open it now and then close it again (Do NOT close Kies!)
1.2.Optional: (Only do this if you are looking for experimental updates!)
1.2a. Open the firmware upgrade widget in Kies
1.2b. Press Ctrl+Alt+U+P simultaneously. Kies will confirm the correct sequence with "Test Mode is ON".
1.2c. Close the firmware upgrade widget of Kies
2.Run regedit (Start-->Run...-->Type "regedit"-->Press Ok) (Windows XP)/(Start-->Type "regedit"-->Press Enter) (Windows Vista/7)
3.Use regedit to navigate to "HKEY_CURRENT_USER/Software/Samsung/Kies/DeviceDB/". You will find a number of folders in numerical order (usually) starting from 1. Find the folder with the relevant keys (see below) and make sure it is the one currently in use. [If you find several folders with the keys and don't know which are the right ones, delete all of them, repeat step 1 and 1.1 and find the folder with the lowest value. (You may have to use F5 or View--->Refresh to get to see the new folders)]
4.Find the registry keys "HIDSWVER" and "ProductCode"
5.Replace them with the appropriate keys as needed for your desired upgrade.
6.Open the upgrade widget in Kies and enjoy updating.
To find the appropriate values for HIDSWVER and ProductCode, check this thread for an extensive list of codes.
Note: If you close Kies, you will have to repeat the process.
Note2: You can upgrade to the most recent official firmware version from any firmware version even if you already have the same version or a newer one installed
3.Extracting Samsung Phone Drivers from Kies Installer
Background: Not all users are interested in installing the full software package Kies in order to get to flash their phone via Odin or Heimdall. The Kies installer turns out to be extractable using 7-zip and the phone drivers have a separate installer. This allows for installing only the phone USB drivers and lets you avoid installing Kies and the included bloatware.
Requirements:
-Samsung Kies installer package (found here)
-7-zip (found here)
Procedure:
1.Install 7-zip
2.Right click the Kies installer and Find 7-zip->Extract to "Kies_x.x.x.xxxxx_xx\"
3.Navigate to "Kies_x.x.x.xxxxx_xx-->CabFile-->USB Driver"
4.Right click the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe.cab" file and 7-zip->Extract to "SAMSUNG_USB_Driver_for_Mobile_Phones.exe\"
5.Open the folder SAMSUNG_USB_Driver_for_Mobile_Phones.exe\ and execute SAMSUNG_USB_Driver_for_Mobile_Phones.exe and follow the installer instructions.
6.Enjoy connecting your phone without the full Kies install.
4.Backing up the /efs folder
Background: Some experimental firmwares modify the /efs folder. This can cause IMEI corruption and/or change the product code your phone reports.
Requirements:
-Rooted Phone
Either (A):
-ADB (from the Android Software Development Kit)
Or (B):
-Root Explorer (from market)
Procedure:
1.Make sure your phone is rooted (and busybox is installed for ADB procedure)
A:
1A.Enable USB debugging mode (Settings-->Application-->Development-->USB debugging)
2A.Connect the phone to USB
3A.Open a command prompt and enter adb (see tutorial)
4A.Acquire root privileges (type "su"). (Make sure you accept the root-prompt on the phone)
5A.Execute "busybox cp -a /efs /sdcard/"
6A.Disconnect the phone, deactivate USB debugging, reconnect the phone and backup the copy of the efs folder to your PC
B:
1B.Use root explorer and navigate to the root of the filesystem /
2B.Press "Mount R/W"
3B.Copy the efs folder to your sdcard
4B.Connect the phone to the PC and backup the copy of the efs folder to your PC.
2. Restore the backup if your IMEI gets corrupted or your product code is changed by a firmware.
Tips&Tricks
Handy Tip&Tricks
by Forum Members
This is for all Samsung Galaxy S users (GT-i9000 only. Some might work on US versions). It is a collection of handy tutorials that were posted in the development section but that do not need to be on the first page constantly.
Note: These links are provided as-is and most are untested by me! All credit for the procedure goes to the respecitve poster/involved parties.
1. Changing Fonts (for free) by socket84
2. Replacing Samsung Media Player with Android default by aditya_t90
3. Generating TUN.KO for OpenVPN on SGS by newmail
4. Replacing TouchWiz calendar with Android default by tommy34
5. Setting default homescreen in TouchWiz launcher by socket84 or the derived SGS Screen Changer by pedrodh
6. Installing Samsung Phone drivers WITHOUT Kies
7. OneClick Lagfix by RyanZA
8. CFLagFix by Chainfire
9. LagFix using update.zip by Tayutama
10. SuperOneClick Root by CLShortFuse
11. Headphone SoundQuality Fix or MixGet from Market by gilsken
12. AMOLED Screen for Notifications App by madmack
13. Using LED-Button Backlights for notifications by neldar
14. Comparing Firmwares on Packages by GAda
15. Stopping automatic media scan & scan on demand by aditya_t90
16. Overclocking/UnderVoltaging the CPU by raspdeep
17. Creating FlipFont APKs by ritalin
18. Circle Battery Indicator Mod by Fightspit (ported to SGS by designgears)
19. Official Firmware Update without running Kies by miki4242
20. Unlocking/Unfreezing Samsung Galaxy S for Free (collaboration, see thread for credits)
21. Choosing between GlassLock and Android's stock lock screen by Ateisti or Android Stock Lockscreen for JM8,JPH,JPK,JM9,JPM,JPA,JP6 by Project1.exe
22. Flashing under Linux and MacOS X using Heimdall by Benjamin Dobell
23. Restoring the three button recovery/download combo by Richthofen
24. ADB filesystem plugin for Total Commander by sztupy
25. Enabling Landscape Mode in TouchWiz Launcher by scheichuwe
Firmware and LagFix Selection Guide
Last Updated: April 3, 2010. Up-to-date as of April 3, 2011 15:53 CEST
As you may have noticed, there are a lot of firmwares on samfirmware.com and it's not very clear which ones are best/least buggy etc.
In this section, I will give a general guide to which firmware to use depending on your preferences:
If you like the stock Samsung Galaxy S experience and are looking for the most stable/bugfree version:
-Flash I9000ZSJPK or I9000XWJS8 according to HOWTO#1.
-Install the one of the kernels below or one of the lagfixes from FAQ#A6.
If you would like have the latest firmware and are willing to tolerate some bugs (this is beta firmware):
-Flash I9000XWJVK according to HOWTO#1.
For a list of current custom ROMs, see this thread
Lagfixes and Kernels:
In FAQ#A6 the currently used methods for lagfixes are described. There are a number of enhanced kernels (most of which use at least one of the lagfixes) that add features such as more accessible RAM, enhanced compiling, Clockwork Recovery, Blacklight Notification and several various features depending on the Kernel. Here is a list of the popular, well tested, optimized kernels (Note: Some of them include an overclock):
-hardcore's speedmod Froyo
-laststufo's Super Optimized Kernel
-supercurio's Voodoo Lagfix
-DamianGto's Ultimate Kernel
-tegrak's lagfix build Kernel
There is a frequently updated list here
General Note:
If you want to take the modding further, look at FAQ#D2 in Post#1 for a list of Custom ROMs and chose one you like. Depending on whether or not there is a lagfix integrated, you should then apply one of the lagfixes from the first suggestion. I would also suggest avoiding loop-mount fixes like OCLF and CFLF (see FAQ#A6) because performance rapidly declines over time.
Note: None of the available ROMs completely fix the poor GPS. Most of the ROMs noted above are provide roughly the same GPS performance. Samsung is hoping to release a full GPS fix in september (hopefully with the froyo release) It is not clear if or when Samsung will release a full fix for the GPS issues. However, it is doubtful since there are now many indications that the issue is in fact hardware related and even the final Froyo release doesn't completely fix the GPS.
For us coming from HTC devices if we hose the recovery partition is there a way to recover the phone. It was HBOOT (FastBoot) in the HTCs. Does ODIN provide the ultimate "debricking" feature. I realize there are ways to brick that are unrecoverable, but if I hose the recovery and I am done I will be very hands off on modding.
thanks for this. a good starting point to gather all the info!
should sticky this
I think we are still out of a mod for this forum...
might wanna add this for calibration of the orientation sensor:
http://forum.xda-developers.com/showpost.php?p=6999499&postcount=8
tommy34 said:
might wanna add this for calibration of the orientation sensor:
http://forum.xda-developers.com/showpost.php?p=6999499&postcount=8
Click to expand...
Click to collapse
Added! Thanks =)
can this be a sticky, its very informative?
Great! I've acctually been waiting for a thread like this!
In Sweden one operator(Tele2) seems to have issues with the device not switching to 3G even when available. Does anybody else have these issues with their operators?
FrezoreR said:
Great! I've acctually been waiting for a thread like this!
In Sweden one operator(Tele2) seems to have issues with the device not switching to 3G even when available. Does anybody else have these issues with their operators?
Click to expand...
Click to collapse
Did you check your APN settings? Did you contact the provider concerning the issue?
Darkstriker said:
It appears it doesn't take long for this reserved post to become useful. I'll post short guides on flashing firmware here. (...)
Click to expand...
Click to collapse
In the Flash Firmware using Odin guide didn't you forget to add "SIM unlocked phone" as a requirement?
Akerfeldt said:
In the Flash Firmware using Odin guide didn't you forget to add "SIM unlocked phone" as a requirement?
Click to expand...
Click to collapse
I know it says so in the guide but I recall having read that SIM-locked phones can be flashed as well. Don't quote me on that!
Added it as a requirement for now.
Edit: I did read it here. However, it seems that those phones aren't actually SIM-locked, so for now, SIM-Unlocked is definitely a requirement.
Thanks for pointing it out! =)
Darkstriker said:
Did you check your APN settings? Did you contact the provider concerning the issue?
Click to expand...
Click to collapse
The APN settings should be fine, the phone works on both 2G, 3G and HSPDA, but when it at some point have switched to 2G it will stay in 2G and you would have to manually set it to 3G.
Yeah we are a group on a Swedish android forum where someone have contacted both samsung and tele2 about the problem. But if not anyone here has the same problem it surely must be tied to the operator, which is what I have thought all along.
efbenson said:
For us coming from HTC devices if we hose the recovery partition is there a way to recover the phone. It was HBOOT (FastBoot) in the HTCs. Does ODIN provide the ultimate "debricking" feature. I realize there are ways to brick that are unrecoverable, but if I hose the recovery and I am done I will be very hands off on modding.
Click to expand...
Click to collapse
I'm sorry efbenson, I seem to completely have missed your post.
I'm not sure how this works on HTC android devices since I have only had a Windows-mobile version. What seems to be the equivalent of the features you are "describing" is the download-mode (VolDown+Home+Power) which can be reached even after interrupted firmware-flashed (experienced it myself. Still scary as hell!)
However, I don't think I'm fully qualified to answer your question. Maybe you could reformulate it, since it's not very clear right now.
This definitely deserves a sticky, thanks for this DS
FrezoreR said:
The APN settings should be fine, the phone works on both 2G, 3G and HSPDA, but when it at some point have switched to 2G it will stay in 2G and you would have to manually set it to 3G.
Yeah we are a group on a Swedish android forum where someone have contacted both samsung and tele2 about the problem. But if not anyone here has the same problem it surely must be tied to the operator, which is what I have thought all along.
Click to expand...
Click to collapse
I haven't had such problems and I dont remember reading anything of the kind so far so this likely is an issue with your provider. Maybe you can check if this occurs everywhere or only in specific areas (like cities) or something like that.
My apologies if there is a thread for this somewhere else.
I have spent the last 2 days looking for one but have either been blind to it or I'm "special"
I currently own the HD2.
Purchased in February of 2011 and am with T-Mobile.
I did manage to flash my phone almost immediately after purchase to a NAND version of Android 2.2
Hspl 2.08
MAGLDR version 1.10
Baseband Version:
15.39.50.07U_2.10.50.26
Kernal Version:
2.6.32.15-g66f6ed7-dirty
[email protected] #2
Build number:
2.29.405.5 CL293415 release-keys
Software number:
2.29.405.5
Browser version:
WebKit 3.1
Now I have no idea if all those numbers are needed or not but, better safe than sorry right.
Anyways, I have had no real issues outside of data connection strength but would like to upgrade to a newer version or OS.
I was looking at this particular one.http://forum.xda-developers.com/showthread.php?t=1275119
But I have no idea how to flash over my current one.
Things such as; CWM, and the MAGDLR various toolkits that have been developed in recent months and other vocabulary of the trade has thrown me for a loop.
I am interested keeping things like calendar events, text messages, photos, audio, etc. The basics if you will.
Please, any help or direction would be most appreciated as I am totally lost.
Thanks in advance.
Verkruk
I guess you need to go back to wm6.5 rom and upgrade from there..
You can download the stock rom from htc official website..
Well, if you have a google account linked (doh), calendar events are usually synced with it. Audio and photos, are usually saved in separate folders on your sdcard, so they will remain even if you changed the ROM.
However, I don't usually save my text messages when I'm upgrading, I don't care if I lose them, and they are not backed up automatically. So you need to look for an app in the market (look for "SMS backup" or something) .
After you've backed up your stuff, follow this tut written by me :
http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7
It's for everyone that thinks he's special (jk) . But you need to edit step 8 and step 10.
in step 8, you will need to go to the ROM's thread that you are to install (obviously)
in step 10, you will need to edit those numbers (150, 5) in correspondence to the ROM you are to install and to what device you own (T-mobile or European).
Good luck.
Marvlesz said:
Well, if you have a google account linked (doh), calendar events are usually synced with it. Audio and photos, are usually saved in separate folders on your sdcard, so they will remain even if you changed the ROM.
However, I don't usually save my text messages when I'm upgrading, I don't care if I lose them, and they are not backed up automatically. So you need to look for an app in the market (look for "SMS backup" or something) .
After you've backed up your stuff, follow this tut written by me :
http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7
It's for everyone that thinks he's special (jk) . But you need to edit step 8 and step 10.
in step 8, you will need to go to the ROM's thread that you are to install (obviously)
in step 10, you will need to edit those numbers (150, 5) in correspondence to the ROM you are to install and to what device you own (T-mobile or European).
Good luck.
Click to expand...
Click to collapse
really good tuto... hope it helped him (or her... dunno )
I keep getting a rapitool error and am unable to continue.
It would seem that I have successfully bricked my device.
Typical really +(
Thank you though so much for your help!
And I really do mean that. Least with your help I stood a chance +)
Will keep trying and will update you if I see any changes.
It took several hours and a few breaks, but I got it up and running. Again thank you so much!
I've been a frequent member of the Galaxy S i9000 forum for a while now, but I recently acquired a Samsung Focus (Rogers locked) through my employer. I purchased an unlock for for $8 through cellunlocker.net so that I could use the phone with my Bell SIM card, this works fine (Data, SMS, calls).
My problem - like many others (or so I've read) is that I cannot receive MMS messages. I am not very familiar with the Windows phone, I understand that it has gone through several changes as far as dev-unlocking goes, and I'm having difficulty finding a guide that will work. What I'd like to do is be able to send/receive MMS messages - and I'll do just about anything to get there .
Can someone help me find an UP TO DATE method of developer unlocking my phone? I've heard this is the first step I should take to achieving my goal. Please let me know what information to provide or how I can help you help me
OS Version: 7.10.8107.79
Firmware Revision: 2124.11.9.4
Hardware Revision: 3.1.0.7
Radio Software: 2124.11.9.3
Radio Hardware: 0.0.0.3
Bootloader version: 5.9.2.2
CHIP SOC version: 0.36.2.0
Cheers
First you need to jailbreak or install a custom ROM to get MMS to work. To do this check the second post of this thread
http://forum.xda-developers.com/showthread.php?t=1538718
I would recommend a custom ROM for the phone to be fully unlocked. If you opt for a custom ROM just be sure to check what phone hardware version you have(behind the battery check where the IMEI is and look for rev1.3 or rev1.4) and make sure the ROM you install is for your hardware(rev1.3 or rev1.4)
http://forum.xda-developers.com/forumdisplay.php?f=789
OR
You could jailbreak your phone (easier)
1.Jailbreak your phone through The WindowBreak Project
http://forum.xda-developers.com/showthread.php?t=1407652
In case your data stops working after the WindowBreak hack check the last posting in this thread for a fix
http://forum.xda-developers.com/showthread.php?p=22057540#post22057540
After you jailbreak your phone install WP7 Root Tools
http://forum.xda-developers.com/showthread.php?t=1569832
When your done either jailbreaking or installing a custom ROM search in xda Samsung focus mms with the carrier you wish to be on(no guarantees though of finding your carrier fix)
Thanks for your in depth help, jiraiya_s.
I've installed the Clean ROM 2.0 (checked for revision under my battery, near IMEI, was none )
My question is from here, do I just have to search for a work around for some MMS settings? Is this difficult to find/are there many available?
Behind the battery on the phone. See pic
Assuming your on Bell try to see if this works
http://forum.xda-developers.com/showthread.php?t=1236103
or try this
http://forum.xda-developers.com/showthread.php?t=1614107
It's for straight talk but you could modify it for Bell.
In the StraightTalk.zip you will have Straight Talk XML file. Open the XML file with notepad and look for any att.mvno, http://mmsc.cingular.com, proxy.mvno.tracfone.com etc from the text and change it with your operators settings and follow the steps this thread on how to install it FROM STEP 5 OR 6(if you installed root tools)
If you installed Clean Rom be careful that the diagnostic app is outdated(sorry I don't have a link on where to download the updated app) but when your on step 9 of the thread("Application Data> Volatile> Email Attachments> Attachments) the XML might not show up on the first try so make sure when you email your XML file send yourself 5-6 files of the XML file(it will work eventually). I had this problem too but it will work.
Either one should hopefully work so good luck.
After flashing the Clean ROM I hadn't had time to play around much with MMS settings, however this weekend....a friend sent me a picture message that came in without any problem! I did install a Samsung Tools with XAP installer, but I guess this was all I needed to do to reset my settings
Thanks again for your links and help!
Try sending a picture message to see if it works. When I installed the Clean Rom I could receive picture messages but could not send them. When I applied the XML file(in my case) I could send pics but could not receive them(probably a bug due to the Diagnostics App that it's outdated in the Clean ROM). But after a week it started to work perfectly. With the first generation Samsung Windows Phones(and LG Quantum) there is a problem with the MMS settings especially if they were carrier locked(even though you unlock your phone the settings still remain). Samsung released an app "Network Profile" but will not work with the first gen phones. So try sending a picture message and ask a confirmation from the receiver to see if he got the pic.
Hi Devs,
I've just joined and am uncertain of the proper place for this thread. Apologies if inaccurately posted.
I have the T337A, which I have rooted on ANF4, but I cannot find a recovery. I have read and read but am not finding the solution to my little project. I would like to get a safestrap on this locked bootloader so that I can install and learn to write custom ROMs. I have tried a safestrap but it was not for this specific device and did not work. I have also installed and purchased CWM Recovery and TWRP Recovery, in my learning process. The problem with the recovery is that there is no custom recovery written for this device and the bootloader is locked, as this is the AT&T WiFi/LTE version. So it looks to me like I need to figure out the partitioning image somehow in order to make a safestrap work on this device...as step 1. Is there anything else that I can do with this locked bootloader? I would love to have some help in writing a custom recovery and ROM for this device but I am a tiny tiny noob here and not a hard core programmer. If I could get some feedback on places to start for such a daunting task, it would be great. I guess one thing that I do not understand is why I cannot make my current rooted ROM the default recovery in TWRP. It asks me to choose from the list of supported devices. I understand that it goes: NAND --> aboot.img/bootloader --> recovery/or/kernel --> OS/or/ROM? If this is close to accurate then I would have to write something to the NAND?, which I'm not sure what is yet, in order to hijack the factory bootloader and then write the partitions on the sdCard for the ROM, like the safestrap folks wrote? It looks to me like they also included a version of TWRP touch which I used on the S4 yesterday and was really cool, so I guess that would be needed as well and is also why TWRP does not work for me now...it cannot hijack the locked bootloader. How do I hijack this hard headed thing? fastboot does not work to this device. In the process of this project, I have also run into a roadblock trying to update the /system/framework/framework-res.apk, in the manner that a flash needs to be done, I think. I want to change the /res/values/bools/bools.xml switch "voice_capeable" to true. AT&T or Samsung disable this on this version of the tablet, I guess to sell tethering or something else I'm not familiar with...but the way it looks to me, everything is configured on the device and I have a phone number provisioned for data at least. Why can't I turn on this switch and use the phone portion of the device? Any time I tickle the running framework-res.apk, it kills the OS. I tried compiling an update.zip aligned and signed with test keys or something like that but when I flash it, it fails with wrong footer and invalid signature...then it wipes me back to the stone ages. I warned I was a noob..! ...but not scared to brick some shtuff in order to learn this and write some custom solutions. An after thought...is there a solution for a bootable extSdCard for Android? This might lead to some options if it is possible.
Gathering phone info...
Collecting information. Be patient! Do NOT disconnect the phone!
Model: SM-T337A
Android Version: 4.4.2
Sales Code: ATT
PDA Version: T337AUCU1ANF4
Phone Version: T337AUCU1ANF4
CSC Version: T337AATT1ANF4
Product Code: SM-T337AZWAATT
HIDSw Version: T337AUCU1ANF4/T337AATT1ANF4/T337AUCU1ANF4/T337AUCU1ANF4
Board Platform: MSM8226
Serial Number: R32FA00PMRF
Imei: 3534.............
Unique Number: C1604.......
Connections: AT,MTP,MTP
Battery Status: 4.28V (94%)
Network Type: GSM
SuperSU Pro v2.40
TWRP donate latest
CWM donate v5.5.3.7
BusyBox Stericson donate v1.23.0
Titanium Backup Pro latest
xPosed v2.7.1
Wanam xPosed v3.3.1
NinjaMorph Pro v2.8.2
ROM Toolbox Pro v6.0.6.5
RootLogger Pro v1.9
Nandroid Backup v4.4.5
Next Launcher 3D Shell v3.20
Root Firewall Pro v2.1
SetCPU v3.1.2
w/respect. PitPin
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
pre4speed said:
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
Click to expand...
Click to collapse
Thanks pre4speed. I am taking a look at the two tasks again tonight and decided to take the res/bool = voice_capable issue on first since this will determine how brickable this device can be for me. If I can use it as a regular modem phone then I might be a bit more careful with the bootloader project I did some more tinkering with the framework-res.apk ...specifically the /res/values/bools/bools.xml resource and tried the following:
-------
Factory wipe
Flashed sammobile.com T337AATT1ANF4 firmware
Rooted
SuperSU
Busybox
Froze AT&T update service and others involved
Titanium backup and pulled a good backup
Online Nandroid and pulled a good backup
Installed my XDA app. of course..!
-------
Framework-res.apk:
Used total commander to copy the running apk off to the sdCard and then my PC.
Decompilled in APKStudio2.0.3b-Windows (I am also using Ubuntu 14.04 if there is a better way here..also Android Studio on both OS...just learning).
Edited my value.
Recompiled with zip align/sign option.
***Now here in lies the problem, if I haven't already created one above ***
The random article I dug up said that in order to get past the wrong footer and signature issue, and stone-age wipe, when attempting this via abd sideload with an update.zip, is to now copy the edited file back into the original APK using 7zip in order to retain the original signing keys. When I open the original APK archive, it does not show the resource folders deemed "important and I should not jack with them" in the compiled APK (mainly values/* folder). The article mentioned the resource folders such as res/values/bools are compiled and hidden and that I needed to copy over the new resources.arsc file. I see this in the newly compiled APK I made but it also put the Manifest.xml and /res folder in there. Do I need to copy all of that or just the compiled resources.arsc file? I did all and it boot looped me so I'm guessing that I either did something wrong or this was not the right answer. The last part was to chmod the new APK, use total commander to mount the folder as rw, copy over the file, and reboot. All of that worked and I had to reboot many many times...loop.
That is where I am on the modem part and am going to attempt copying just the resources.arsc in a few. I will post more on the bootloader side soon, as I've been researching what goes on from the time I push the power button until the time I swipe the first screen. Lots of reading
w/respect - PitPin
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
PitPin said:
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
Click to expand...
Click to collapse
Stalled out temporarily on the tab project as laptop hard drive bought the farm. Back in action and made some progress on the tab voice_capable issue. Everything appears to be there and in working order but the SMS modules. I think this has something to do with why the contacts app is blowing up but not sure yet. GoSMS and EXDialer seem to work together without blowing up but the dialer taps the modem and then dies. Taking a break from this to start a thread on rooting the AT&T Alpha. I'm about half way through the exploit on that project. Any input on what might be my SMS problem on the tab 4 would be appreciated. Attached are a few screens.
Does anyone know how to removed the caution sign on the left corner it keep telling me unauthorized action have been detected.
I am in the same boat, I so wish this would come through because I do love this little tab.
same boat
/baker said:
I am in the same boat, I so wish this would come through because I do love this little tab.
Click to expand...
Click to collapse
so did you finally get it going or what?I have been wanting to get my Tab going as well. I've Rooted it and paid for an unlock even, which worked fantastic by the way...Thanx XDA!!! The rooting guide I got from here was right on point,no problem at all!!But anyways, I have it on metro pcs now on the unlimited $60 plan which is awesome (.REAL unlimited internet with NO THROTTLING ) for me because now at home I run pda.net, which gives me very good, fulltime, internet for my home computers as well as the ability to stream everything onto a large screen or even via windows when we want to watch with all the bells and whistles! No lag at all usually,and I don't use my hotspot because of the usb internet connect on pda.net. When I do use the wireless connect, it doesn't take any of the allotted hotspot usage up either!!All in all it's a great deal for me. I just got a new sim for it, called in the imei to metro ,which in turn gave me a phone number and data account, and presto!Been on the net ever since! Now that I've had it for over a month ,I wanna get the voice capability to work as well, being that I am paying for 2 lines now. Although I can use the old trusty hangouts dialer with the GoogleVoice easily enough. I want to be able to use my metro number mainly because these phone companies charge and charge and charge, never caring about us,or our need to have communication at our disposal at all times.Cell phones are by far not inexpensive and the internet wasn't started for us to pay aan arm and a leg to use.Anytime I come out good while dealing with a wireless company. it's a stupendous event,I'm telling you!! Heck ,I'm writing from my home computer now, going through the Tab at this very moment! Nevertheless, I'm wanting for the devs, to come through as well. With maybe even a new rom,sans the at&t stuff, of course, since I do now have a different carrier? Heck, the Tab is even great for when we travel! 24/7 unlimited internet /streaming , and the screen size is much better than the phone screen ever was!I just really wanted to thank XDA for the work they put in to help us part - timers out,Ive been rooting and unlocking and bricking and un-bricking for quite some time now,I even repair phones now actually,but the programming and the putting it all out here for guys like me to have fun and tinker with these phones would be entirely impossible without the DEV'S and their hard work for SURE...Thanx Guys!!You ROCK!
Hi. I need some information and help. I'm a complete newbie to any of this android hacking.
I've had a Samsung S4 since 2013, came with Jelly Bean. Apps are no longer supported, and most new ones aren't allowed, but my S4 works too great to toss! -I took the plunge and recently updated to official KitKat... A downgrade that doesn't allow apps to write to SD cards, gps is dodgy now... -I stopped there, since I've seen too many horror stories from 5.0 updates, -so I know I've got to look elsewhere, and this forum seems the best place for this! -I'm hoping mine is one of the "supported S4's" here!
-Is my Samsung one of the "Galaxy S4 LTE-A" phones that you have a lot of potential updates for??
Mine is an Aussie phone currently with a 64mb SD card, and via the Droid Info App, here's what I know about it:
Model: GT-I9506 (ks01ltexx)
Manufacturer: samsung
Baseband Version: I9506XXUCNJ1
RIL Version: Samsung RIL v3.0
Build Number: KOT49H.I9506XXUCNJ2
Build Fingerprint: samsung/ks01ltexx/ks01lte:4.4.2/KOT49H/I9506XXUCNJ2:user/release-keys
Bootloader: I9506XXUCNJ2
Java VM: Dalvik 1.6.0
OS Version: Kitkat (4.4.2)
SDK: 19
CPU Architecture: ARMv7 Processor rev 0 (v7l)
Board: MSM8974
Chipset: Qualcomm MSM 8974 (Flattened Device Tree)
Cores: 4
Clock Speed: 1190 MHz - 2265 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: interactive
Kernel Version: 3.4.0-2587343
Kernel Architecture: armv7l
1) If this fits in with the 9506 models that are on this system, then which option is the best-working? -Least experimental? Please voice your opinions and experience!
-I'm hoping to get to at least OS 8 or 9 so that I can finally use the current covid government tracking apps (no joke!), and to keep my S4 viable for longer still, and, maybe stuff all working, battery holding, gps, phone, wifi, nfc... maybe access to the sd card by apps ;-) .
I notice there seem to be many routes like LineageOS, HavocOS, CrDroid... Official vs unofficial. For a newbie who's only messed around w APK's, I definitely need some advice
2) And lastly, how much space for these (Windows 10) programs and the chunks of "ROM's" that are needed? -Got to make sure I have plenty of room on my trusty laptop, I think!
3) For an expert, how long to complete all of the run(s)?
Thanks!!
Hi,
I tell you what I use and what is trending right now, than you need to do some digging to know how to do it.
You need first a custom recovery for your phone. This one will work for you, I have the same:
TWRP 3.1
Then a custom Rom, you can use this one, it's the most updated:
LineageOS 18.1
Try to see look for how to flash a Recovery (TWRP), then once that done, the other part is easy.
Good Luck.
himseslf said:
Hi. I need some information and help. I'm a complete newbie to any of this android hacking.
I've had a Samsung S4 since 2013, came with Jelly Bean. Apps are no longer supported, and most new ones aren't allowed, but my S4 works too great to toss! -I took the plunge and recently updated to official KitKat... A downgrade that doesn't allow apps to write to SD cards, gps is dodgy now... -I stopped there, since I've seen too many horror stories from 5.0 updates, -so I know I've got to look elsewhere, and this forum seems the best place for this! -I'm hoping mine is one of the "supported S4's" here!
-Is my Samsung one of the "Galaxy S4 LTE-A" phones that you have a lot of potential updates for??
Mine is an Aussie phone currently with a 64mb SD card, and via the Droid Info App, here's what I know about it:
Model: GT-I9506 (ks01ltexx)
Manufacturer: samsung
Baseband Version: I9506XXUCNJ1
RIL Version: Samsung RIL v3.0
Build Number: KOT49H.I9506XXUCNJ2
Build Fingerprint: samsung/ks01ltexx/ks01lte:4.4.2/KOT49H/I9506XXUCNJ2:user/release-keys
Bootloader: I9506XXUCNJ2
Java VM: Dalvik 1.6.0
OS Version: Kitkat (4.4.2)
SDK: 19
CPU Architecture: ARMv7 Processor rev 0 (v7l)
Board: MSM8974
Chipset: Qualcomm MSM 8974 (Flattened Device Tree)
Cores: 4
Clock Speed: 1190 MHz - 2265 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: interactive
Kernel Version: 3.4.0-2587343
Kernel Architecture: armv7l
1) If this fits in with the 9506 models that are on this system, then which option is the best-working? -Least experimental? Please voice your opinions and experience!
-I'm hoping to get to at least OS 8 or 9 so that I can finally use the current covid government tracking apps (no joke!), and to keep my S4 viable for longer still, and, maybe stuff all working, battery holding, gps, phone, wifi, nfc... maybe access to the sd card by apps ;-) .
I notice there seem to be many routes like LineageOS, HavocOS, CrDroid... Official vs unofficial. For a newbie who's only messed around w APK's, I definitely need some advice
2) And lastly, how much space for these (Windows 10) programs and the chunks of "ROM's" that are needed? -Got to make sure I have plenty of room on my trusty laptop, I think!
3) For an expert, how long to complete all of the run(s)?
Thanks!!
Click to expand...
Click to collapse
Hello,
You can find everything you need in my S4 Unified Collection & Guides.
Follow the "Clean Install Custom ROM" Guide step by step and choose a ROM for your variant at Recommended ROMs section.
Reading and trying to digest this stuff now.
-A quick question: by the wording, I gather that one would use TWRP to back-up the current OS and all that is on your phone (so, if necessary, the current one can come back on)?
-One more: I gather from ruadus, that my phone is one of those 9506 TLE-A phones that these posts all talk about, so that I can go forward?
Thanks!
himseslf said:
Reading and trying to digest this stuff now.
-A quick question: by the wording, I gather that one would use TWRP to back-up the current OS and all that is on your phone (so, if necessary, the current one can come back on)?
-One more: I gather from ruadus, that my phone is one of those 9506 TLE-A phones that these posts all talk about, so that I can go forward?
Thanks!
Click to expand...
Click to collapse
- Yes, you can use TWRP to Backup and Restore current OS and all that's inside the phone. (move the backup to an SDCard or to external storage)
- Yes, you can go forward. You can find the latest version of everything you need in my Collection & Guides I linked above.
Retrial said:
- Yes, you can use TWRP to Backup and Restore current OS and all that's inside the phone. (move the backup to an SDCard or to external storage)
- Yes, you can go forward. You can find the latest version of everything you need in my Collection & Guides I linked above.
Click to expand...
Click to collapse
Thanks!
I've looked at your Collection & Guides page, and I can find downloads for "ks01lte" (like https://androidfilehost.com/?fid=1899786940962577903).
Mine says it's a "ks01ltexx".
-I can't find any info online as to thee difference between ks01ltexx and ks01lte, so...
1) -Will the ks01lte-labelled files (programs) of yours also work for the "xx" that I have?
2) Lastly, I now have access to an old windows 7 32-bit laptop w more diskspace (but only 1gb of ram) that I could try to use as the mainframe for Odin, etc. -This older machine will work OK for that??
Thanks again for your taking the time to help!
himseslf said:
Thanks!
I've looked at your Collection & Guides page, and I can find downloads for "ks01lte" (like https://androidfilehost.com/?fid=1899786940962577903).
Mine says it's a "ks01ltexx".
-I can't find any info online as to thee difference between ks01ltexx and ks01lte, so...
1) -Will the ks01lte-labelled files (programs) of yours also work for the "xx" that I have?
2) Lastly, I now have access to an old windows 7 32-bit laptop w more diskspace (but only 1gb of ram) that I could try to use as the mainframe for Odin, etc. -This older machine will work OK for that??
Thanks again for your taking the time to help!
Click to expand...
Click to collapse
Hi,
I believe ks01lte will work. is it the model I9506? if it is so it will work.
I don't see why it won't work with your Win7, maybe it will be slow, just stop any unnecessary program running to avoid crashing your machine.
himseslf said:
Thanks!
I've looked at your Collection & Guides page, and I can find downloads for "ks01lte" (like https://androidfilehost.com/?fid=1899786940962577903).
Mine says it's a "ks01ltexx".
-I can't find any info online as to thee difference between ks01ltexx and ks01lte, so...
1) -Will the ks01lte-labelled files (programs) of yours also work for the "xx" that I have?
2) Lastly, I now have access to an old windows 7 32-bit laptop w more diskspace (but only 1gb of ram) that I could try to use as the mainframe for Odin, etc. -This older machine will work OK for that??
Thanks again for your taking the time to help!
Click to expand...
Click to collapse
As ruadus said, these files will work fine for your variant.
Odin is portable and small program, no need installation or any special hardware to work. You will be fine.
Just follow the steps on my guides, if u have any other question don't hesitate to ask
Ok, so I'll be starting pretty soon.Am using a WIN 7 machine that I have kicking around,because it has a lot of empty disk, so that I can store the back-up copy of my Samsung S4 I9506 ks01ltexx phone.
-I've got ODIN on my PC and it seems to come up fine. Got the combo bootloader+modem tar file and the TRWP tar file also downloaded... -Haven't yet dragged down the updating OS file yet.
-I've downloaded the Samsung USB driver, but haven't installed it since the phone loads instantly on the laptop w the current driver...
So,if I'm correct, my first step should be to get TWRP onto my PC,and (via ODIN) then onto the S4, and then use TRWP to back it all up to my PC?
-Or should I follow the order of the steps in the guide and do the Bootloader and Modem "flash" first and then follow w TRWP??
Thanks!
himseslf said:
Ok, so I'll be starting pretty soon.Am using a WIN 7 machine that I have kicking around,because it has a lot of empty disk, so that I can store the back-up copy of my Samsung S4 I9506 ks01ltexx phone.
-I've got ODIN on my PC and it seems to come up fine. Got the combo bootloader+modem tar file and the TRWP tar file also downloaded... -Haven't yet dragged down the updating OS file yet.
-I've downloaded the Samsung USB driver, but haven't installed it since the phone loads instantly on the laptop w the current driver...
So,if I'm correct, my first step should be to get TWRP onto my PC,and (via ODIN) then onto the S4, and then use TRWP to back it all up to my PC?
-Or should I follow the order of the steps in the guide and do the Bootloader and Modem "flash" first and then follow w TRWP??
Thanks!
Click to expand...
Click to collapse
You can just take backup of ur personal files (if you have any) from your device to your PC. No need TWRP for that.
Doesn't matter if you will flash first or later Bootloader & Modem. Just follow the steps in the guide if you are unsure for something.
Retrial said:
You can just take backup of ur personal files (if you have any) from your device to your PC. No need TWRP for that.
Doesn't matter if you will flash first or later Bootloader & Modem. Just follow the steps in the guide if you are unsure for something.
Click to expand...
Click to collapse
Thanks (have already backed up my 20GB of pictures and SMS, etc.), but I just want to make sure I can back up the current "working" OS, and be able to put it all back the way it was, if something just doesn't work at the moment after my upgrade attempts. I understand that I'd need TWRP for that, correct? -Which can still be done in the order your guide suggests?
Thanks
himseslf said:
Thanks (have already backed up my 20GB of pictures and SMS, etc.), but I just want to make sure I can back up the current "working" OS, and be able to put it all back the way it was, if something just doesn't work at the moment after my upgrade attempts. I understand that I'd need TWRP for that, correct? -Which can still be done in the order your guide suggests?
Thanks
Click to expand...
Click to collapse
Oh yeah, if you want to backup your OS with data and all these, use TWRP and put the backup into an external storage like sd card or into your pc. If u ever want to restore just go to TWRP, chose Restore and select the backup file.
Retrial said:
Oh yeah, if you want to backup your OS with data and all these, use TWRP and put the backup into an external storage like sd card or into your pc. If u ever want to restore just go to TWRP, chose Restore and select the backup file.
Click to expand...
Click to collapse
Hi,
Thanks again !
Just to get a bit more info: I'll necessarily have to backup my S4 to my laptop's disk (via TWRP). -Apparently the usual is to an SD, but won't have that.
I've googled,and have seen that (at least a couple years ago), I'd need to run something called ADB (Android Debug Bridge) on my PC and droid to allow for that. -And with that and TWRP, I can do a safety backup of the current OS, etc. directly to my PC (and if necessary, put that older OS back on my S4 w ADB).
An example web blog is: https://nerdschalk.com/twrp-backup-pc-adb/
-I didn't see mention of ADB usage in here; is it still necessary as an "add-on", or is it already taken care of in the newer versions of TWRP, Odin, etc?
Thanks!!
Hi,
I've never done that before, I usually use my SDCARD.
Did you follow the steps on the link you shared? What was the issue?
You can go to the TWRP thread to ask more question if you're having probelm.