yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] latino147:
It's terrible. It's like two different screens that flash continously, when you touch the lists and move them up and down you can read them a bit, but it's hard to keep focusing. It's from the start of aroma until the very end (rebooting)
[Galaxy S III Original Android Development] shinyazz52:
When you mentioned aroma I was like WTF!

So read back a few pages and saw that you meant when trying to install ultima rom. I thought you were talking about after rooting with cf auto. My bad :confused:

Sent from the S3
[Galaxy S III Original Android Development] Chainfire:
Today's update to Mobile ODIN does fix the flicker issue, btw.

But yeah I was initially confused as well as to what he meant, until I figured he was talking about AROMA.
[Galaxy S III Original Android Development] 0mega007:
Hi, i noticed after installing CF-Root 6.4 that the "syscope" process become frozen in titanium backup

I got 3 questions?

1)Does CF-Auto-Root freezes the "syscope" process too?

2) If is true that CF-Auto-Root disables "syscope", do it stays disabled if i do a factory reset?

3) If CF-Auto-Root doesn't freeze the "syscope" procces, can i unfreeze it, without causing problems (even on factory reset).
[Galaxy S III Original Android Development] PIRATA!:
So there is a new version of MobileOdin Lite out there??

Same for FlashKernels??
[Galaxy S III Original Android Development] BnYmN:
I've got no root though I flashed it 3 times and twice without "Auto Reboot" but I still got no root. What have I done wrong?

I have international SGS3 (I9300) and used "CF-Auto-Root-m0-gti9300.tar.md5"
[Galaxy S III Original Android Development] jj92942000:
International S3 here, just flashed with Mobile Odin & everoot JB I9300XXDLJ4_I9300ORODLJ1_I9300BVDLI1_HOME.tar and it became unstable. Keeps rebooting in 1-3 minutes, I flashed recovery-cwm-touch-6.0.1.2-i9300, then CF-Root-SGS3-v6.4 then CF-Auto-Root-m0-gti9300 and none are taking root. As soon as I flash one of them it reboots in 1-3 minutes and no root. 1st time I can\t root, was rooted from day one on ICS. If I flash just stock and no root mobile is stable.
[Galaxy S III Original Android Development] kischde:
@jj92942000

you rooted with everroot, flashed cf-root v6.4 and after that cf-auto-root? i´m not sure but i guess that might be the problem itself as you rooted three times with different methods..? maybe those methods interfere and that causes your issues?
[Galaxy S III Original Android Development] jj92942000:
Each time I flashed stock rom with odin PC after 1st time with everroot. Actually, after 1st reboot after flashing with mobile odin and everroot I lost root. Then had no choice but use PC odin. None root options take. I'm sure I can flash ICS stock, then root, triangle away and flash ICS with mobile odin and restore all with TB. Seems something in JB is blocking any successful root on this stock rom.
[Galaxy S III Original Android Development] MeX_DK:
Apparently auto root "voids" your OTA updates :/. I thought that was not the case.
[Galaxy S III Original Android Development] Kangburra:
Does it really matter, we have all the Roms and (mobile) Odin. forget OTA and start developing! :)
[Galaxy S III Original Android Development] PIRATA!:
Ok, I'm about to root my new i9300.

I would like to understand what EverRoot is and if I must use it as a lot of people nominates it here.

Before rooting I'll check to have JB (since I think it is shipped with ICS, I'll find a way to update if there's no OTA updates).

Then I'd like to just root and install custom recovery.

About TriangleAway...is there a way to reset counter to have everything like stock with root and custom recovery?

Or shall I give up with that?
[Galaxy S III Original Android Development] MeX_DK:
It matters if you are trying to keep the phone as close to original...
[Galaxy S III Original Android Development] shinyazz52:
From the man himself

http://xdaforums.com/showpost.php?p=33712009&postcount=142
[Galaxy S III Original Android Development] MeX_DK:
Well in the past he said that you could have both, ie that root didnt screw up OTA. Hence the confusion :P.
[Galaxy S III Original Android Development] Kangburra:
You are on a developer forum, flashaholics and modders, keeping as close to stock is not the idea! :good:
[Galaxy S III Original Android Development] tsch:
It matters. Read the OP, there is clearly stated, that this should be "close to stock as possible" and that it should not break OTA.

I totally agree with MeX!

