yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
It's not irrelevant which one you choose for reasons I have discussed above. If you get a d2can installed vs a d2att you can have major problems. To flash the latest ROMs you have to have a recovery installed that labels your phone as a d2att. The easist way to do this is to flash d2att TWRP. CWM is different and can cause problems with Canadian users which have been discussed in many threads.

In the end its ultimately up to the user what they want to flash. My opinion however and I've been around a while is to use TWRP and use the d2att recovery. General concenus is that it's the better way to go as of late and will allow Canadian users the ability to flash everything found here. Sure there are lots of methods and various ways of going about the same thing. I'm trying to spell it out for them with detailed information on what I KNOW works for Canadian users. Not simply saying doesn't matter, flash away whatever you want because I know that's not the truth and I'm trying to save them the time of running into problems like the user above with the d2att/d2can assert. He has CWM installed now and it's not working for him so I'm simplying leading him to TWRP which I know works.

I'm not sure what ROMs you flash or if you are a canadian or an american user eduardo so I'm not sure if you fully understand the d2can asserts etc. I'm not trying to call you a liar because you seem to believe what you are saying I am simply trying to steer these Canadian users in the right direction to avoid any problems down the road. I've been a canadian user with the S, SII and SIII and stuff isn't always cut and dry for us. It can be confusing when talking about firmware labelled one way or another and what should I or shouldn't I be installing on my phone. So I appreciate your input but I'm not sure you understand the whole story.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kayone73:
Im an American on att so I guess I know which way to go. Thanks for the advice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Two d2att (S3), one I897 (S), two tablets (Nexus, Samsung). So, yeah, not Canadian. :)

This is not the user in Canada you've been posting to, btw. No location noted. I did assume d2att. I do like autoroot because it's fast, simple and reliable. Then an alternate recovery can be flashed.

I see regular posts from TWRP users dissing CWM and ROM Manager on the basis -- I assume -- of their own experience, but not a survey of users. I'm under the impression there are far more people using CWM than TWRP, although this doesn't really say much about either recovery. My experience with US versions of devices has been very good with CWM

I do appreciate your attention to detail and experience with Canadian devices. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I do realize that this isn't the same user but as you mentioned, no location was given so I can only assume he is Canadian and try to steer him in the same direction so if he IS Canadian he won't have any trouble. It will get him to the same end point whether he is Canadian or not so I was erring on the side of caution.

As for my method of getting root installed. It's also reliable and involves exactly the same number of steps as AutoRoot. :) Either way I'm not here to argue with you. Both work so either will do.

I appreciate your input around here as I'm sure many do. I just want it to be clear that us users up in here Canada can make things a little more confusing for the community. We have the M variant of the phone and on top of that there are about 6 carriers up here that use that phone. We have our own little quirks and work arounds and it's not always as simple as your straight up as you d2att users when we are rooting and installing our custom recoveries. So you can't always just say that everything will work or whatever method is better when in fact that's not always the case.

As for CWM vs TWRP. I used CWM with no problems on the Galaxy S and SII and it wasn't until the S3 that I decided to make the switch to TWRP shortly after rooting and installing CWM. I made the switch mostly out of curiosity but also due to some discussion in the CM10.1 Development Thread about TWRP being a little more superior at that time. I haven't looked back and yes CWM is likely the more popular choice but I have read about problems that CWM CAN cause especially for Canadian users. So yes both recoveries; speaking from experience on both, are great, I just find that TWRP is a bit more reliable, a little more clear to the user and is better for us Canadian users.

Thanks again for your input. Things sure can get crazy around here especially if you are a beginner. Even finding out what your phone is referred to in the custom rom world can be hard enough. d2att doesn't sound like what I would want on a Canadian phone and why is the Nexus 7 referred to as grouper? Getting even that sorted out can be hard let alone actually getting down to learning about ADB, custom recoveries and getting ODIN set up.

Thanks for helping out!

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Totally agree. After flashing a variety of ROMs I've settled on Slim, and they have builds for all my devices. But...looking at their download page, there are 28 (!) devices supported, and many are unrecognizable by name. Just found out a few days ago that mako is Nexus 4.

Might pick up unlocked GS4 from Google when they start selling them next week. Don't know what that's called (MD4?). I know Slim team is working on build for it. Not that I need another phone. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I agree. It's pretty wild. As for me I'm running CM10.1 on the S3 and Slim on my Nexus 7. I've tried a variety of other ROMs but those two are my favorites that I keep coming back too. Both seem so professional with their nice websites etc. I'm not saying there aren't some great ROMs with links only found through these forums because there is but I just like how organized and professional CM and Slim seem.

