Related
As the title states today i got my sgs s II. impressed with it so far but i want to start flashing new roms. Came from the sgs 4g i am familiar with cwm, odin and superoneclick but looking at roms here i see that there are ICS roms that have special requirements as to flashing (read the megamix install instructions) and i don't want to brick or otherwise mess this phone up. if anyone can guide in the right direction where to start and the differences in the roms on this forum id really appreciate it.
The ICS ROM's are not completely stable yet, they are based off the Skyrocket ICS leak. But it's the same as your old phone, Odin CWM then flash a rom. No need to root if you're going to flash a custom rom, they are already rooted. The only requirement for ICS is flashing the super wipe zip from the dev section before flashing the rom. Just make sure you follow instructions in the OP word for word, and you will be fine. But READ READ READ 3x before jumping in.
Sent from my SGH-T989 using xda premium
ihateDISCO said:
As the title states today i got my sgs s II. impressed with it so far but i want to start flashing new roms. Came from the sgs 4g i am familiar with cwm, odin and superoneclick but looking at roms here i see that there are ICS roms that have special requirements as to flashing (read the megamix install instructions) and i don't want to brick or otherwise mess this phone up. if anyone can guide in the right direction where to start and the differences in the roms on this forum id really appreciate it.
Click to expand...
Click to collapse
It's hard to brick. Use Odin, flash something with root, and use CWM beyond that. Generally, ROM features are listed in the threads where they're posted. You might start out by reading through some threads.
thx for the info i was a little confused about the ics was looking thru and the tuesday rom looks very nice. again thank you for the info and for putting up with a noob.
I agree with what everyone has said.
For what it's worth:
Eugene's Macnut is my daily driver. I try them all, and I am always going back to it. Fantastic battery life, great performance, and everything just works. The custom driver is fantastic--already highly undervolted.
If you don't care about wi-fi calling, his CM7 is fantastic.
If you want ICS, they are all basically the same right now, with a few tweaks / mods / themeing here or there.
Yaldak's vanilla update will be the next ICS that I try (none are quite stable enough for me yet...and no wifi calling) whenever he releases it.
Also--if you haven't already, just CWM via Odin, and you can be done. I never even booted into the stock version when I got the phone.
any working links for the cwm? looking thru posts cant find one that will open.
ihateDISCO said:
any working links for the cwm? looking thru posts cant find one that will open.
Click to expand...
Click to collapse
this is a zip i put together. it has:
Odin 1.85
CWM recovery.tar.md5
ADB / USB Drivers for the t989
http://dl.dropbox.com/u/622730/t989.zip
Enjoy!
I recently rooted and started flashing my GS2 as well as my GF's G2x. For the GS2, I've tried Tuesday's BluRay. It's really nice..very fast and smooth, great looking themes for it too, but I found it was a bit too limited, and eventually had to load another launcher and reconfigure some of the sounds. I also really missed the time on the status bar (M&S has since put out a patch that added the clock to one of the themes, unfortunately it wasn't the theme I preferred). I ran with that for a couple days and have since flashed Foxstar. I really like Foxstar's included utilities and tools, but it was a bit laggy coming out of the lockscreen and scrolling through pages. I've read that loading faux's kernel over the included synergy helps a lot. Will probably do that in a bit and run with foxstar for a few days to test out performance and battery life. But I'm getting itchy fingers and might try one of the CM7 ROMs or Juggernaut soon. I'm making Nandroids of each install I've done (as well as the stock), and eventually I'll pick one to run as a daily driver.
I recommend Eugene's next CM7 update the R3. I've been running with it since R1 and it's superb.
With the massive customizations it's hard to go back to GB or the alpha like ICS's out there. Although the latter have great qualities.
does the cm7 have the tv out function via the mhl cable?
Since you're new here. The few times a gs2 was bricked is because of:
1. flash a rom different galaxy s2 rom as in the international, the att, sprint, old vibrant. We can flash the skyrocket roms though.
2. Using odin to flash a stock rom incorrectly. i.e. using a pit file, battery falls out etc
3. the Phone just DIES OUT. Believe it or not, some people's phone just shuts off and won't turn on again.
But other than that, our phone is pretty hard to brick if you're not stupid.
T989 is a beast and is very hard to brick if you have a lil bit of root knowledge...everything ive learned has been thru google , trial and error and the bad ass devs here at xda..if u search for it you will find the answers to all your questions
ihateDISCO said:
As the title states today i got my sgs s II. impressed with it so far but i want to start flashing new roms. Came from the sgs 4g i am familiar with cwm, odin and superoneclick but looking at roms here i see that there are ICS roms that have special requirements as to flashing (read the megamix install instructions) and i don't want to brick or otherwise mess this phone up. if anyone can guide in the right direction where to start and the differences in the roms on this forum id really appreciate it.
Click to expand...
Click to collapse
Sell it and get a phone with better development. This ones is horrific imho, but you know what they say about opinions. 8)
Since a lot of people have asked me about TWRP 2 for Epic Touch and SGS2 devices, here's the deal:
1) I don't own an Epic Touch or a SGS2 device of any kind.
2) As some may be aware, many Samsung devices do not have and/or properly use a recovery partition. Instead the recovery is packed as a second ramdisk or as a separate recovery.rc in the same ramdisk in the boot image. This means that every time you install a new ROM or kernel, you will get stuck with whatever recovery is included with the boot image.
3) We do have a process that lets you inject TWRP into boot images that are still using the dual ramdisk setup typically found in CM7 boot images. I believe that somewhere along the development path of CM9, the boot image packing method changed to a single ramdisk with 2 init files (recovery.rc). This type of setup is much more difficult (if not impossible) to do "injection" and since I don't have a device in hand to work with I have no plans to attempt to create an injection method for this new type of boot image. The injection process still appears to work on CM7 boot images and some kernel devs for SGS2-type devices have not moved to the new method (yet).
4) We now have code that compiles in CM9. This new code base is much simpler to get started with - you just replace the bootable/recovery folder with the TWRP source code and grab a copy of our slightly modified 1.20 busybox code and you're ready to compile TWRP after adding a few build flags to your BoardConfig.
5) The TWRP source code is all public, including the GUI. It's pretty easy to compile and work with and we have a nice guide to help you out here: http://tinyw.in/nP7d
If you need help integrating TWRP into your builds or have questions about compiling TWRP, feel free to find us in #twrp on Freenode. TWRP works very well with thew GooManager app and if you host your ROM on http://goo.im, your users can receive notifications of ROM updates and easily download and flash the update almost like a regular OTA update. In addition, http://goo.im now supports automatic differential zip creation. You upload an update to your ROM and goo will create a zip with just the changes. Your users get smaller downloads, faster installs, and less wear and tear on the device since only the updated / deleted files get replaced, but this functionality is only easy to use with a supported recovery like TWRP. Please consider adding TWRP to your builds and using http://goo.im and GooManager! All of this functionality is free to you and your users!
If you're feeling really adventurous, you're welcome to install this for the Epic Touch after installing a copy of CM7. I was told by a tester that it was working fine but use at your own risk and be prepared to Odin / heimdall a working boot image if something goes wrong! Note that backups and restores done in TWRP / CWM are not easily interchangable!
http://goo.im/devs/OpenRecovery/epictouch/openrecovery-twrp-2.1.2-epic4gtouch-signed.zip
I can probably create the same kind of a zip for SGS2 International if someone is willing to stop by #twrp on Freenode to test it. I do know that someone has successfully tested a ramdisk on the SGS2 with Exynos so TWRP should work on this device with relative ease.
Also note that it appears for the time being that most Samsung devices released in the USA where all team win members live, are going to be using Qualcomm chipsets instead of Exynos. This means that the only Samsung device that's readily available in the USA that uses the new boot image methods is the Epic Touch. We have a release for the AT&T Galaxy Note and Skyrocket but both of these devices use the Qualcomm chipset which uses a "normal" and separate recovery partition.
No idea what this is about but I got the second post! Woot
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There is a working CM7 for the E4GT. It's posted over at Rootzwiki. TWRP worked fantastically on my Evo and Evo 3D. Glad to see we have another option besides CWM. Hopefully we can get past the bricking issue with ICS roms and I can throw this on my phone permanently.
Thanks Dees_Troy!
Agree worked awesome on my e3d looks to be great
Thanks for this
Sent from my SPH-D710 using xda premium
Team win ftw!!
Sent from my SPH-D710 using xda premium
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Just wanted to say I used TWRP on my 3D and Nexus S and was my favorite recovery hands down. Would love to see it come to the Epic Touch.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
I'm going to second everyone that likes twrp. I also enjoyed the recovery very much and it was the one thing I missed when moving to e4gt. I can't wait for source on ICS. If someone doesn't build it into a kernel, I'll be doing some kernel research and building it for myself.
Sent from my SPH-D710 using Tapatalk 2
This is great news I'm tired of not having a working recovery on ics
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
first off the evo shift is an older lower end phone, so performance on any recovery besides cwm which is so basic is probably iffy. TWRP has been pretty amazing on the evo3d and also on my Gnex, and if it gets ported in any working for on the e4gt id be happy to use it for my wife's phone.
if i understood this correctly, twrp recognized the issue with a constant recovery on the e4gt, and they are basically giving us the source to build it into our roms instead of the the stock recovery, so its atleast there on install. it would be nice to see the developers working on cm9 on this phone integrate it into the rom.
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
i want a working one already because i dont have the means to get mobile odin, and im rarely home, i came from the og epic and most of my flashing was done on the go. Now im lucky to update my rom once a week. A working recovery that wont brick my phone is a huge plus for people on the go
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
I don't mind flashing the EL26 Stock CWM kernel at all. With Mobile Odin it literally takes a minute tops. But I like having the best on my phone and IMO the best recovery out right now is TWRP. It's always worked REALLY well for me. Not one single issue ever. Add in the other features, like compressing backups to save space which may not be a big deal with this device but anyone who's used Sense 3.0 could testify how awesome that feature is. Along with being able to theme every aspect of the recovery and as a themer I just love that option. That's just to name a few. So again, in my case it's not about being lazy but more about wanting the best available for my phone. So if TWRP is a possibility I would love to see it.
I have to agree with tiffany. It is more about the recovery itself. I use mobile odin and take no issue with the current methods but I also would like to have TWRP running on my phone. Hopefully source is released soon and we can take advantage of this. Thank you for posting the links for it and hopefully one of our devs can help to make this happen.
Ok, I admit, odining back to el26 isn't something to complain about for normal flashing. But when trying to alter system files to get the result you are looking for can become somewhat frustrating when a boot loop occurs. Normally a battery pull and a quick flash gets you back in the game. In my experience though, as I'm sure other cracks flashers can agree, sometimes you just have to flash something new, right before you step out the door. Lo and behold you realize you have just set yourself up for failure, failure to boot that is. As I stated in another thread, a lot of folks have busy lives and don't spend every moment reading xda, all they want to do is grab what's hot and flash it with the same procedure as every other Android device that they have come to know and love. In my opinion, working recovery = happy forums. And soon enough we will, and when we do, I want to be sporting TWRP.
Sent from my SPH-D710 using Tapatalk 2
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
daryelv said:
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
Click to expand...
Click to collapse
Sure this is true of some but I get thanked all the time for the work I do. There will always be the gimmie gimmie gimmie people, no matter what your doing.
And yeah if I could theme download mode I probably would. Just the way I am.
graffix31 said:
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Click to expand...
Click to collapse
For those who haven't seen this in action, its worth a look. It is nice to open up goomanager and see all of the latest ROMs and versions that are hosted in goo. You can select the ROM you want and the script flashes it for you and IT WORKS! It is very slick. I would love for a dev to take this on!
Would love to see a themed download mode
Sent from my SPH-D710 using Tapatalk
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
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!
Hi folks,
Just decided to retire my old S3 and when looking for a new phone my main requirement was to get a good DAC built in without breaking the bank or renewing my contract, ended up with the Sprint Note 2. Naturally I was excited but quickly put off by the stock ROM so I decided to root/flash, etc. This is what happened so far;
-Rooted with newest TWRP and root verified on stock rom (followed NK2 instructions)
-Made the big mistake of flashing now without backup, after trying a couple of roms I kept having the same problem (phone gets stuck in load animation indefinitely regardless of rom flashed)
-Gave up on custom roms so I flashed a rooted stock NE2 rom and phone turned on wooohooooooo
-But wait, no network connection, no voice or data, tried to flash modem zip file from http://forum.xda-developers.com/showthread.php?t=2139889 but it keeps saying zip is corrupt, redownloaded & recopied to SD with the same result.
Now I have a working phone but not so working since I can't place calls. What went wrong? any help is very very appreciated.
Phone works after flashing Alliance ROM but somehow now TWRP recovery is gone and phone is UnRooted which is less than ideal but it works nevertheless...
Now before I go off wasting a whole day flashing & waiting for battery to recharge can anyone please point me in the right direction?
I need to figure out the following:
-Root method that works, I'm on Alliance NE2 now
-Which recovery is best recommended for current ROMs?
-Need a kernel that enables audio features like Direct DAC & upsampling
-ROM that actually works with said Kernel and functions at least 90% with wifi tethering etc.?
Surprised it's this difficult with this phone coming from the S3 which took me no more than an hour first time rooting/flashing.
hhmmm 63 views and nobody able to help?
Currently stuck on this ROM, which is horrible because maps doesn't work well, pandora crashes, UI fc's left & right and to top it off the phone is sluggish in every way possible.
Unified Toolkit not working, drivers installed properly, ADB visible in device manager, debugging enabled yet phone can not be seen by Toolkit.
I really don't want to switch back to my cracked S3 but I'm not left with many options considering my note 2 is barely usable now.
Is anyone out there... there.... ere... ere... ere.....
lol seriously feeling like I'm the only person left in these forums.
Use odin to flash recovery but make sure you uncheck reboot option. Once flashed remove battery and while doing the recovery hotkeys insert battery. Now wipe everything and flash another rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app
here's what I've done now;
-Flashed newest TWRP via Odin
-Wiped & flashed Rwilco12's NE2
-Rebooted and phone booted yipeeee
-No cellular connection, crap phone i hate you
-Rebooted to recovery & flashed NE2 Modem
-Rebooted again and recovery is now gone
So either I get root but can't use the phone as a PHONE
or I loose Root and get basically the same POS I started with.
I've given up on eye candy, custom rom, custom settings and my expectations have dwindled down to just ANY ROM + Root + Tether yet that can't even be accomplished. I know I'm doing something wrong but at this point I'm over 10 hours into trying to figure this out and have no idea what to do next. Anything?
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
oceanisbleu said:
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
Click to expand...
Click to collapse
Twrp 2.8.6.x works for almost every rom but you will find most users recommend philz. I as a wantabe dev will suggest philz 6.0.7.9 expect in a few rare cases with aroma installer needing twrp. Personally I have philz 6.9.7.9, twrp 2.8.6.0, shift dual recovery and devil dual recovery zip on my external sdcard. This way I always have what I need depending on what I am doing.
All this info along with solutions to every problem is here on xda already. It may take some time to find everything but really the users should do his homework before doing anything to the phone anyways.
Also if you read the rom thread (Alliance) you would know why you lost root. Simply put you updated supersu app and binary. It is a known issue on every ne2 based custom rom for this device.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
oceanisbleu said:
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
Click to expand...
Click to collapse
I will read every page myself even if it takes a week. You say reading it is more trouble than it is worth which is why you had that issue with Alliance. Same goes for your omni issue.
If you don't want to read that is up to you. A google search will normally help with common issues. I dont mind helping but you have to help yourself first. Not to be rude but I wont answer your omni question because you have not looked. Ypir issue is the number 1 issue omni users have.
Sent from my GT-N7105 using XDA Premium 4 mobile app
won't argue with your opinion as I have my own
oceanisbleu said:
won't argue with your opinion as I have my own
Click to expand...
Click to collapse
I see you edited that a bunch. I dont mind helping. I have been helping so far. Now about the omni gps. I only know on possible fix bit it is a pain.
1. Flash stock/stock based rom
2. Get gps lock
3. While locked and in app reboot to recovery
4. Wipe and install aosp rom & gapps or restore aosp backup
Then you might get gps lock.
Sent from my GT-N7105 using XDA Premium 4 mobile app
reading back I realized some clarity on my part would have been helpful rather than make a general statement.
So the issue with reading 25, 50 or a 100 pages isn't by choice (may have sounded arrogant the way I said it at first) but I work 50 hrs a week, I do work on my home myself, I rent out rooms to students, I have other projects going, etc. so a very very busy lifestyle. Not to mention the daily crap that tends to come up all the time the moment I get home from work so in short, I really can't afford the time to read in that much detail whether I want to or not.
Regardless, by no means am I lazy when it comes to research, notice my post count? yet I've been here since 2009, and since 09 I've had at least 8 different phones (windows phones too) I really try to figure out everything I need on my own so in this case I spent 3 days working on my initial issues, after that I posted this thread which was 8 days ago and had it figured out and finished yesterday (a few bugs aside), that's easily 10 days I spent at least an hour or two a day working on one thing. Surely you understand how frustrating that must begin to feel.
Regarding my last reply, haha I had to delete most of it because I realized I was beginning to take my frustration out on you when in fact you're the only person who actually offered help (still very very thankful) and to top it off I screwed up the rest of the reply when I mentioned GPS, got that mixed up with the topic we were actually discussing (losing root) this happened because I was reading through the GPS issues before I got to your reply and yah mixed it all up, so again apologies for the lack of clarity and thanks for your last reply, it's more straight forward than all the comments I found on that issue.
You won't have to explain anything else I promise haha and I did all this just now but want to verify I did it correctly so I don't come back to it again. After flashing ROM/Gaps/Kernel & supersu, never update supersu after running rom correct?. Root verified as of 30 minutes ago.
GPS, this one is a big big deal because I use it for work but I had already found the answer pretty quickly as I had read something about it before I even flashed Omni.
I do know how frustrating it can be. I have been in worse spots and had to create my own fixes which I have shared here. As far as time goes I understand that being a parent of 7 children.
I am still active here and always willing to help others long as they help themselves also. We seem to have gotten off badly. While some of your post seemed you had done nothing to help yourself. So lets forget earlier stuff and move on.
Yes you seem to have all the steps correct.
FYI android 5.0-5.0.2 all have gps issues but there is a flashable fix. Most new 5.1.1 builds have gps fixed.
If you run into any issues feel free to ask but include steps you have taken to fix the issue. The more you tell the better help you can get. Plus others wont think you are wanting to be spoon fed.
Sent from my GT-N7105 using XDA Premium 4 mobile app
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
oceanisbleu said:
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
Click to expand...
Click to collapse
Well I personally have a Frankenstein device. It started out as a sprint l900 but I removed the sdcard/sim board and put a n7100 board so I can use a cricket sim. This causes issues with calls on aosp so I run modified t0lte (n7105 international) roms.
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile, I believe Phill'z CWM download link is down as well.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Click to expand...
Click to collapse
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
oceanisbleu said:
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
Click to expand...
Click to collapse
Well the donation would be nice but understand when you hit my donation button/link it will take ypu to the Red Cross donation site. That is not a mistake. I personally dont take donations and feel of someone wants to donate something it should go where it can be used by those who need it.
Sent from my GT-N7105 using XDA Premium 4 mobile app