Sent from Planet 9.
[Galaxy S III Original Android Development] MeX_DK:
For you perhaps. But i have never actually bothered with some of the custom roms. I tried a custom kernel once for my SGS2 and SGS3 and it was so bad that i made my phone worse :P. So yea I am not gonna bother with that route again, I actually like what samsung has made in general and the only thing i have done is use another launcher that allows me more tinkering.

But by all means if you want to flash custom roms etc go ahead. I just like my phone as it is, with a few minor mods: ie call recording etc.
[Galaxy S III Original Android Development] jj92942000:
For anyone experiencing same problems, I resolved it. Auto root didn't work nor CF-6.4 which I used before on ICS. S3 toolkit with XXdlj5 despite having dlj4, also CF-6.1 worked go figure, after I flashed CWM touch 6.0.1.2

My problems are with superuser and binaries, about half root apps were granted root others throw into reboot when asking to be granted root. Both supersu and superuser same problem, got around by granting root without asking.

---------- Post added at 02:47 PM ---------- Previous post was at 02:42 PM ----------

See my earlier comments, once you flashed and root, then install mobile odin pro and triangle away. You'll need to reset counter then flash stock rom with mobile odin and everroot checked then flash CWM touch with mobile odin and everroot. You might need to install CWM app after if you want. Don't update binaries status should stay normal.
[Galaxy S III Original Android Development] repsaj9:
I'm a noob to Samsung (came from LG) so I ask this --

After reading about ODIN and Mobile ODIN, I understand that you can also flash a stock ROM using Mobile ODIN, instead of doing it OTA. Let's say you have successfully rooted JB, installed Mobile ODIN and then later on decided to upgrade the firmware to another stock ROM but you do it via Mobile ODIN instead . Will you lose the root privileges you had before updating?

I see that OTA updates void the root afterwards, but I'm not sure about Mobile ODIN.

Thanks and good job CF!
[Galaxy S III Original Android Development] Kangburra:
Mobile Odin has an inject root option for any Rom, so you will always have root user access.
[Galaxy S III Original Android Development] shinyazz52:
Hey guys , im about to root my s3 using cf - auto , has anybody been successful using this on build i9300xxdlj1? There is a few comments around the forums saying people had issues rooting whilst on this build. Any feedback would be appreciated .
[Galaxy S III Original Android Development] akhil333:
I did both. But factor defaults means settings>factor reset.
[Galaxy S III Original Android Development] PIRATA!:
Wait a minute...you say to do this??

1.flash stock rom

2.root that rom

3.install mobile odin pro and triangle away

4.reset counter

5.flash again same stock rom with mobile odin and everroot checked

6.flash preferred recovery (CWM or CWM touch or TWRP) with mobile odin and everroot (might need to install CWM app after if installing CWM touch)

7.don't update binaries so to have status stay normal

Is this what you say???
[Galaxy S III Original Android Development] jj92942000:
Exactly because 1st root has to be with PC odin then mobile odin keeps root without adding to counter and flashing same stock rom changes modified to REGULAR. You can skip all this and just do that in event of warranty and let counter and modified continue.
[Galaxy S III Original Android Development] rajaraj:
i could agree.I see no SuperSU installed.whenever i try to verify root access,root checker says "system runs extremely slow"
[Galaxy S III Original Android Development] PIRATA!:
....but in the moment I'll install custom kernel, all this list is useless as I'll be for sure in MODIFIED...right??
[Galaxy S III Original Android Development] jj92942000:
So what, if ever an issue just do the above steps and you'll return phone to stock and 0 counter. On custom ROM triangle away can only reset counter to 1. You have to be on stock to get it to 0. Some let counter go to 100+. Have fun and flash away knowing tools are there to get it to factory stock and 0 counter.

---------- Post added at 09:21 PM ---------- Previous post was at 09:17 PM ----------

See my posts a pg. or two back. Be prepared it may not take, I'd have other methods available, but each time reflash stock dlj1 or whichever job stock ROM you want.
[Galaxy S III Original Android Development] PIRATA!:
Deleted.
[Galaxy S III Original Android Development] SiriusCybernetik:
Do you really believe that rooting your phone is staying as stock as possible?

If you like it or not, you modified your phone in a way not supported by the manufacturer.

While on ICS it may have been possible to have root and OTA, it is no longer the case on JB.

Samsung must have packed additional modification detection mechanisms with the JB update.