As always though, everyone is encouraged to find something that works for them. I would say that CM or Slim are great beginner ROMs for new users to get a feel for AOKP vs TW. There is lots of information on them and they are great for learning on in my opinion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] touched2u2:
Not sure if I am in the right part of the forum but figured was good as a place as any you get some help.

With that being said I rooted my Rogers Samsung S3 and tried a few Roms like Liquid and a few others and I finally settled down on Hyperdrive RLS14 Which is running great and does what I want on my phone.

Now to my problem after reading and searching to no avail which I am sure posting here I will be pointed in more than likely the right direction on the first try lol

My phone if I plug it into my Mac Android File manager loads up on its own(meaning it detects the phone) but when it opens I get can not connect to device(this is only with USB debugging off) if it on I get nothing. If I hook it up to my Windows laptop using the Unified tool kit which did see my phone originally does not any more so in order to transfer anything to my micro card I got to remove it from my phone and hook up to either pc.

So long question short what am I doing wrong that neither of my PC's see my phone(but Charge the phone) and how do I fix this issue.

Thanks in adavance :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flatherskevin:
You should try having USB debugging on. Also make sure you phone is turned on and is not off or in recovery mode because, at least on Windows, the device wont show up. if you have those things it should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] touched2u2:
I have tried having debugging off and on with no luck.

I did switch off debug and switch off mass storage and now my windows PC sees the phone and I can now transfer files to my phone but still not seen on my MacBook which is what I use and most.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Have you been messing with USSD codes? For example, *#7284# lets you change the Qualcomm USB Settings. If you did that & forgot to change it back, it could screw with your ability to communicate with the device.

Also, drivers! Try removing & reinstalling drivers on the computer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] touched2u2:
yeah I never messed with the USSD and Mac does not have drivers for samsung but before I rooted and such my phone was seen by my mac so not sure what to do but atleast my windows machine sees it now at least.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] digitalnights:
Hey....

I'm not a n00b when it comes to the S3 but I have a question about something. I want to try a custom ROM in my phone, but What I would like to know is this: How do I make a full backup of what I have now, almost like a mirror copy so that I can flash my phone back to the state it is now without having to re-install all my apps and info etc if I don't like the custom ROM...? Is this possible?

Thx...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jd1639:
Make a nandroid backup in recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
In CWM recovery, choose backup and recovery. There are a variety of backup options, one of which is image.zip, with other options including full backup (nandroid) and data-only backup. The last one would restore apps and their data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] digitalnights:
Ok I did that... SO where in my phone is the backup now? It didn't really tell me where it saves to etc...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
I use twrp but it should be the same a folder on ur internal SD called cwm ( twrp if ur using that ) and in the folder should be another folder named backups
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] happyhourtx:
t-mobile ROMS

i have a att SGS3, 4.1.1, rooted, unlocked using tmobile sim. i have enabled 4G/LTE using the guide here.

my question is...should i use a TMOBILE ROM? will that work? or just stick to att roms?

using a stockROM now.

any suggestions on what ROM would be awesome.

Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
You can't get T-Mobile 4g on an AT&T phone only edge I believe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] happyhourtx:
thread here:

http://xdaforums.com/showthread.php?t=1771021

no more edge!!

so now i just want to know if i sjhould flash a tmbile rom or attrom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
It's been so long I don't remember the precise location (likely CWM), but it's on internal SD -- although I remember being able to save to extSD if I wanted, and you can also name the backup file what you want. When you flash new ROM and Gapps, then boot into recovery, choose restore and it will give you list of backups (depending on how many you created) to choose from. That's why custom naming comes in handy. I'm assuming you only backed up data.

I don't remember whether data backup overwrites Gapps (I think it does) because I've been on same ROM for all my devices for long enough that I only dirty flash updates (no weeklies or nightlies) and don't back up data. Not, mind you, that I'm recommending skipping data backups. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WayTooChok:
Samsung Galaxy S3 on 4.1.1 to Latest PA Rom

Hey,

I'm new to the forum and new to flashing roms. I am currently running a Samsung Galaxy S3 on 4.1.1 rooted and I would like to flash the latest Paranoid Android Rom 4.2.2 (with HALO). I have been reading and looking up tutorials but there's nothing that's similar to what I want to do.

