Related
I have noticed a few people complaining of call echo with AOSP ROMs (even with "noise suppression" checked), as well as some stock based ROMs. I was having the same problems. Stock based ROMs were better, but echo was still there. I tried several radios without avail.
What finally worked for me was going back to stock through Kies (keep in mind this will wipe your internal sd as well, so move your backups off your phone). I have since been able to flash PACman ROM without call echo. I have not tried any others but I assume the result would be the same. If someone is willing to test other ROMs/radios and report back that would be great. I just don't have the time.
Also, I did not flash a different radio after going back to stock. I assume it would be okay to do so, but I am not a dev so that is only a guess. What I think going back to stock fixes is some missing/corrupted libraries that are somehow surviving ROM flashes (like in a protected storage or something like that).
Anyway, I hope this helps someone else.
EDIT: This doesn't work all the time, and has only really worked for me once. I have done it twice and it worked great the first time, and not really the second. It's worth a shot, but just keep this in mind.
:::Specifics:::
Essentially all I did was go to the latest stock rom image from T-Mobile. Kies upgraded my phone to UVLI1, which is T-Mobile's latest 4.0.4 stock rom. Kies essentially wiped everything from my phone (except external storage) and imaged it with the latest factory image which includes the latest radio. I have since been able to root, install TWRP and flash an AOSP based rom without degradation in call quality. I did not flash over the radio that was installed by Kies, and I did not wipe android secure in TWRP (don't know if that made a difference).
What you should try if you are having call quality issues:
1. Go back to stock unrooted (use your method of choice, I used Kies but that doesn't work for everyone so try Odin or Heimdall)
2. If you didn't go to the latest stock unrooted image from T-Mobile and Samsung, do that through Kies which should now work for almost everyone (as of Jan. 1, 2013, the latest stock image is UVLI1/TMBLI1)
3. You should now be able to root and flash any rom you like without call quality degradation (if this is not true for you please let me know --- see above for what I did at this point)
I'd be interested in getting some feedback from this. Keep in mind that I am not always available and may only be able to reply once a day or less. Again, this is just what worked for me, it may not work for you. Please give yourself plenty of time when going through this process as Kies is not very fast (at least in my opinion).
UPDATE:
Here is how I got Kies to update my phone while still rooted and even running an AOSP rom. As always, do this at your own risk. I accept no responsibility for broken devices or lost data/pictures/music/etc. However, I have done this twice now, so just read and understand what you're doing and you should be fine.
Keep in mind that this WILL WIPE YOUR INTERNAL STORAGE! You have been warned.
1. Disconnect your phone from your computer
2. Launch Kies and click on Tools>Firmware Upgrade and Installation
3. Input model number (it's case sensitive !?) and hit OK
4. Input serial number (found under battery) and hit OK
5. Hit okay on windows until it starts downloading the latest firmware for your phone
6. After it's finished downloading it will tell you to put your phone in download mode and connect it to your computer. Do it, check "I understand..." and hit OK (I also opted out of the sending of information to Samsung)
7. Wait until it's finished. It will likely launch a window saying it's downloading a file for emergency recovery of your device.
8. When it's (finally) done it will tell you it was successful (hopefully). Your phone will automatically reboot and all will be well with the world and your phone.
Hope this helps.
kies fails recognize my phone. already have the phone drivers installed.
You have an interesting post, but it would be of more use to people if you specified the exact information about what's on your phone. Such as which stock ROM version you were able to flash through Kies and what radio version you are currently using.
There are different stock ROMs and radios on the forums, so it doesn't solve anything if you haven't told us what exactly works with your phone that others should try.
Here is the rub. I haven't been on stock unrooted rom since buying the phone in March. I have bounced around roms and radios quite a bit (probably at least one or two a week on average). My wife has complained of call echo for a long time (multiple roms, multiple radios and AOSP and touchwiz based roms). Touchwiz based roms had better call quality but echo was still present. I decided to Odin back to stock unrooted and see if it was a hardware issue or not. It wasn't a hardware issue because call quality was great. So I rooted the phone, installed the latest TWRP (2.3.3), but wasn't happy with stock rooted so I decided to try an AOSP rom. I wiped only cache, dalvik cache, system and data (not android secure, don't know if that made a difference or not). It works great; i.e. no call quality issues. I did not flash a radio.
So, essentially what I did was:
1. Went back to stock unrooted (Kies put me on latest 4.0.4 from T-Mobile, which flashed a radio, the rom and cleared internal storage)
2. Rooted and installed TWRP
3. Flashed my rom of choice, but not a radio and I didn't wipe android secure (not sure if that matters)
Honestly I don't know what about that process fixed the echo issues, all I know is it did. If you can't go back to stock unrooted through Kies then use Odin. There are great threads giving step by step instructions on how to do that. I just decided using Kies would be easiest for me, and it worked for me.
I hope these are the details you are looking for FineTalent. And thanks.
Excellent lol. If you own the d30 case from tmobile take it off. Worked for me as well.
I do have the d30 case but taking it off didn't seem to make a difference. Besides, the wife didn't like the idea of my phone going commando.
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
I did not know that LI1 was the latest 404 ROM ?
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
bert269 said:
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
Click to expand...
Click to collapse
It was simply the latest one Kies found for my phone. I believe it was labeled as UVLI1/TMDLI1, but I suppose I could be mistaken. If you install Kies on your computer (shudder, I know) and plug your phone in it will compare the rom version on your phone to the latest known rom from tmobile/samsung. You will need your phones serial number I believe. At least, it was needed when I "upgraded" anyway.
whytechapel_x said:
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
Click to expand...
Click to collapse
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
monkeybuttons said:
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
Click to expand...
Click to collapse
1.Well i didn't root my stock phone. After using odin
2.I used cwm 6.0.1.5
3.Same.
4. Well i followed the steps in the all star thread which is wipe data/factory reset. Then flashing rom and wiping cache and dalvik cache.
5. The all star rom is heavily modded so idk. I tried it with "noise suppression" on and off.
6. All star gapps.
I want to point out that as soon as i flashed jedi knight 6, the call echo was gone but i want to be able to use my AOSP roms without call echo.
Since I'm not a dev I can't really diagnose the problem. I only hoped that what worked for me would work for others as well.
When I went back to stock I rooted, but didn't like stock. TWRP has been my go to recovery for a while now and the options available in PACman rom have me by the heart strings, so those are the first things I tried. I wish I had time to fiddle around with it and truly try to find out why it worked for me but I just don't have that option right now. Sorry I'm not of more help.
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
whytechapel_x said:
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
Click to expand...
Click to collapse
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
FineTalent said:
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
Click to expand...
Click to collapse
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
whytechapel_x said:
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
Click to expand...
Click to collapse
I am not able to exactly help you with your issue as I am using a different ROM than you. However, if you have tried different radios and they did not seem to fix the issue, can you possibly try installing a different kernel? Also, check the phone settings and see if there is an option to turn on 'Noise reduction' which has been mentioned on here before, it seemed to have worked for some people.
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
whytechapel_x said:
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
Click to expand...
Click to collapse
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
monkeybuttons said:
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
Click to expand...
Click to collapse
will do. but if i remember, i would still get call echo on aokp milestone 1
whytechapel_x said:
will do. but if i remember, i would still get call echo on aokp milestone 1
Click to expand...
Click to collapse
Have you tried any ICS based AOSP roms? Like cm9.1 or AOKP (I can upload the file for you if you want; it is no longer on goo.im). I think I kept ICS AOKP the longest of any rom.
Hello All,
aXcelio here…..
I'm new to the world of Android switched from the iPhone….(was and still am a loyal user of IOS devices for the better part of 5 years)…..but out of shear boredom, I made the decision to decided to make the switch and I for the most part could not be happier. In doing so I picked up a Galaxy Note II SGH-1317 (AT&T), I've updated the stock rom (I think that's what its called) to JellyBean 4.2.1……now I'm in a place where I want take advantage of some of the feature embedded in CM (it looks really cool)……
So a buddy of mine, who's been running with droid's for as long as I've been running IOS decided to give me a hand in getting my device rooted……we used an exploit called EXYNOS, and installed TWRP (again forgive me ignorance if I'm speaking out of term…I'm learning, or trying too), everything appears to be running without incident, (with the exception of my not being able to create any backup…as the system tells me that I don't have any free space)….get back to that in a lil bit.
Now….I scored the CM site as well as XDA, but haven't really been able to find what I'm looking for (some of which could be out of fear of destroying my device, and some of which is based on a lack of understanding….more I think though of destroying my device……..I should note that I completely understand that any of that any info I get here or there…..is as is, and without any guarantee.) So here I am reaching out to you folks for some guidance……..with that allow me to ask a couple of questions…..
In an effort to get a better understanding of what my buddy did…..I would like to go through the process of setting my device back to defaults (as if I just brought it home from the store) no root, no play apps that I've installed….(I can do that later, and I'm not overly concerned about losing anything) and re-root the device…..that being said, is there a way to that (set the device back to defaults)….I've seen one article using the stock firmware, (which I've downloaded) and another which states that I can do a factory reset which will unroot the device…(but not sure what approach to take or for that matter I should even worry about that)
The second thing I'm wondering about is this……most of what I've read regarding the install of CM is that I need clockwork recovery (or something along those lines) but I have TWRP…..if I opt to not reset the phone back to factory default and unroot (or find that I really don't need to move in that direction) can I install CM using TWRP?…..if I need clockwork, can I instal this over TWRP……or do I need to do something different?
a
The last thing I have (at least for right now) is this….assuming I can move forward with the install and configuration of CM, I wonder if any of you can provide a step by step guide on how I go about this on my particular device……I've seen this article well as this ones these however appear to be for version 10, of CM…but I see there is a 10.1……I read another article (but can't seem to find it now…which stated that it worked with my device and 10.1, with a link but all of the nighties….seemed to be specific to the Galaxy Note…..not the Note II…..and again I would much rather reach out to you guys for guidance prior to doing anything…..The last question I have is I see there is a version 7100 of my phone and then one that says something about LTE (but not specific version……) is the SGH-1317 an LTE device that is version agnostic (if you will)….in other words if I see a post for an LTE GNII is that speaking to my device or something else……
Thanks a lot……
aXcelio
If your all ready rooted why go back to stock?
You don't have to install CWM TWRP is fine as your main recovery.
don't install any ROM for the N7100, that is the non LTE version of the Note 2, it will brick your phone.
CM10 is Android 4.1.2 Jelly Bean. CM10.1 is 4.2 Jelly Bean.
Read the forums for the specific ROM it will give instructions on installing the ROM even if it mentions to use CWM, installing with TWRP is fine.
READ READ READ and have fun
I think i understand, you want to reset and do all this stuff on your phone yourself.
? You would would have to Odin your phone back. Either mobile Odin or one for pc. Pretty simple task once you get the files you need. Think that's right..
Edit: as the guy above me said either is fine. Just preference in what recovery to use. I would suggest to only use cmr based recovery as those seem to be more friendly with development programs and roms than the official by koush that you see in play store. I wouldn't even downloaded it.
Sent from my SGH-I317 using xda premium
nidnarb said:
I think i understand, you want to reset and do all this stuff on your phone yourself.
? You would would have to Odin your phone back. Either mobile Odin or one for pc. Pretty simple task once you get the files you need. Think that's right..
Edit: as the guy above me said either is fine. Just preference in what recovery to use. I would suggest to only use cmr based recovery as those seem to be more friendly with development programs and roms than the official by koush that you see in play store. I wouldn't even downloaded it.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
PC Odin is more safe for the record
Here is a link to a post that breaks down the basics of starting from scratch, rooting and installing clockworkmod and then flashing a ROM. The instructions are in reply to a gentleman inquiring about the Jedi ROM but the instructions will be good for most other ROMs out there. Just check the installation instructions in the op of any rom to make sure there is not something else required for install.
http://forum.xda-developers.com/showthread.php?p=35726061
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
saj222 said:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Instead of linking me to something I've already read, how about actually saying something.
I'm finding too many "this might work for rogers, this might not"
Last time i followed a tutorial meant for an AT&T unit, I hard bricked the phone, and ended up tossing it
Sorry if it was in the wrong section before Kenny.
How about me not responding at all next time? I know no one is forcing me but its simple enough to find this info by searching. I understand your hesitance... No one wants an expensive brick.
I'll put something together for you later today unless someone else beats me to it. Deal?
js593 said:
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Click to expand...
Click to collapse
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
saj222 said:
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
Click to expand...
Click to collapse
Thank you very much. I';ll be looking this over and attempting this tonight.
js593 said:
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
Click to expand...
Click to collapse
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
thecoach1999 said:
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
Click to expand...
Click to collapse
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
js593 said:
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
Click to expand...
Click to collapse
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
saj222 said:
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
Click to expand...
Click to collapse
I believe i ran into the issue blindly.
I forgot to update the bootloader before flashing it. Will try again when i get home and report back with anything.
..
fffft said:
If that sorts your issues, then call it done and thank the people that helped you.
The earlier suggestions were good and not to be faulted. However there is more than one way to do most things. So if you are not happy for whatever reason here is a slightly different approach. There are some very stable custom ROMs that are very snappy and have a similar no lag, fluid feel (Google calls this "butter") to them vis a vis the Nexus. So a simple approach to that result would be:
1. Download and install the Samsung S3 V7.0 toolkit (program)
2. Start the toolkit program
Choose "n" when asked if you want to update the program
Choose your phone version. This is probably "53" for you
Choose option #1 from the main menu to install the necessary USB driver to your PC
After the driver is installed, connect your phone to your PC with the Samsung USB cable.
If your phone is currently stable, you can skip steps #3 + 4.
If you are uncertain, then steps #3 + 4 will restore a stock Rogers firmware as a starting point:
3. Go to Samsung updates and download a stock Rogers firmware
4. Install the stock firmware. This is toolkit menu option #8, 4, 2
5. Download the custom Wicked Aroma ROM v10 (main thread here)
6. Copy the Wicked Aroma ROM to your phone. You can do this in windows by going to file manager and drag and drop the Wicked file (leave it zipped) on the "Samsung Mobile MTP Device - Phone/Data" folder icon.
7. Flash the Wicked ROM from "recovery mode"
Ensure that your battery is at least 80% charged. Then turn your phone off and disconnect the USB cable
Push and hold the home button, volume up and power button at the same time until you feel the phone vibrate and see blue text on screen in the upper left hand corner. Then release the buttons.
On the onscreen phone menu, choose wipe (factory reset)
Then choose install and select the Wicked_v10. zip file
The rest of the install will be automated on your phone screen. It will ask you to select a number of options. If you are uncertain, then just leave them at the default settings. Ensure that you leave the wipe cache setting as is when asked. And I'd recommend the stock theme and stock kernel to start. The rest you can leave as is or change to what sounds attractive to you.
Note that the wicked ROM will change your boot splash screen. Most people won't care and it's not that hard to revert if you don't like the logo for some reason. This is the logo that appears for a few seconds when you first power up a phone.
This is a very snappy, pretty much zero lag and stable ROM. I think that you'd like it.
.
Click to expand...
Click to collapse
Thanks for the lengthy reply.
I tried putting the new bootloader on there, and tried re-flashing, but it did the same thing. So, in the mean time i'm going to use the Dandroid rom (didn't install the Gapps) and it seems to be working okay. I just fear a bit as the phone seems to be running much warmer then it usually does....
In the mean time, ill use this one, and see if it makes a difference (it could still be loading all my settings and whatnot, so we'll see what happens. I love the look of this rom though. Very simple, very clean. Exactly what i was looking for. Those samsung stock themes are terrible.... Thanks a bunch for the help people. Greatly appreciate it!
Personal taste varies a lot and there are a lot of themed ROMs on this site. So you should be able to find something that you like. It sounds like you want something snappy and Spartan looking. If you like your results so far, then no need to go any further.
If you end up trying the Wicked ROM, perhaps choose the Miui or Holo launcher and ASOP lock screen options.
There are an endless variety of home screen themes to be discovered. And no way to know what you might like. A few random screen shots:
http://media02.hongkiat.com/cool-android-homescreens/Clood.jpg
http://media02.hongkiat.com/cool-android-homescreens/evening.jpg
http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2012/09/jb_holo_launcher.jpg
http://i380.photobucket.com/albums/oo248/jb-dan/DroidInc/d4281332.jpg
http://mycolorscreen.com/wp-content/uploads/homescreens_2012/270592/KLPOS7.png
http://desktopspotting.com/wp-content/uploads/2011/12/Minimal-Android-Home-screen.png
.
Just installed the Wicked rom on my S3. NICE! Need to play with the settings a bit to get it configured the way I like, but a definite keeper.
Very nice job.....Kudos!
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!