Related
Basic concepts, how-to'sThis thread is a work in progress. If you would like to contribute information or have ideas for what should be added please PM me.
Disclaimer "just because i am trying to be helpful does not make me responsible for anything that you do to your phone. playing with any of this stuff could destroy your phone"
I am not a dev, but I have been flashing on Samsung phones since the international S2 came out. I also spend a ton of time reading the forums and researching what I don't know. I would like to give back to the community in some way and I hope that this post can help the noobs not brick their devices, as well as keep them from being overly annoying to the members and developers here by posting in the wrong places and asking dumb questions.
Some basic rules if you are a noob and don't want to turn your phone into a brick.
1. be patient. don't be the first or even the tenth person to flash anything. wait until you see others using whatever Rom or kernel with success.
2. If you have any doubts about what you are doing, read more. don't flash.
3. make sure you are in the forum for your device, not some similar or related device.
Some basic rules for these forums
1. If you have a question, the first thing to do is look it up yourself. that means searching the forums first, then searching Google.
2. If after searching you can't find an answer, then post in the q&a forum
3. don't report bugs unless you are using an intact version of whatever Rom, if you have changed kernels, installed a ton of apps etc it probably isn't a bug, it's a bad combo or its you.
4. don't report bugs unless you are 150% sure that no one has reported it yet.
5. if you report a bug, make sure you can duplicate it first, then get a logcat of the problem so you can help (see below for logcat info)
Why flash?
by flashing your device you can make your phone act differently, look different, and enable new or disabled options. you could ,for example:
enable native tethering
enable call recording
change the look of your phone
add custom toggle buttons
overclock or undervolt
increase battery life
etc..
Kernel vs Rom vs Recovery vs Modem
Kernel is the layer between the phone hardware and the rom. it controls things like Wi-Fi power, touch sensitivity, possible range of screen brightness, phone logging, and processor max and min speed. kernel must be designed not only for your device but also for the type of rom you are using (Sammy rom or Aosp) some kernels support all roms, others are specific.
Rom is the operating system of your phone. there are three main categories of roms.
roms that are based off of the Samsung stock rom (Sammy rom)
roms that are based off of Android open source project aka AOSP (AOSP, AOKP)
roms based off of the miui project (these used to be a branch of AOSP but recently they have also used Sammy base for miui)
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs3) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days, especially on the sgs3. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
modem is a file that controls the cell radio of the phone. helps determine what frequencies to use and settings for a particular network. It is important when flashing a radio that you flash a radio that is for the AT&T sgs3 as flashing the radio from another carrier has been known to cause problems with the IMEI
Methods for flashing files - Odin vs mobile Odin vs. clockworkmod(cwm) vs adb
Odin is the internal Samsung tool for flashing. I believe it only exists on Windows platform. This tool is mostly used to initially flash an insecure kernel or rooted kernel, OR to return to completely stock rom. This tool can effect your flash counter (see below). Files for flashing in odin generally should end in .tar or .tar.md5 although sometimes they come zipped and the tar is inside the zip. Read more about Odin before using it as it can easily break your phone. !!!as a general rule make sure you never check the "partition" checkbox EVER!!!
Mobile Odin is a phone based version of Odin made by the very talented developer Chainfire. It can be installed on a rooted phone and used to flash the same .tar based files as the desktop version. Mobile odin has a few advantages. 1 you can use it from your phone. 2 it does NOT effect the flash counter on your phone, 3 it can auto root a stock rom (nice if you want to try out a brand new update that has not been rooted yet)
clockworkmod(cwm) is recovery based tool that can make backups of your entire phone, flash new roms, kernels etc.., and do many other useful tasks. Once you have this on your phone my guess is that most of your flashing will be done through this tool. The files for flashing through clockworkmod are .zip files. Clockworkmod will NOT effect your flash counter.
ADB is the android develpment bridge. It allows for command line interface with your phone through it's debugging options. ADB can do most anything as I understand it. In my several years of flashing I have only had to use it once, and i could have waited for someone to come up with another solution. In general as a noob i recommend you stay away from ADB.
open source vs Samsung based roms vs miui
Open Source Roms such as AOSP/AOKP are built using Google's open source android code as a base. The developers then add functionality specific to the device. The advantages of these builds are that they often have tons of options built in to the rom that change the behavior and look of the phone. They usually allow you to change the toggles in your notification pull down, change the battery display, make all kinds of adjustments to sounds, vibration etc... Some people also prefer the "vanilla" android look and feel. These roms often provide "bleeding edge" concepts, design, and modifications. The Disadvantages of these roms is that some of the hardware coding is done closed source by the phone manufacturers, which means that things like bluetooth, camera, video recording, and MHL video out often don't work or take much longer to get working by the developers. Basically anything that relies on the Samsung framework will not work in an open source build. This means Svoice, Snote, and the Samsung camera app will not work.
Samsung based roms are taken from the Samsung original phone software and modified by the developer. Usually, these roms are modified in order to be faster and to make changes to some of the features. Expect to see changes to the stock rom like: debloated (ATT and samsung software removed), de-odexed (explained later), enable tethering, unlimited sms recipients, added notification toggles, etc. Most of these changes are made to: make the phone faster, improve battery life, make the phone easier to theme. The advantage of these roms is that they still use the Samsung framework so all the proprietary stuff like camera, bluetooth, MHL still work, the disadvantage is that they will never be as customisable as open source roms.
MIUI is a rom that focuses on theming. Official MIUI (Chinese) gets updated weekly on Friday and then there are lots of miui developers who adapt it to other languanges and make some tweaks to it. MIUI can be built from AOSP source or Samsung source and depending will have different features. The first MIUI rom for our phone just appeared in these forums and it is based off of AOSP. MIUI has a unique look and is also highly customizable through theming. There are tons of themes available for download through the rom itself and you can mix and match any part of any theme you want. This includes icons, lockscreen style, etc.. Some people criticize while others praise MIUI for being very "iphone like". This is because the icons look more iphone like and there is no app drawer in the MIUI launcher. However, you can still use any launcher you like within MIUI.
odexed vs de-odexed
odexed is how the phone comes stock from Samsung. Odexed means that system files and apps are split into two pieces and kept in different places on the phone. This is done to speed things up a bit. However, it makes it harder to theme the phone because the apps are split up. Most custom roms choose to de-odex (basically regroup the files back into one) so that custom themers can make themes more easily for the phone.
download mode and recovery mode how to access
(Copied from mskip and his toolkit thread here: http://forum.xda-developers.com/showthread.php?t=1746665)
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
STEP BY STEP how to flash your phone for the first time
A. get root
first off, you need to gain access to the root of your phone. there are several ways to do this (thanks to all the talented devs).
I recommend using mrRobinson's method as it will not trip the flash counter on your phone.
1. you will need to have odin from here http://forum.xda-developers.com/showthread.php?t=1722686 remember to hit the thanks button, download and install odin.
2. Kies (on Windows, not on your phone), Samsung's sync program, can interfere with Odin. Either make sure Kies is closed and close it out of background processes using the task manager in windows...or better yet, uninstall it completely.3. make sure you have the proper samsung drivers installed. you can get the USB drivers directly from Samsung here: http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT
4. you need to download the right image from mrRobinson's thread. to find out which one hit the menu key from your home screen, select system settings, select about phone at the bottom, and look for the build. it should be either UCALEM or UCALG1. Once you know, go to mrRobinson's thread here http://forum.xda-developers.com/showthread.php?t=1739426 download the matching image, and dont forget to thank him.
STEPS 5-7 COPIED FROM mrRobinson's THREAD
5. Extract the .tar file from the .7z file you just downloaded from the thread in step 46. Put your phone into download mode (see how above)
7. Start Odin, connect your phone to your PC, you should see the box under ID:COM change color to show your device is connected. click on PDA and select the .tar file you just extracted. Hit the start button and wait for the file to flash to your phone. When done your phone will reboot automatically. One word of warning about Odin: DO NOT TOUCH THE CHECKBOXES!!! WHATEVER YOU DO>>DONT TOUCH THE RE-PARTITION CHECKBOX!!!!B. installing clockworkmod
the next step is to get a working clockworkmod recovery on your phone instead of the default recovery. Again, there are many ways to do this and there are several different versions of CWM recovery available. I recommend using the one from Rom Manager as it seems to be compatible with most roms. Note that currently most versions of CWM can only see your internal SD card and not your external if you have one.
1. Go to the Google play store and download Rom Manager (https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd)2. Open Rom Manager app, flash clockworkmod recovery (first option), choose the appropriate phone..in this case galaxy s3 att, grant it superuser privileges, it should say install successful. NOTE: some users have reported not seeing the S3 ATT in the list of devices in Rom Manager...this is a bug and hopefully will be fixed. It may be that you need the purchased version instead of the free version for it to work? Not sure why this is but if it gives you trouble there are other ways to flash a recovery image. The next easiest way once rooted is to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1746665 from there you can flash both cwm or twrp whichever you prefer. Alternatively you could also use goo manager to flash TWRP link to goo here: https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
C. Test out your new recovery and make a backup of your phone
1. turn your phone off, then turn it back on while holding the Volume UP and home key. (more detailed instructions above) You should see Clockworkmod Recovery at the top.2. Use your volume keys to navigate to the backup option and select backup, then wait for it to complete. You now have a backup of your phone you can restore to at any time.
D. downloading and flashing a new rom
now its time to decide what rom to flash. when choosing a rom read the first post of the thread (the OP) carefully and take time to read through most if not all of the thread. At the very least go read the last 10 pages of the thread so you are familiar with any current issues people may be having. Once you have picked a rom:
1. Download the rom you want to try2. Make sure that the rom ends up on your internal SD card and that you know where it is3. Get into CWM recovery4. As a general rule it's a good idea to wipe data/ factory reset from CWM recovery (this will wipe all your data on the phone except any photos/videos you may have taken)5. It is also good practice to wipe cache from CWM recovery6. Lastly, from the advanced menu in CWM choose to wipe Dalvik cache7. now go back out to the main recovery screen and choose "install .zip from SD Card" option and navigate to your rom, select it and confirmnote that a new rom may take longer to boot the first time.
Flashing "dirty" vs flashing "clean"
Clean
Doing a clean install of a rom means erasing or formatting all the data from the previous rom before you flash the new one. This is the prefered way to flash a rom to ensure that it will run smoothly. It is necessary if you are switching from one rom type to another (CM to Samsung base). In order to do a clean flash you need to boot into recovery and select the following options: wipe user data (this wipes all apps and personal data, but not your photos/videos), wipe cache, advanced>wipe dalvik cache, storage/mounts>format system. This will ensure that no trace of the former rom is left on the phone. Beware that at this point your phone will not boot until you install a new rom. I suggest using titanium backup to backup apps and smsbackup+ for texts to make getting your new rom configured easy.
Dirty
Doing a dirty install means just flashing a new rom right over the top of the old one without wiping any data. The advantage to this is that you don't lose any apps or account info. The disadvantage is that you open up the possibility for problems. Generally you only want to flash this way if you are upgrading a rom (CM10 nightly to the next nightly, or from one samsung based rom to another). If you decide to flash over the top and have any issues, you should not report bugs, but try flashing clean first.
backing up IMEI
There have been some issues with people losing their imei number when flashing roms. *It appears to be limited to the old imei software version 2 but the evidence is not yet conclusive. *If you lose your imei, you will not be able to connect properly to the data network. *Luckily some devs have figured out how to re-inject an imei number into our phone and get it working again. *It is certainly a good idea to back up your imei info before flashing just to be on the safe side. *There seems to be two main threads dealing with backing up and restoring your imei. *you can check them out here:
http://forum.xda-developers.com/showthread.php?t=1801997
http://forum.xda-developers.com/showthread.php?t=1804117
huge thanks go out to these devs for figuring this out!! as always make sure you thank them.
I have yet to try either of these methods out myself so if one seems much easier or clearer please let me know.
tethering (for stock Samsung based rom)
you can use a mod to enable wifi tethering from your phone to up to ten other devices and share your data connection. If you are running a custom rom you probably already have this enabled and don't need it. It is already included in any AOSP roms also.
Make sure that you use the version of the mod that is for your software version number (UCLEM or UCLG1 see beginning of rooting guide to figure out which one you are on).
The original mod for UCLEM is here: http://forum.xda-developers.com/showthread.php?t=1732262
The mod for UCLG1 is here: http://forum.xda-developers.com/showthread.php?t=1768826
The Flash Counter
The flash counter is an internal counter that ticks every time you install a non-samsung firmware through Odin. This allows Samsung or AT&T to see if the phone has been flashed with custom roms. custom recoveries such as Clockworkmod and TWRP as well as the mobile version of Odin DO NOT change the counter. Only flashing non-Samsung files through the desktop version of Odin does. You can see your flash counter when you enter download mode on your phone. Luckily, Chainfire has developed an app that allows this counter to be reset, so there is really little concern anymore about having the counter trip. If you do need to send your phone in for repairs, you will want to reset the counter and then flash an unmodified stock rom through odin to get your phone back to factory state.
Link to Chainfire's app through this post here: http://forum.xda-developers.com/showthread.php?t=1800878
Logcat
Logcat is a way to access the android system log for everything that is going on behind the scenes. This tool is used to help developers pinpoint problems in a rom. If you want to actually be helpful to a dev when reporting a bug, you should really learn to use this tool. I am no expert on logcat but you can find some good information in this post: http://forum.xda-developers.com/showthread.php?t=1726238
APN settings
This is the apn that comes on stock at&t phone. It allows you to connect to LTE as well as hspa+
Name: ATT PTA
APN: pta
MMSC: http://mmsc.mobile.att.net
MMS Proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: 410
Auth: none
APN type: default,mms,supl,hipri
NOTES BELOW ARE COMING SECTIONS. Feel free to pm me questions you would like to see answered or suggestions for other info:
theming
unlocking sim
returning to stock
What info is stored in each area: system, data, cache etc...
Looks good.
Stuck
FNM
I now know more about Android OS! Thanks for the info.
Good thread! In your step by step guide I suggest you add installing adb and adb basics. IMO, this is essential for anyone flashing, has bailed me out of trouble on more than one occasion.
Sent from my SGH-I747M using XDA Premium HD app
MORE ! MORE ! Very nice work thanks, this is shedding some lights on the terms we see floating around
excellent information, much appreciated, so what is de-odexed and odexed? thanks again!!
I got my s3 when it first shipped, and soft bricked it a month later. Even if you do everything right, it can still mess up. So waiting for a USB jig to come in the mail since my homebrew jig didnt work or I hard bricked my phone... Be warned...
Very helpful thread, thanks a lot!
Thanks for this guide!! Very helpful. Coming from a very different phone, everything about the S3 is foreign to me! Could you maybe talk about backing up nv stuff and imei?? I know there's another thread that explains it, but, this being the noob helper, I think it'd be good for anyone new to this phone.
Thanks
Thank you for making this! I'm sure this will help a lot of people out. I've flashed quite a few times and having a guide like this is definitely helpful.
I sure hope I had this guide when I flashed for the first time a few days ago, but at the time you only had part 1 done and the guide had not been completed yet. Glad to see it finished and it'll definitely help out others.
mods
Thanks for all the invaluable info on flashing ROMs. I've been a BB user for years so Android is still new to me. I'm looking into rooting and trying out some custom roms, but I had a question. When it comes to Mods can you just add those individually?
I want to use Team Sonic's FreeGS3 Rom mainly due to it's Sony Bravia engine Mod and the Awesome Beats Mod (or at least when they get it working on apps other than Google Music). However, they don't have a fully supported Rom for AT&T just yet.
Trying to have the best of both worlds....I may just need to try out something else and wait for the full ATT version.
This is a great thread you've created OP. However, I'm a tad confused. You mention in the guide that Kies interferes with Odin and you say to close and close it out of the backround, but you also mention "better yet, uninstall it completely." One of the reasons I'm rooting my new phone is to be able to delete this bloatware. Are you implying this is possible without first rooting the phone?
Thanks a lot in advance, this is very helpful.
jroyjohnson said:
Thanks for all the invaluable info on flashing ROMs. I've been a BB user for years so Android is still new to me. I'm looking into rooting and trying out some custom roms, but I had a question. When it comes to Mods can you just add those individually?
I want to use Team Sonic's FreeGS3 Rom mainly due to it's Sony Bravia engine Mod and the Awesome Beats Mod (or at least when they get it working on apps other than Google Music). However, they don't have a fully supported Rom for AT&T just yet.
Trying to have the best of both worlds....I may just need to try out something else and wait for the full ATT version.
Click to expand...
Click to collapse
I would wait to flash any ROM that isn't specifically for your device. However you may be able to flash the mods you want like the bravia mod on top of an att ROM. You need to find the original post for the mods you want, and do some research to see what they require and if anyone has used them successfully. Be extra careful of mods written for the international version of the phone.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
omi__ said:
This is a great thread you've created OP. However, I'm a tad confused. You mention in the guide that Kies interferes with Odin and you say to close and close it out of the backround, but you also mention "better yet, uninstall it completely." One of the reasons I'm rooting my new phone is to be able to delete this bloatware. Are you implying this is possible without first rooting the phone?
Thanks a lot in advance, this is very helpful.
Click to expand...
Click to collapse
I can see why you are confused. I am referring to kies on your windows PC. (If you installed it at some point) Not the version that runs on the phone.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
OP, are you sure you can install CWM through ROM Manager after rooting? I remember trying to do this on my SGS2 last year and my phone soft bricked. Tried it twice, and still soft bricked.
Why not just use Robinson's method?
ComradeNF said:
OP, are you sure you can install CWM through ROM Manager after rooting? I remember trying to do this on my SGS2 last year and my phone soft bricked. Tried it twice, and still soft bricked.
Why not just use Robinson's method?
Click to expand...
Click to collapse
I tested it out myself and it works fine. I figured this was the easiest way to get it done and not have to get adb up and running. Also, the official cwm is supported by all the new roms like cm10 and some other recoveries have had issues flashing those roms.
Thanks for putting this together! Very Helpful!
One question, you say flash CWM , first in list choose Galaxy S3 ATT, when i open Rom Manager and choose Flash i don't have the S3 for a choice ?I have Galaxy Note, Skyrocket and T-Mobile Galaxy S2, no S3....
Cholerabob said:
One question, you say flash CWM , first in list choose Galaxy S3 ATT, when i open Rom Manager and choose Flash i don't have the S3 for a choice ?I have Galaxy Note, Skyrocket and T-Mobile Galaxy S2, no S3....
Click to expand...
Click to collapse
Try scrolling down the list
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
In the past couple of weeks I had jedi 3.x rom installed on my i317 from att, with asylumcore kernel at 1.92ghz overclock and no fsync(). Had it fully themed from various theme mods around the forum and everything was running great till i found a AOSP lockscreen mod that i decided i really wanted to put on here. I flashed the mod and my phone would load up show the TW lockscreen for 1 second then reboot again over and over. I was stupid and did not make a backup before flashing the lockscreen. could not get phone to stop resetting w/o pulling battery. after flashing the new jedi rom and kernel my phone still continued to bootloop, but without ever getting to the bootanimation. I had a cm rom on the sd card that i kept to try on a "rainy day". after flashing that the phone was able to fully boot and was working but this rom is very buggy for me. i realized that i had forgot to format /data before or after flashing and thought this could be the issue. went into recovery and now every time i try to format it the recovery reboots. tried flashing teamwinrecovery and it only loads the splash image then a blank screen. So i went back into cm and used the app Rom Toolbox Pro to see if it could clear out all of /data, and mentioned that my version of cwm had to be done with rom manager but with the option to try anyway? i answered yes. phone booted into recovery and now automatically tries to clear /data but keeps rebooting and repeating the process. Now i can't flash anything becuase rom toolbox is automating the whole thing.
So I ask, does anyone please know of anyways that i can mount my phone to my computer for editing without being booted up into the rom or recovery? or is there a way to use Odin to somehow clear all the partitions so that i can start new?
Sorry for long post but right now my phone is a $650 brick.
U just answered ur own question.......odin bacjk to complete stock
Sent from my SAMSUNG-SGH-I317 using xda premium
I live outside of any major city and the only real internet i could get was through my phone via tethering. so i was on dialup to even write the previous post. But I went into town and borrowed the local restaurant's cable internet and downloaded the stock firmware and I believe everything is in working order
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
JonoPorter said:
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
Click to expand...
Click to collapse
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d a bad flash in a custom recovery but everytime I have to use Odin I get extremely nervous.
Read Beerdroid's guide and you can't go wrong
hednik said:
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d abad flahs in a custom recovery but everytime I have to use Odin I get extremely nervous.
Click to expand...
Click to collapse
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
xBeerdroiDx said:
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
Click to expand...
Click to collapse
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
JonoPorter said:
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
Click to expand...
Click to collapse
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
hednik said:
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
Click to expand...
Click to collapse
i'm an advocate of AOKP, but thats just my 2 cents. there is a very solid 4.1.2 milestone out and their 4.2.2 milestone will be released very soon.
although faryaab is a great kid and puts some good stuff together, remember that supernexus is a port and you could experience bugs (as i did). again, just my opinion
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB
Don't even try this LOL!
I was browsing around my storage closet and i saw my d710 sitting in the original device box, it has been so long since I touched this device and I thought I'd tinker with it knowing it's broken anyways ( cracked screen, touches are still usable, 3.5mm HJ busted ). I stumble upon lanchons thread with isolated recoveries and using twrp 3.0.2.0-1 with his patch and I thought to myself, huh, what if ( Derp moment ) I use CM13 on this....
So I fully wiped the device. installed isorec cm 11, flashed 2.8.4.0 i9100 + Patch, rebooted, flashed i9100 3.0.2.0-1.img + Patch, rebooted, re-wiped the device, transfered cm13 over via usb mass, and installed it.
I removed the asserts from the zip and I couldn't care less if it had bricked or not and what do ya know, Its optimizing apps after a 10 minute sit away from the device.
I just started tinkering now so there's a lot I haven't played with, all I know is the camera works, and WiFi is broken, back button works and the search button = menu, lmfao. If any of the developers wants someone who tested and booted it up, well here it is.
NOTE: I tweaked the build.prop on certain aspects of device model and ID, to SPH-D710 instead of GT-i9100 just in case it needed to be d710 to boot up, which I highly doubt i didn't need to change.
if you guys want me to tinker more just ask :3
How does this not have any replies? We might finally find a way to bring Marshmallow to the D710 after all!
I can confirm that this method works. I installed Slim6 and sure enough it booted, however it looked like it had the same issues as CM13 as stated in the op. I'll attach some pictures of the about phone screen. I guess the GT-I9100 and the SPH-D710 are similar enough that marshmallow roms will boot although with deal-breaking issues(wifi, nav buttons.)
Probably needs a custom kernel that'll fix the wifi issues, i think you can always fix the capacitive buttons with a tweak to the /system/usr/keylayout files. Besides that, it is really laggy and unstable for me, all i can do is sit at the home screen, and when I start doing something it over heats ( my battery is old, might be the issue ) and hard reboots the device.
Other than that you need to add qemu.hw.mainkeys=0 to enable native on-screen nav buttons
Can't install gapps, not even pico, insufficient device storage. :/ but why bother when wifi doesnt even work lol
Edit: I hope Dastin or anyone can see this post and start cooking up some MM Goodies, or even do ports and build some custom kernels
i also did this with cm12.1 a few months ago and experienced the following problems:
USB doesn't work on the i1900 ROMs or recoveries
likewise with SdCard
rebooted often (wasn't overheating)
no WiFi, but Bluetooth worked
buttons wonky (don't remember exacts)
With how the recovery works I bricked it. I tried installing the cm13 kernel with the twrp that doesn't work with it and bricked it. I have been unable to Odin anything working because my battery died, and I am unable to charge it.
EDIT: got it to charge using a different phone and a small battery modification. testing the d710 cm12.1 beta
I might do this with mine, but the battery is practically dead and i sometimes get random resets (even when in recovery).
Would be nice to bring some life back into an older phone.