I understand that before the flashing process, I should Back up my SMS, etc. Once I back them up using a third party app, I flash the rom and restore the backups correct?

Now for the part that i'm actually confused about, the files that are uploaded to the Nexus forum, can I use these files or must I use other PA files specifically for Samsung Galaxy s3? If so where would I get these files and how would I go about finishing the rest of the flashing process.

If you could help me out, that would be much appreciated. You can PM me.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Definitely you must only ever flash a ROM made for your phone. You must make damn sure it's made for your device. This one is for the AT&T model (d2att / SGH-I747).

As far as the backups, yes. Depending on the backup method you used, you may need to install the appropriate app in order to restore.

In any case, you should 1st do a nandroid backup from recovery before you attempt this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kayone73:
Ok a dumb question but I ask because I wonder if this happened to me.

Before installing a new custom rom I know the proper procedure is

1. Make full nandroid backup with what custom recovery installed

2. Do a full system data wipe

3. Go to install and flash new rom file and updated gapps file

4. Wipe cache/dalvik before rebooting.

My question is: doing a full system + data wipe doesn't touch the nandroid backup file, correct? I only ask because I made a nandroid backup of my stock HTC rom prior to installing CM10.1 and somehow, my stock rom nandroid backup vanished, and I'm trying to rule out possible reasons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
It shouldn't touch ur back up cuz the backups r stored on ur internal SD unless u clicked format SD also I don't think recovery or flashing a ROM could do this but i cold be wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kittentitten60:
I was recently on vacation in an area with no service, but my phone kept trying to download updates anyways so I disabled the downloader app in order to preserve battery. I forgot I had disabled that and tried to download an app later. My phone froze immediately, and now every time I start it up it says "unable to download, try again later" and freezes right away. Could the freezing be because I disabled the downloader or would it be something else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] freakboy13:
Did you freeze natively or third party such as tibu?

sent from my T.A.R.T.I.S

(Time And Relative Tarts In Space)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kittentitten60:
I'm assuming when you say freeze you mean when I disabled the app and not the actual phone freezing (I don't know the accepted terms for these things). I froze the app natively through the phone's settings by hitting the disable option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] disavow:
phone losing apps

Hello, I have a 16g S i747 and recently only with certain apps i noticed that whenever i reboot or Battery dies and i charge and turn back on. I have apps missing, and it's the same ones. I d/l from play and when i reboot they are no where to be found and i have to d/l again. Also a couple of other apps will give me the "unfortunately (name) app has stopped" msg and i will have to un-install and d/l again. and 3rd some apps will just show me the Eula as if i had just run it for the first time or any data i had put in the app was not saved. this all just started happening maybe about 3 months ago and it is only certain apps.

My phone is rooted

stock rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Have you moved apps to the SD card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewzta:
On a custom rom(carbon), if I use one of those pay to unlock services will it work?

Or do I need stock software?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
I haven't actually done it myself, but I think you need a stock ROM to interpret the USSD Codes.

But, why not do the free unlock yourself?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
If its a tw ROM it should aosp it won't I don't think most dialer codes work on aosp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewzta:
post-mortem - I was just lazy, I will flash a stock TW.

oddspec - thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] disavow:
Nope, All are on device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Unless you've already paid for the unlock code, I still suggest you do the free unlock. It's actually pretty easy. Since you're going to flash back to the stock ROM, you can at least try the procedure before buying the code.

Do the problematic apps have anything in common? Are they all paid apps, all free apps? Are they all from the Amazon appstore, for example?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
You can unlock with ASOP ROM. I've done it. Has nothing to do with ROM. Turn phone off and replace current SIM with another one (i.e., replace AT&T with T-Mobile), turn phone on, enter 8-digit unlock code in box that is displayed upon boot. Done. Works with carrier code or other vendor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] disavow:
Nope, some free, 1 paid, from amazon, some are games
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Slushh:
USB troubles

So I am having quite a hard time troubleshooting my phone. My main problem is I cannot copy files to the storage. I have kies installed.

Device will not show up in My Computer

Troubleshoot connection on kies

[kies re-installs driver]

Phone shows up and works for a second or two before the storage freezes up and I cannot copy or see in it.

Also, I downloaded a ROM onto my device to update it. When I do it fails. The error in CWM says assert failed, it says status 7 later. Whatever that means
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kittentitten60:
Whenever I install the stable version of CM 10.1 all of the data on my phone gets erased, including all pictures, TiBu backups, etc. Even if I don't do a factory reset everything is gone after I flash 10.1. Does anybody know how to prevent this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
Uninstall kies and the Samsung usb drivers. Download the latest drivers from Samsungs website, reboot your device and pc, connect your s3 and reinstall drivers. That had worked for me once in the past.

