yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] freakboy13:
Have you done this yourself or are you just reposting what others have said?

:confused:

So this is completely untrue.

Removing bb will do nothing of the sort.

To remove the modified status you will need to flash back to stock.

I have removed busy box, rebooted and it was still modified. Nothing I have done changed this. I tried installing superuserSU instead of the Su. Nothing.

Uninstalled bb again used a diff installer.

Modified. Cannot be removed by uninstalling bb.

Flashed back to stock. Gone.

I re-rooted using Odin , modified again.

I need bb for tibu so I could care less

Being modified hurts nothing, does nothing other than run the risk of warranty rejection. Atbh if att is like tmo they don't check this stuff.

Is there a secret method or certain procedure for removing Bb?

Idk I just did what another member told me and twice it did nothing.

I'm fine with modified....I'm a rebel baby!

:beer:

PS ... I am suspecting either Bob has nothing to do with it or there is more too it... ahdunno...lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I'll never repost what others have said as my own experience. Let me clarify though, I do not know if simply removing Busybox changes the status back to unmodified. however here is what i know (from my own tests, not reading)

it is a sysscope process that runs on the system doing this "scan". After flashing the method in the OP so your system contains su and Superuser.apk the scan runs and still will show an UN modified state. once busybox is installed and you reboot the scan runs again and detects busybox and shows a modified state. Removing the sysscope.apk's that do the scanning still result in a modified state as something lower level (kernel?) notices it can't call sysscope and sets state to modifed.

All of the above I saw and tested myself looking at logcats as the system boots. I didn't uninstall busybox and see if it went back to unmodified but it stands to reason that if it detects busybox then NOT having busybox should put it back... Are you sure the uninstall removes all traces of busybox? did you confirm that? all symlinks it creates, etc? Did you reboot and ensure the scan ran again?

edit: i don't know those answers myself as i stopped caring. I knew i could get back to unmodified if i wanted and at the time with a 0 counter using this method that is all that was needed. My tests for myself was to see if there was an easy way to stop that scan from happening but I believe you'd need a different kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I haven't heard of anyone losing IMEI flashing anything with ODIN. I can't claim to have read every thread but it seems to be something that can happen flashing things with non stock recovery only. IF that is true then you can at least root your phone safely with this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sicwan:
Subsystem reboot?

I'm not sure what's going on, but I had my phone for a week before I rooted with this method, (Mine is an AT&T one, I got mine on the 22nd and rooted on the 29th/30th)

After that I've noticed my phone will sometimes wake up, disconnect from 3/4G, lose cell service, the battery % will go away, along with the battery icon. and my phone will become unresponsive for anywhere between 5-20sec, then it will come back showing no service, the battery icon and % come back, then it will reconnect and have cell service. what doesn't come back most of the time is my data connection. I have to turn data off, go into airplane mode, then turn off airplane mode and turn data back on for it to come back. (note: i do not know if this is because of what happens when the phone "soft reboots" but I've had this issue a few times when I hadn't noticed the phone "soft rebooting", so i can't say they're 100% related.)

it almost reminds me of when Explorer crashes and windows "comes back" after restarting it.

Has anyone else had this issue? I skimmed though about 2/3 of the posts and didn't see anyone talking about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mordred69:
I must say, I reverted it back to normal. I also had Titanium Backup (which uses BusyBox) installed.

Steps to follow:

1. Uninstall BusyBox from INSIDE the app.

2. Clear data, force stop, uninstall BusyBox Free app.

3. Clear data, force stop, uninstall Titanium Backup

4. Reboot

My device status went back to NORMAL. :good:

Thanks for your quick reply!

By the way I took the liberty of naming your method, on my sig, and link to it. Hope you don't get bothered.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I think this is called a "hot boot" and I've had my phone do it a few times, usually when I'm using it. It looks like the phone just rebooted, but I never see the boot logo or anything like that. It looks the same as when I choose "hot boot" from (the pay version of) QuickBoot.

In my case, every time this happens the gsiff_daemon process goes wild and eats up all my memory. There's other reports of the same thing in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
quick question, I flashed the new UCALG1 root injected(version with the universal search on), but when I go to settings/about device, it shows