Remember: The first step in quitting flashaholism is to admit that one is a flashaholic.
[Galaxy S III Original Android Development] ErickXavier:
Theres any way to use HEIMDALL on Mac to root using your method?
[Galaxy S III Original Android Development] shinyazz52:
Anyone assist me ?
[Galaxy S III Original Android Development] Muyfa666:
SGS3 @ v4.1.1...

Flashed XXDLJ4 and then CF-Auto-Root.

I get the red android recovery logo at reboot with no errors, but there is no SuperSU and the root does not seem to work. I've redone the auto root but nothing happens.

I've read Chainfires post over and over again. I can't find out what I'm doing wrong. Any suggestions?
[Galaxy S III Original Android Development] sunstorm:
Try installing SuperSU from the market and set permission to auto grant to prevent crashes. Worked for me.
[Galaxy S III Original Android Development] jj92942000:
See my posts a pg or two back. Had same problems and found fixes.
[Galaxy S III Original Android Development] rainowy:
Hello I am going to root my wife newest galaxy S3. I bought it with ICS and installed JB via Odin. I will use CF auto root and want most stable rom as possible. I don;t care about CWM as long as I can flash new roms via odin and make backup via Titanium Backup. I don"t care about OTA update also. Will let you know how rooting process goes.
[Galaxy S III Original Android Development] kchiman:
Sorry.

I have rooted my device and flashed third party kernel.

Can I go back to stock kernel if I flash this "Root" again?

I am now on 4.1.1 (BB: XXELJ2, Build number: ZSDLK2)

Actually the Software Update is unacceptable and always show because of the modified status

I just want to go back stock kernel and get if fix.

Thank you.
[Galaxy S III Original Android Development] CryptXus:
juz found my problem,.... once i install supersu and set to give root access to all apps, everything is fine now
[Galaxy S III Original Android Development] zimasha:
How can i tell if i have a locked bootloader?

I am afraid that if my bootloader is locked, then rooting with cf-auto root method will brick my phone.
[Galaxy S III Original Android Development] Muyfa666:
I also got it working now. One have to download SuperSU from Play Store after installing CF-Auto-Root. My mistake was installing only the pro license, not the actual program... :)

One more thing, to get CWM back, I just download the version I find from Play Store?
[Galaxy S III Original Android Development] shinyazz52:
Why root with cf-auto root if you want cwm? Should have used cf-Root 6.4 :)

Sent from the S3
[Galaxy S III Original Android Development] Muyfa666:
The CWM in CF-Root 6.4 have compatibility problems with JB 4.1.1...
[Galaxy S III Original Android Development] shinyazz52:
The app does, yes, but the recovery itself doesn't if you enter manually :thumbup:

Sent from the S3
[Galaxy S III Original Android Development] Kangburra:
I used the auto-root and the put TWRP on instead, much quicker and has an install queue for themes and mods.
[Galaxy S III Original Android Development] JKM2247:
I can't agree more. CWM was seamless. It's a bit annoying that a simple upgrade from 4.0.4{with CF v6.2} to 4.1.1 with CF v6.4 or this auto thing with an aim of better Android experience lead to some unpleasantness. The other backup options like Titanium appears tiresome to some of us normal folk. I too hope ChainFire will reconsider
[Galaxy S III Original Android Development] JKM2247:
Yeah, definitely something is wrong. Though I am coming into this topic probably quite late in the day and most likely issues I might raise have already being addressed, please pardon me. I upgraded from 4.0.4 with CF v6.2 working perfectly to JB XXDLIB yesterday and immediately rooted with CF 6.4. However that message of limited functionality caused me to search for better and I landed here. I re flashed JB afresh and followed this CF- Auto instructions to the letter. On installing Root checker, it showed me I have Root but since I have gotten addicted to CWM, I downloaded ROM Manager from Play store but could not get any Root grant so making it practically useless. I installed Titanium and same thing, no super user grant. Scrolling through application drawer showed no SU. Anyway, the long and short is, I re flashed JB again and rooted with CF- v6.4, it's limitations not withstanding, and now all these other Apks work now. So, it can only be a very strange coincidence that a myriad of us in different locations can have an error with this CF unless there is a problem with the CF itself.

ChainFire I respect your work a lot and you probably have good reasons for abandoning CWM. But life was much simpler for us simpletons when we rooted with CF something and life progressed smoothly ever after