As far as the status 7 error, you either need to update your bootloader, your recovery or both. Read up before you proceed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DukeofPhone:
ROM not seeing cell identities

OK so I have installed the hyperdrive rls14 ROM on my AT&T galaxy S3, I have gone thru the install process several times and its the same result. The activation fails and my llama profile app does not work because the cell towers are not being identified. Anyone know how to correct this issue? This also happens with the synergy r484 ROM.

See the pic below for the cell identity issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Verizon ports can be a bit finicky with reception. Is the signal dropping out ? I don't know much about llama beyond that you set profiles that are triggered my locaiton of cell towers i.e. near home ?

Does this happen on at&t rom's or t-mobile ports ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
Stuck in a ROM... help...

I'm currently running a pretty cool ROM, "The goodness" which is pretty good, just tired of it though. Tried to flash a new one, and got a fail. Did the usual cache wipe, and data wipe, and error again. Even did a data, system and cache reformat and STILL had an error. I'm stuck... It says to check MD5 but everything looks correct. I'm sad now.. Any advice would be helpful. This isn't my first rodeo, but definitely my first horn to the rump. Help please...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
have you tried downloading the rom again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
Yeah... Then I thought that maybe it was that ROM, so I tried the CM 10.1 to test it out, and same error. Did a PC download then transfer, and even a direct download from my phone. (GS3 at&t) Still kicking back...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
and its always the same md5 error? out of curiosity, what custom recovery and version are you running right now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Update your recovery. Flash a recovery IMG in Odin or can you restore and use ROM manager?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
same one each tome. Right now I'm running Clockwork at 6.0.3.1 Think reflashing the recovery would help?

---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------

Updated recovery now to double check. I hoped to avoid Odin, but if I have to, I guess I have to. I prefer ROM manager due to the lack of need for a PC. Work shuns on using their machines for "personal use". And thanks for taking the time with me. I really appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
you wont need odin for anything during this procedure.

nice to see you again, sir.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
Recovery reflashed, attempt 4 going in! Thank you again, both of you. I really appreciate it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bruce Lee:
Do you have the latest bootloader and modem? I had the same issue with flashing cm10.1 but I am using using the below recovery.

TWRP check for download and update's

TeamWinRecoveryProgram

Thanks to: TeamWin & Dees_Troy for bringing this to our device

(Or download GooManager app from Play Store, launch app, grant root permissions, hit menu key and select Install Open Recovery for the latest TWRP version)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
I did see that error! I got so caught up on the first one that I over looked that. Downloading it now! Thanks for the new outlook.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bruce Lee:
For a heads up it might be a boot loader issue and if it is, the recovery won't unless you fix that first. Please read first about boot loader flashing before doing if that is the case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
Thanks for the heads up. You saved another potential heartbreak. Researching the bootloader now before attempting ROM flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
moment of silence....

so yeah... I broke rule #1 and was tired and rushed and didnt read all the way. Out of frustration i tried to flash a bootloader without really doing the proper research on it and paid the ultimate price. Its gone.... bricked. Hard... Ordered a GS4 from amazon...

http://xdaforums.com/showpost.php?p=36433966&postcount=105

This is what I flashed with tired eyes, and short temper. Live and learn.... Thanks for the help though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
i dont know how you managed to get yourself over to the international S3 forums.

there is an I747 and I337 guide in my signature that detail the standard procedures involved in rooting, flashing, unlocking, etc. the (correct) bootloader issue is covered in the I747 thread.

do not do anything with the S4 until you are absolutely certain of things. until then, look over the I337 guide to begin becoming familiar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Horashia:
tired eyes

It was a very dumb thing to do, and I do know better, which makes it worse. Three in the morning after a ten hour work day is now time to play with your phone. Using "In case of emergency" LG incite in the meantime. Oh windows 6.5 and resistive touch screens... I didn't miss you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
hilarious.

we've all done it. messed around with our phones out of impatience. something you learn to never do again. cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SRTGS300:
When I flash a rom can I delete the file because its taking up a gig and a half lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
yes.

grab up a micro sd card sometime. they're well worth the $10 investment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SRTGS300:
I have a 32gb lol I'm running out of space gonna have to upgrade to a 64 lol. Thanks man.