the baseband version/kernel version/build number from UCALEM, is this normal :eek:

it should say UCALG1 right?

md5 after I downloaded to my computer and run hashcalc

f9a8516fc16b81c1caad0459a4e1bcaf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mordred69:
Did you flash the right image when rooting the phone? There's one for UCALEM and one for UCALG1... if you flash UCALEM over UCALG1, the phone will report UCALEM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
positive, here is the md5/sha256 values right after I downloaded the image, extension 7z, size 570 MB (598,634,406 bytes) they match the OP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikron15:
Do you mind sharing which root method (thread link will do too) you used that wiped off your IMEI?

I used the rooting method specified by this thread OP on my Rogers S3 and was getting bad battery life on Rogers stock ROM. Tried flashing ICS diet ROM and still the same huge battery drain (10% left after 8hrs of usage). I have now flashed Telus stock rom onto my device and it's behaving normal with big difference in battery consumption (17% left after 21hrs since last charge)...only thing is i am not rooted any more :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
Is that for the current OTA update? Last time I tried it unupdated me and then the OTA update reinstalled again taking away my root.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I don't know. mrRobinson put it together; I'm only hosting it.

BUT, as you're the second person to voice a problem with it, and because I haven't flashed it myself (because of IMEI worries), I'm taking down my root69_ATT_I747UCALG1.7z mirror. Sorry everyone: use the other UCALG1 version and then manually fix up your GoogleQuickSearchBox.apk if you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
Looking at my downloads.. I have been using verison 67 that is 69 .. If you reenable the link I'll test it and tell you if it works or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
Rooted and SU installed. That was all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
I followed this guide to the letter and it wiped my imei.

http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/

DO NOT ROOT WITH THIS METHOD!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
Yeah that is why I am probally not going to put CM10 on this.. And will stick only with this way of rooting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
Probably gonna take a leap of faith and attempt this later tonight. Dunno how I'll explain this one to rogers if something goes wrong again, so fingers crossed!

EDIT: Worked perfect. Rooted, stock, and that's where it shall stay until this imei gong show gets sorted out. Thank you sir!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
Followed the instructions to a tee and it worked FLAWLESSLY. Thanks dude!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milestonedude:
I flashed the AT&T completely stock with just root injected. The only difference since I've flashed is my status bar now says AT&T and before i flashed my s3 my status bar was blank. Does anyone know how to remove this carrier logo from my status bar?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikron15:
Thanks for the info...

Can we use the telus root injected kernel on Rogers s3? They are same models and have same stock build. Currently flashed the Telus stock non-rooted build onto my Rogers device n loving the no bloatware part n good battery stats. My next step is to flash the Telus root img instead of rogers, will that work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markandmyia:
How do I "manually fix up my searchbox apk"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Download Statistics

Just for you interest:

File...........................Downloads

Telus............................165

Rogers..........................331

Bell...............................249

AT&T............................2488
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goojman:
When flashing firmware thru Odin the only box that should be checked is the auto- reboot box right?? Trying to flash back to firmware prior to the OTA update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
First you do a google search then you follow the directions you found :cyclops::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I can swear I read someone discussed how to edit that field. Can't find the post right now but maybe you can, I know it exists.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markandmyia:
so helpful...thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
wow that's a lot of downloads....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Check this Post http://xdaforums.com/showpost.php?p=29086708&postcount=177 Remember to thank the OP for doing this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Download the apk from here, and install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
If you look you can find it..

Zmore took down his hosting link because people had issues with it, I tested it for him and while it worked it is not nearly as safe as manually doing it. And honestly I would not want to host a file that has even a tiny chance of killing someone's IMEI.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I'm not sure anyone had issues with it. one guy was asking about baseband versions and the other guy was actually using the root67 when he asked his question. A different apk inside a tarball flashed with odin can't have any more of a change than the root injected version of killing someone's imei.

Edit: oh, that "guy" using root67 was you... :D

anyway, there aren't any issues with it. i used same image from samsungfirmware for it and the one with just root injected. only difference is a different GoogleQuickSearchBox.apk.