---------- Post added 27th November 2012 at 12:50 AM ---------- Previous post was 26th November 2012 at 11:52 PM ----------

Good description of my situation as well
[Galaxy S III Original Android Development] caalca:
Flash zip's with odin

I also miss CWM, but could somebody tell me how to flash zip's with odin?

I need to flash a modem, but with the stock recovery I get ''Signature verification failed".

So, how can I flash zip's with Odin? I don't want to brick my phone again :(
[Galaxy S III Original Android Development] Kangburra:
Get mobile Odin, works with Tar and Zip files.
[Galaxy S III Original Android Development] beardymarrow:
Have you tried installing supersu from play store after auto rooting. I had same problem and that fixed it.
[Galaxy S III Original Android Development] bpalob:
Solved it on mine,...

I've had the same issue with the root not being recognized properly... as mentioned above. Installed SuperSU from Play Store, now all is fine. Thanks a lot !
[Galaxy S III Original Android Development] Chainfire:
I have updated all the CF-Auto-Root downloads. The scripts have been slightly improved, the roboto font is now used, and SuperSU has been updated to v0.98 !

There is no need to flash the updated version if you are currently successfully rooted (you'll have gotten the latest SuperSU from Google Play updates already).
[Galaxy S III Original Android Development] brainimpact:
Thank's buddy just tried the update on a clean device worked perfect no going to play store for SuperSu as CF-Auto-root installs as intended
[Galaxy S III Original Android Development] 0mega007:
Chainfire please answer me this.
[Galaxy S III Original Android Development] radiobicho:
Hi, Chaifire, is it possible to make NANDROID backup/restore using CF-Auto-Root on my GALAXY SIII GT-I9300? Thanks in advance.
[Galaxy S III Original Android Development] cammel:
No, cause it doesn't install a custom recovery, after using cf-auto root you need to install cwm recovery or TWRP recovery in order to perform a nandrois backup/restore
[Galaxy S III Original Android Development] pat357:
You can still use ROM Manager (=also from ClockWork) !

It does all that plus even more !
[Galaxy S III Original Android Development] radiobicho:
Thanks, bro! :)
[Galaxy S III Original Android Development] 0mega007:
Hi, i want to now why the root disables sysscope.apk and if i can just delete it without having problems with the root if i factory reset after i deleted.

Will i still get "modified status" if i delete it or i will get "status not available"

Is just i don't like havin disabled apps, so i rather delete it if no problems will happen even in case of needing a factory reset being rooted
[Galaxy S III Original Android Development] Androidgeert:
I get "modified status" how to change it to normal.

Couldn't find anything with search, there are a LOT modified mods and more.

With TriangleAway i get in Downlodmode Official, but setting>over phone>status only say scanning...

Geert

Sorry for bad inglish, i am netherlands
[Galaxy S III Original Android Development] shinyazz52:
http://xdaforums.com/showpost.php?p=33657188&postcount=129
[Galaxy S III Original Android Development] Androidgeert:
Thanks mate,

Gonna try it
[Galaxy S III Original Android Development] HellcatDroid:
This obviously can't be used when device encryption is being used, eh?

I just killed my data using this:

- was on 4.1.1

- was using device encryption

- updated to 4.1.2

- everything was nice and well

- used AutoRoot for rooting the system

- after AutoRoot recovery had done it's work and rebooted, my /data partition is toast, phone keeps asking for the password and doesn't accept the (correct!) password to decrypt /data and boot up.

WTF?

Why does it (try to) touch /data AT ALL???

It's not a big thing for me right now, as I made (as always) a full backup before flashing, so I can just restore everything and then root manually from CWM and adb shell.

But it's annoying to have to restore the backup now and I think it's something that should be looked into / fixed.
[Galaxy S III Original Android Development] wonsanim:
Thanks Chain:good:Fire
[Galaxy S III Original Android Development] volant:
hi. could u please give me another download link? download speed for me is 1kb/s from ur link. i dont know why!!

edit******: just found another link.
[Galaxy S III Original Android Development] executerx:
I rooted the device using CWM and CF-Root, then used TriangleAway to flash counter and it worked. But still, device status was modified.

I then thought it might be that he recognizes a custom recovery, thus not letting the device status be normal.

So I downloaded the CF-AutoRoot, realizing that it will install a stock recovery instead of the CWM. I did that, and then TriangleAway again and it worked but it had the same effect: device status is considered modified.

How can I fix that?
[Galaxy S III Original Android Development] aggazz:
Read somewhere that you must factory data reset the phone in the stock android recovery afterwards, try it see what happens?
[Galaxy S III Original Android Development] executerx:
Factory reset means that I will wipe out all the apps I currently have (along with any other data on the phone). This also means that I would loose the superuser binary. Are you sure?
[Galaxy S III Original Android Development] HellcatDroid:
Superuser app is usually installed in /system/app, no loss there when wiping.

About all the other apps: Backup and Restore being the magic words here ;)
[Galaxy S III Original Android Development] blooxx:
I`m still waiting for someone to give the thumbs up for this one!it works or not?:laugh:

Later edit: I confirm , after the reset th device status it is normal and supersu it's present in the app drawer!

Will post back if the status changes!
[Galaxy S III Original Android Development] wonsanim:
Flowless:good:
[Galaxy S III Original Android Development] kamikaze.df:
A noob question about root:

At this time, is no other way to root without increases flash counter ? (in ICS stock rom as example)

Other noob question:

If i increase the flash counter to a high value, and for some reason i need send the phone to "warranty" ... is correct say "use triangle away, shutdown, flash a stock firmware and all its ok" ??

Thanks
[Galaxy S III Original Android Development] thegh0sts:
is android version a factor when it comes to rooting with this kit?
[Galaxy S III Original Android Development] strikoo:
It works on 4.1.2. Latest official update without problems.
[Galaxy S III Original Android Development] eduardo_b:
After 30 pages I just have to note that it isn't absolutely necessary to update from ICS to JB (I have JB on Nexus tablet and I can take or leave it) and the warranty is only for a year, so flashing the counter becomes decreasingly important as the weeks and months go by. Going to custom ROM makes OTAs irrelevant (and the OTAs end up on xda anyway). An awful lot of angst about this stuff. If the phone still works well after 30 days, the odds of warranty issues are minimal or less for the next 11 months. Root, flash, enjoy. :D
[Galaxy S III Original Android Development] blooxx:
Not in europe sir, here we enjoy a standard warranty of 24 months, and a lot of things can happen in that time!!

See the sudden death thread where about 2 dozens i9300 where sent to repair with a faulty motherboard.

So Chainfire`s method of having root and still mantain the counter to 0 is the best one ever!
[Galaxy S III Original Android Development] makedoc:
Hi,

