[Q] CM on Telus Phone - T-Mobile Samsung Galaxy S II SGH-T989

Has anyone else with a Telus S2X been successful with ClockworkMod and CM.
I have these instructions:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II_(T-Mobile):_Full_Update_Guide
A few months back their wiki said the T(*(D was not supported but now it is...apparntly?
Anyone else try?

ingrouille said:
Has anyone else with a Telus S2X been successful with ClockworkMod and CM.
I have these instructions:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II_(T-Mobile):_Full_Update_Guide
A few months back their wiki said the T(*(D was not supported but now it is...apparntly?
Anyone else try?
Click to expand...
Click to collapse
Hey im using the S2X right now. Just follow instructions on THIS forum for installing Clockworm Mod or TWRP, and then flash the latest CM10 nightly.
Basically what i did was
I used Odin to Install Clockwork Mod, then used clockwork to install a custom rom(Like a CM nightly..which works GREAT for me but have a few bugs still).
Id suggest finding forum posts on installing clockwork, and reading a bit on using cache wipes and so on.
I personally run the S2X using TWRP recovery instead of clockwork, and the latest CM10 nightly. I cache wipe(theres a thread by thederekjay in the dev section) on every update as well to ensure its clean.
Just read guides and youll figure it out.

Thanks. I've used Odin to install Clockwork before. Which version is a good one?
Also when I goto Cyanogenmod's page I don't see specific S2 builds. Would this one work? http://www.cyanogenmod.com/devices/samsung-galaxy-s2

ingrouille said:
Thanks. I've used Odin to install Clockwork before. Which version is a good one?
Also when I goto Cyanogenmod's page I don't see specific S2 builds. Would this one work? http://www.cyanogenmod.com/devices/samsung-galaxy-s2
Click to expand...
Click to collapse
That will brick your phone as thats or the international version.
http://get.cm/?device=hercules
We go by Hercules(Tmobiles hardware equivalent to the S2X)
As for CWM, i dont use it. I use the latest TWRP which i installed using Goo Manager. I think you need a rooted rom preinstalled to use goo manager. I believe 5.0.2.7 of CWM is what i used or something like that.
The dev section should have a threat just for CWM and read through it to see if anyone has issues. Also reading through the CM10 threads will be helpful for seeing if theres issues.
Id also suggest looking for the 'Discontinued' Darkside cache wipe script. You 'install' it like a ram in CWM, and it wipes the cache's and its helpful.
In TWRP i usually Que up my flashes. I flash my CM updates daily, and i queue the cache wipe script right after. You can also manually wipe dalvik/cache partitions but the script does it for you faster.
Im not sure what you're running right now. But you will also want to go to the modem thread thats stickied in the dev section and keep the Telus LLE4 modem ready to flash as well. You only need to do it once, but if youre currently on Gingerbread still youll need that for ICS or JB roms. Your 'about phone' screen will tell you what modem your currently running. Should end with LLE4.

Related

Weird Problem flashing Roms

Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^

[Q] Noob here. Is installing Cyanogenmod 10 on my SGH-i747M with Rogers safe?

Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Flash a newer recovery prior to flashing CM10.
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Sent from my SGH-I747M using xda premium
such as
SaneinOne said:
Flash a newer recovery prior to flashing CM10.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Such as...
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
okay
GlassRaven said:
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
Click to expand...
Click to collapse
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
EdwinForTheWin said:
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
Click to expand...
Click to collapse
I don't really recommend that as that could cause unwanted trouble. From my experience, I just followed the rooting guide that I posted, flash a custom recovery, and flashed the Cyanogenmod 10. Another tip, if you don't want to lose your contacts, make a backup of it before flashing a ROM. Preferrably you write them in a paper so it would be easier. If you have important messages, use an SMS/MMS backup tool to save them. As for applications, make a list of applications that you consider are essential for you so you could just redownload them. Starting out in a custom ROM is really hard at first but you'll get used to it.
Its safety is directly proportional to your ability to follow directions.
Your first mistake was you used the app to unlock the VERIZON S3 bootloader.
All other versions of the GS 3 have unlocked bootloaders.
You should definitely do some more research before you attempt root and custom recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Can you just use ROM Manager after rooting and flashing the stock ROM to download CWM, then CM10? And is the CM10 you're using on your Rogers phone compatible? I don't see a Rogers version on the CM site. Did you use the AT&T one?
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
tonymtl said:
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
Click to expand...
Click to collapse
What does touch recovery do? And do I have to use that link to flash it, or can I use ROM Manager? And if I were to use that link, I would DL the zip, boot my phone into download mode, plug in, open Odin, make sure auto reboot and F reset time are checked, load the .tar into the PDA, and click start? What happens to the previous ROM that was there?
And when I first root my phone, and load the stock rom, do all of my apps remain? I haven't rooted yet, for my Rogers phone.
A touch recovery lets you touch the screen as apposed to using the volume rocker.
You will keep all your data.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the help! Another question, if I would like to unroot my phone, and decrease the flash counter, is there a thread I should see for the I747MVLLH1? I know about triangle away, but Rogers/my model isn't supported for that.
Triangle away does support Rogers gs3
Thanks! So should I flash CM10 through ROM Manager, or through the link that was posted? I'm not exactly clear on how to flash the ROM through the link though. Does flashing a new ROM erase the previous ROM? And 'wiping cache' doesn't wipe your data/apps right, only 'wipe Data and Cache'? And I don't really need to bother with kernels too right?
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
tonymtl said:
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
Click to expand...
Click to collapse
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Yes it will ask you if you want to wipe, if you download cm10 ROM from ROM manager it will ask you if you want the latest gapps. You can get ROM toolbox or titanium backup to backup your apps and restore them after flashing rom. Backup is just in case but you can always flash stock ROM later if anything goes wrong.
ily112 said:
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Click to expand...
Click to collapse
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
s0ulja said:
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
Click to expand...
Click to collapse
How exactly would I flash through cwm recovery?

Flashing JB Roms causes bootloops

Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
I got a bootloop before when trying to flash JB roms and what I did was restore to original state (using the bad flash recovery technique), and then not rooting it but installing cwm through Odin and dirty flashing the Rom in cwm. Once it flashed I used it for a few to make sure that everything was working correctly. Then I got the goo manager app and got twrp. After that I followed all the steps in the OP (Jedi jelly) and flashed the Rom. Now I'm running Jedi jelly 3.1 perfectly. Hope this method helps.
Sent from my SAMSUNG-SGH-T989 using xda premium
djtreo said:
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
Click to expand...
Click to collapse
are you using darkside scripts to wipe? because they will cause bootloops
skinsfanbdh said:
are you using darkside scripts to wipe? because they will cause bootloops
Click to expand...
Click to collapse
is there any way to reverse the loop that the darkside wipe is causing?
it REALLY sounds like the recovery u are using is TOO OLD. Make sure u are using the latest version of twrp (2.3.3) to flash all jellybean roms.
TWRP is backwards compatible and touch capable, so if you're worried about flashing GB or ICS ROMs it'll do the trick just fine
it is however a requirement for flashing all 4.1 ROMs.
Basic install instructions:
make sure u have root
download goo manager from play
open > menu > install open script recovery
agree to everything, but make sure t989 is in the downloaded image name
reboot to recovery u should see twrp

[Q] Wind SGH-T999V CM Help

Okay, I'm new to Android and I heard this is the go-to spot for help. Anyway, this is what happened to my Wind SGH-T999V. Mind you i'm VERY new to this rooting thing
I rooted my S3 by using TWRP 2.6.3.0 and i used odin3 v1.85 and it worked. I downloaded a root checker and it said i'm rooted. Then i put CM 10.1.2 on my sd card and wanted to install it via TWRP recovery but it gave me an error that said "No MD5 filed found" or something along those line.
I then tried to use different versions of twrp ( twrp 2.6.1.0) and a different CM (10.1.1) but i still got the same "no Md5 found" error. So, a friend then told me to ditch twrp all-together and download CWM instead. So, I download recovery clockwork touch 6.0.3.7 and put it on my phone.
THEN, i tried to go back to the recovery boot place, but after that small blue font saying "recovery boot", my phone goes black. I dont see the old twrp recovery or the clockwork one.
I just really want to have Cyanogenmod on my phone, i've been having a hard time. Help please?
Just disable the md5 check, most or the ROM files are not going to include a hash file, but will flash fine. TWRP or CWM will error out if the flash fails.
Also, it sounds like your recovery install failed, just reinstall using ODIN and a file from @DocHoliday77 (I recommend TWRP over CWM, but it is just preference)
It's already unchecked.
Install TWRP and try again, should work without issue. Also, redownload the ROM file, preferably the latest version, 10.1.3RC2 (I think)
Sent from my T-Mobile T999L using TapaTalk 4 and delivered by Planet Express.
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
qasde455 said:
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
Click to expand...
Click to collapse
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
http://get.cm/?device=d2tmo&type=stable
"Stable" is relative, the RCs are just as good.
Aerowinder said:
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
Click to expand...
Click to collapse
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
You need to edit the install script because your device isn't supported. Or you can download Doc's version.
Actually I'm pretty sure cm includes the T999V, but I'm betting the firmware needs to be updated.
Look in Aerowinders Sig for the links to the firmware. In that OP you should find a link to the thread with the T999V firmware.
Or, you can go to my T999L thread and get the Rom there. But w/o updated firmware it may be buggy.
Sent from my SCH-I535 using Tapatalk 4
It's already unchecked.
qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
CM10.1.3 is now Stable and will be the last 4.2.2 build. It should has the all of the Asserts, including the MB7 one. Also, update your TWRP, the current is 2.6.3.0.
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
malibu.barbie said:
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
Click to expand...
Click to collapse
You should read the sticky threads, and use xdas search for terms or definitions anytime you run into stuff you aren't familiar with.
Sent from my SGH-T999V using Tapatalk 4

[Q] Having trouble with the I747M and ROMs.

Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Czaran said:
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Click to expand...
Click to collapse
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
BCSC said:
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
Click to expand...
Click to collapse
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Czaran said:
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Click to expand...
Click to collapse
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
BCSC said:
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
Click to expand...
Click to collapse
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Czaran said:
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Click to expand...
Click to collapse
I wouldn't use Odin. It really will only become necessary if you want to flash back to complete stock.
You do want the latest version of CWM installed or you will run into problems flashing. You can get this 2 ways.
1: through Rom Manager. You will find your specific CWM with these steps. a-Recovery Setup b-ClockworkMod Recovery c-Hit menu button to left of home and pick 'Show All Devices' d- Here scroll until you get 'Samsung Galaxy S3 (AT&T)' D2ATT. e- Click Flash ClockworkMod Recovery. Allow permissions for root. Ignore the touch option unless you want to pay for it. I can teach you the free way.
You will now have the latest CWM
You can download the latest CM-10.2, it is in release candidate stage and is extremely stable. They have been working on it for months. It will give you 4.3 (The good kind, not the one I warned against). After downloading a ROM, you leave it zipped exactly like it is. Do not extract it, just move it to your SD card. You will also want Gapps. Gapps is necessary because it is Google's own software that is legally not allowed to be built into ROMs. It must be installed separately. You can find those here. They help you know which to use with chart depending on which Cyanogen you use http://wiki.cyanogenmod.org/w/Gapps. Again just move the zip over to your internal.
With these 2 zips transferred to your phone you are ready to start. Before you do, make sure you have transferred all your pics and stuff off of the phone. Also be sure to save your contacts. You can now boot into recovery. You should notice recovery version 6.0.4.3. Volume button scrolls menu, Power button selects. You will want to do a Nandroid backup in case anything goes wrong. I know you did one with CWM 5.5 but should do another just to be sure it is with current CWM. You can delete the other one later.
Goto - backup and restore
Goto - backup to external or /storage/sdcard1 (i put both because im already on 4.4 and may have different menu than you.
Let this work and when done continue to flashing ROM
Go to 'choose zip from /sdcard'
Select CM-10-xxxxxxx.zip
After this completes you will do the same with Gapps.zip
After completion of both files you will need to factory reset your phone. Flashing AOSP over Stock will cause boot loops if you do not.
Go back to CWM main menu and select wipe data/factore reset
After completing this go to wipe cache partition and select this.
Finally you want to wipe Dalvik cache. you will find this in CWM under main menu /advanced/wipe dalvik cache.
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
BCSC said:
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
Click to expand...
Click to collapse
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Czaran said:
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Click to expand...
Click to collapse
Cool terminal emulator was that other way to do it. Hope all is well for you with this. Welcome to flashing. As another tip, if you are going to flash a lot, there is an app called Titanium backup that is well worth the $5 it costs. It saves all your apps and data and after a clean wipe you can just reinstall all your apps in one step. For example after a wipe you will not lose your Angry Birds levels if you restore your titanium data. It's worth a look.

Categories

Resources