Edit2: that being said, I don't care not providing that image. Doesn't make much sense having 2 500+mb downloads for one apk change. prob best to supply the stock and let people swap out the apk if they care enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
Oh I thought I saw someone losing their IMIE or w/e it is called ... yeah I derped and still had an old verison but it works fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Here is a permanent mirror for the I777UCALG1 Stock plus Root

root69.stock_ATT_I747UCALG1.7z 570.58 MB

MD5 Sum: 2d3c950883f82d7aae4b0c2a073140ca

I'm going to upload the other file overnight. It usually takes over 2 hours to upload because my internet has a slow upload speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
His site obviously more popular than mine haha

Rogers:102

Telus:110

Bell: 142

BTW my md5s are also those on the server, I verified them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Thanks for the heads up. Yeah ive read about this and am a bit concerned. What can i do about this? There doesnt seem to be any roms specific for the sgh-i747M version and everyehere says to use the AT&T sgh-i747 version roms and mods and some have...with success but dont want to pooch phone with IMEI data issue..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kssxs:
Resist the temptation! :p

I don't even HAVE my phone yet, and it's going to be my first Android device, so imagine me reading all these threads and saying to myself... 'maybe I shouldn't have ordered one of of these'... and then I see my co-workers White S3, and see it at Best Buy, and can't help myself ;) . Right now, the way I see it, the MOST safe thing to do is NOTHING, and keep an eye on these forums. There are plenty of talented and experienced people working on this problem, and sooner or later, the solution will be found. Worst case scenario, you can try to find love for TouchWiz :eek:.. personally, it doesn't look all that bad to me, but again, this is my first Android device, so.....

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Getting a "Forbidden: You don't have permission to access /xda/root69_ATT_I747UCALG1.7z on this server." Error on this link from the OP:

"This one is root-injected, but it also retains the univeral search that was removed from the stock OTA update.

Perm Mirror 1:ATT Download I747UCALG1- Needs a mirror, if anyone can help."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
@MrRobinson,

I have uploaded the file root69_ATT_I747UCALG1.7z to Dev-Host for a perm mirror if you want, or will you remove this link from your OP? Let me know, I'll post the link if you want it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
if i can pick one, anyway you can mirror the stock one?

I'm not sure if i should provide the googlequicksearch orig one or not? Like i said kind of seems stupid to have a whole other 500+mb file for one apk change. Those who want to change it can do so easily. maybe I'll just upload the apk to my dev-host (it can handle that :) )

What do you think? opinion?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
The permanent mirror for the stock UCALG1 is in post #769.

If it were my thread, I would remove the modified UCALG1 download from the OP, and put a link to the Universal Search, so anyone who wants can add it themselves.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
missed it on the page change, Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harlenm:
Is there any advantage to using adb or terminal emulator to install cwm recovery versus using rom manager to install it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
No. At the time the instructions were originally written, ROM Manager didn't support our phone. The only other reason not to use ROM Manager is that the latest version of CWM can't see the external SD card. If that's important to you, you have to manually install 5.8.4.5, the last version that could.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kssxs:
Is there an official link for an S3 CWM v5.8.4.5 (I'm on TELUS). I've done some searching, and while I can find that version from the official homepage, I'm worried that I'll download the wrong version, as the page has links for specific phones, rather than a general download for all.

And why would they remove support for external SD cards in the newer versions? What is the logic behind that? We shouldn't have to use an older version to get support for something that so many of us will have as extra storage in our phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] altitude909:
Ok, maybe I am a little thick today but how am I supposed to extract something with a MD5 extension? I thought those were checksum things, not archives..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Just rename the file to CWM-Recovery-LTE-SGS3-v2.tar (drop the .md5 extension) and your archive program should see and extract it like any other tar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] altitude909:
yeah, tried that and it comes up as not a valid archive. Gzip maybe? Im using 7zip

*edit

Winrar did the trick
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Winrar is usually better with these type of files (my default), but tried it on 7zip as well and it works but it gives an 'expected end of archive' or some message like that but it still extracts the files correctly.

I've noticed that with 7zip, you've got to be on the right alpha/beta build to get certain things to work :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
Anyone having trouble installing BusyBox. My system storage shows 0 available. And it seems to fail on the installation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] altitude909:
Rooted :) nandroid backup in process..