I follow the instruction and this is what I get from Odin:

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> recovery.img

<ID:0/007> NAND Write Start!!

<ID:0/007> cache.img

<ID:0/007> RQT_CLOSE !!

<ID:0/007> RES OK !!

<ID:0/007> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/008> Added!!

however when i start Triangle away I get a message the SuperUser access is needed but could not be acquired.

Have I miss something?

Thanks

If I check for Software update is telling me that device has been modified and software updates are not available.

HELP

UPDATE.

I USED ODIN 3.07 AND IT WORKED.

THANKS
[Galaxy S III Original Android Development] mikep99:
download Superuser or SuperSU from the market.
[Galaxy S III Original Android Development] makedoc:
Hi,

I installed SuperSU but it gives me following message:

There is no SU binary installed and SuperSU CANNOT INSTALL IT"

Thanks

If I check for Software update is telling me that device has been modified and software updates are not available.

HELP
[Galaxy S III Original Android Development] nanodroid:
Hi,

I installed this and my phone keeps on restarting. I have flashed it properly everything went smooth. Why is this happening
[Galaxy S III Original Android Development] Quipper2008:
Hello,

i have the problem Odin shows me added and connected (e.g. 0:[COM4] and want to flash something in pda (recovery, cf auto root... but nothing happens:confused:
[Galaxy S III Original Android Development] HabueN:
What is CF auto root? Is this a replacement for CWM?
[Galaxy S III Original Android Development] HellcatDroid:
http://xdaforums.com/showpost.php?p=33305767&postcount=1

(read the full post and your questions shall be answered)
[Galaxy S III Original Android Development] nanodroid:
Are you sure your phone is rooted/you are flashing the appropriate files?

one thing that happened to me is that odin wouldnt detect the phone but it turns out you need to select continue (arrow up on your phone so ot will detect it. this is not mentioned in the instructions