Download mode shows clean bill of health

thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
Can someone confirm this working on Rogers model? Our build isn't ucalem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
The root component definitely would not be recommended for any other variant except the AT&T i747 since it's very ROM specific.

However, the process for rooting the image files should be the same if/when the Rogers firmware is available to tinker with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
Downloading now. Just under 50% left. Then I'll put it up on dev-host and post a link in a couple of hours as soon as the upload is complete.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
I'm out of 'thanks' for the day, but thank you to the both of you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Got yer back - thanked 'em both :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
Is there any way to unroot this without messing with the flash counter? I want to make sure I can get back to pure stock just in case I have to return the phone.

Thanks again for this method!

EDIT: I just checked the Team Epic website and they have a post that says how to unroot. Can anyone confirm this works?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
If you flash the original stock ROM from the sticky - http://xdaforums.com/showthread.php?t=1737848 it should take you back an "out of the box" state without tripping the counter and removing all traces of root and recovery.

This only works with the ones in the sticky because they are official (albeit leaked) Samsung update files.

Also - if returning for warranty, you'll also want to do a factory reset to clean your SD card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Can you install cwm using terminal on your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Yes, just type su for root and then the command in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpazevedo:
Thanks for the question, I had the same idea. Thanks again mrRobinson for this. Now I can have a clean root when I get my phone this weekend.:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
It was this. Thanks! I've been out of the Android game for far too long.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Diviance:
Another mirror:

http://goo.gl/q0Dw8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bracketologist:
I'm having BusyBox installation problems too. It fails at the end of the installation. Also, when I installed AdAway and updated the host file, it couldn't create the symlink. It said I needed to be "S-OFF", which if this were an HTC phone, it means that the bootloader security needs to be disabled. Odd error to see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I'm not able to test more till tmr but did you come from completely stock or were you prior rooted?

If you can, can you try a factory reset from within cwm which would format system?

if not i can try this stuff tmr.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I made CWM-flashable versions of the regular and touch versions of 5.8.4.5 for AT&T, which you can find here.

I have no idea. I wish I did. I can't find any kind of change log for the clockworkmod.com CWM releases. Maybe someone else knows?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
Being someone else that this is my first smartphone/Android

I know old TW was bad.. but this one is very good :) Don't worry about CM just root and enjoy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sentry07:
You were right, I found it here http://xdaforums.com/showthread.php?t=1768826
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kssxs:
So those ARE phone-specific, or can be used on another carrier's phone? With all of the stuff going on lately with the lost IMEI issue, I think taking every precaution and asking every question is justified, so don't mind me ;) .

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Check out this page: http://clockworkmod.com/rommanager. You'll find one listed for Sprint, AT&T, Verizon, and T-Mobile, as well as a generic S3 one (which I think is for international). I'm don't know any more than that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Intercrew:
Thank you so much for the guide :) I've successfully rooted the phone. I'll be hold off on installing the CWM or Part 3 optional part of the guide as it's not that safe to install such apps cause of losing the IMEI right?

I got one quick question however. I thought rooting deleted everything? My phone is exactly the same as before, nothing uninstalled and only thing new is the superuser app. Is it necessary to get the elite superuser app or is the normal one fine?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1sagain:
Telus User And confirmed working

I didnt flash CWM yet cuz im too tired...

But Yes!

I am a telus S3 user (got my phone yesterday) and I followed the OP and it worked like a charm

It did take its time with the system.img.ext4 part but it took about 10-12 minutes total

I used ODIN 3.0.7 too

tytyty
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Intercrew:
I've successfully rooted the phone using Telus canadian variant. But I'm confused on how to get CWM. The comands for the android terminal emulator doesn't work :S

Also is there a guide on how to install chainfire3d for the s3?

EDIT: Also whats busybox used for?

Thanks for helping out a n00b
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tx3kgtman:
Edit: Nvm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
If you followed the directions exactly, it will work. However, if you miss a step, make a typo, leave out a forward slash, fail to install busybox first, etc. it will fail.

Can't help with chainfire3d. Busybox contains all the linux command stuff you need to work on the command line, such as the dd command, etc.